Skip to content

a10-octavia v2.0.0
Compare
Choose a tag to compare
@ytsai-a10 ytsai-a10 released this 17 Nov 04:10
· 132 commits to master since this release
v2.0.0
fdc82a1
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

a10-octavia on openstack victoria branch

Features:

  • STACK-2099: OpenStack Victoria support for a10-octavia and acos-client
  • STACK-2359: Unset operation support: openstack victoria unset operation support
  • STACK-2005: Loadbalancer Statistics Support:
    Abilities to provide statistics for loadbalancer, listener and amphora.
  • STACK-2694: vThunder Failover Support:
    Abilities to health check and recover vthunder instance that not responding for a while. Only support failover spare vThunder and Active-Standby mode vThunder instance for now.
  • STACK-2612: Licensing:
    Abilities to get license for vThunder instance that created by a10-octavia.
  • STACK-2322: VCS Enhancement:
    Enhance ACOS VCS feat ure to make VCS more stable and efficiency while configured via openstack.

Limitation:

  • STACK-3019: For loadbalancer statistics, ACOS didn’t have similar counter for request_errors statistics. Therefore, a10-octavia can’t provide any request_errors statistics for the listener.
  • STACK-3020: a10-octavia only support Flexpool licenses.
  • STACK-3021: In ACTIVE-STANDBY topology, there can be no difference in bandwidth allocation or other GLM settings. And also the ‘appliance-name’ attribute cannot be used because of this.
  • STACK-3028: Unset operation only support options which supported by a10-octavia set operation.
  • STACK-3029: amp_image_id option will be removed in our configuration in Victoria.
  • STACK-3017: a10-octavia can’t failover spare vthunder without data interface. (Since ACOS not allow to configure slb server if no data port interface, and health manager need ACOS send UDP heartbeat via slb server)
  • STACK-3090: For member batch update, the vthunder flow may take longer time than terraform timeout. And cause terraform report timeout error but it is success on openstack.

Bug Fixing:

  • STACK-2290: Fix VRID blade-parameter lost after VCS configuration merging
  • STACK-2306: Fix VRID not deleted when Loadbalancer is deleted.
  • STACK-2406: Fix vBlade new interface not enabled after create Loadbalancer or member in new subnet.
  • STACK-2235: Fix failed to delete loadbalancer when vthunder instance is dead or shutdown.
Assets 2
Loading