Feature Overview 

The current Octavia implementation supports active-standby for HA. This is good from an HA perspective, but it has limitations in terms of failover to back up time and load loadbalancer forwarding performance (throughput, connections/sec, total number of connections). 

Active-active deployment of Amphora VMs optimizes on the to aspects by providing faster failover to backup and enabling better forwarding performance as an aggregate of multiple Amphora instances. 

Goals

• Active-Active amphora VM deployment for faster failover to backup
• Better aggregate forwarding performance via multiple amphora VM
•  L3 active-active HA with BGP and ECMP
• Auto instantiation of additional amphora VM upon failure

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Refer to the following upstream specification for detailed description of the feature. 

https://docs.openstack.org/octavia/latest/contributor/specs/version1.1/active-active-l3-distributor.html

Done - Acceptance Criteria 

• Functional operation of active-active deployment
• Automation and regression support for active-active deployment

Documentation Considerations 

Feature requires documentation as new feature in the Users Guide and Release notes

Background and Strategic Fit 

• Must have to compete with commercial loadbalancer solutions
• Explicit customer requests for the feature
• Make Octavia carrier grade solution for loadbalancing and adoption with service providers, telco customers and entperise customers with requirement of higher forwarding performance and low tolerance for downtime

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

cc: michjohn@redhat.com 

• …