Releases: a10networks/a10-octavia
Releases · a10networks/a10-octavia
a10-octavia v2.2.0
Features:
- STACK-3400: a10-octavia IPv6 Support
a10-octavia allows to use IPv6 subnet to configure loadbalancer and members. And most a10-octavia features will still supported with IPv6 subnets. - STACK-3399: Pending Resource CleanUp
a10-octavia will periodically clean up objects in pending status in case of configuration errors. - STACK-3394: ACOS 5 SSL aXAPI Support
For ACOS 5 or later devices, a10-octavia will use corresponding AxAPI payload to prevent compatiablity issues.
Known Issues:
- STACK-3593: The Pending Resource CleanUp feature is not supported with vThunder as amphora case
- STACK-3580: Configure VLAN via a10-octavia is not supported for IPv6.
Bug Fixing:
- STACK-3392 Fix a10-octavia failed to update client-ssl certificate
a10-octavia v2.1.0
a10-octavia v2.1 on openstack victoria branch
Features:
- STACK-3256 Fully Populated Load Balancer: Support Octavia fully polulated Loadbalancer create API, therefore all componets of the loadbalancer components are configured at once in one request.
- STKC-3281 Proxy Protocol: A10-Octavia supports PROXY and PROXYV2 Protocol on pool
Limitations:
- STACK-3275 In Proxy Protocol support, changes in use_aflex_proxy are not applied to objects that are already configured.
Bug Fixing:
- STACK-3242 A10-Octavia failed to create a Load Balancer as IPv6 subnet had more than /32 prefix in the cluster and “ValueError: Negative shift.
count” error is received. - STACK-3169 SLB Health Monitor used the wrong port to monitor the backend server on ACOS.
a10-octavia v1.3.3
a10-octavia v1.3.3 for openstack stein branch.
Bug Fixing:
- STACK-3129 With cascade Loadbalancer deletion, sometimes NAT Pool is not deleted on Thunder.
- STACK-3121 Duplicate members in Batch Member Update case Loadbalancer in pending status.
- STACK-3169 SLB Health monitor use wrong port to monitor backend server on Thunder.
- Add configuration option to switch subnet validation and neutron_lbaas server name format.
- Fix rpc failed issue (Case #00320603 | a10-octavia RPC Connection Leaking)
a10-octavia v2.0.0
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.
a10-octavia v1.3.2
New Feature:
- Default Flavor ID
With this release, A10-Octavia supports the default flavorprofile configuration option in the a10_global
configuration, which will be applied globally to all the users if a flavor is not specified during a load balancer
creation. - Batch Member Update Support
With this release, load balancer pool members can be created, updated, and deleted in a batch using the
Octavia API.
Bug Fixing:
- STACK-2762 The options l2dsr_support and slb_no_snat_support did not work if they
were configured in the set command. - STACK-2620 Load balancer operation failed if the description was more than 63
characters. - STACK-2765 The listener cannot be created for the load balancer if conn_limit was not
specified in the configuration file
a10-octavia v1.3.1
Bug fixing for v1.3.1
- Remove the limitation which "The device-name flavor can only be used to specify the devices whose 'project ID' is not available in the configuration file".
- Fix VRID and Floating-IP issues after loadbalancer is migrated from neutron-lbaas by a10-nlbaas2oct
- Fix failed to delete slb server on Thunder after loadbalancer migratie from a10-neutron-lbaas to a10-octavia when use_parent_project is enabled
- Fix failed to create listener after loadbalancer migratie from a10-neutron-lbaas to a10-octavia when use_parent_project is enabled.
- Fix cascade deletion failed when an aFlex l7rule reference a pool
a10-octavia v1.3.0
Requires:
- acos-client v2.8.0
- ACOS 5.2.1-p1
Features:
- Device-name Flavor Support
- L2DSR Flavor Support
a10-octavia v1.2.0
Requires:
- acos-client v2.7.0
- ACOS 5.2.1-p1
Features:
- A10 Alembic Version Table Enhancement
- Support for vThunder as Amphora
- Dynamic Interface Detection Enhancement
- Support for SLB Cascade Deletion