Feature Overview

In RHOSO 18, Octavia supports the jobboard feature through Redis support, it means that Redis is used to ensure High Availability of the Octavia controllers.

Unfortunately, the Octavia antelope release (upstream of RHOSO 18) didn't fully support Redis Sentinel, which is HA for Redis, because some configuration settings were not implemented in Octavia. So the Octavia services only use 1 Redis instance in 18 and have limited resilience during Redis node failures.

This issue was fixed upstream and will be available in the next major release of RHOSO, the octavia-operator needs to take it into account to configure Octavia and Redis accordingly, then the Octavia services will be able to use multiple Redis instances.

Goals

• Octavia operator configures the Octavia services and Redis instances for HA
• Using Redis Sentine improves the stability and HA capabilities of Octavia in RHOSO
• Note: Redis might not be enabled by default in Octavia

Requirements
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.

Done - Acceptance Criteria

Octavia configures the Octavia services with sentinel

During Redis master failover, Octavia services automatically reconnect to new master

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

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

• …