Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

Provide visbility into the behavior of the on-prem IPI internal loadbalancer VIPs.

There are two primary things this covers:

1. Displaying which node holds each VIP. This should only require access to the addresses configured on each host and the Infrastructure CR that lists the VIPs. With those two pieces of information we should be able to indicate in the Observability UI which node holds which VIP. Hopefully this is the low-hanging fruit here.
2. As a further extension to that, we could provide a new view that includes a timeline of VIP events. This would require parsing the keepalived logs from each node, much like https://github.com/cybertron/keepalived-log-parser does. This is quite a bit more complex and might warrant its own epic, but we can make a call on that as we discuss this more.

Why is this important?

Customers want to know what is happening with their VIPs - where they are, when they moved and why, if they are present in multiple places, etc.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

...

Dependencies (internal and external)

1.

...

Previous Work (Optional):

1. Offline version of this that is intended for post-mortem debugging: https://github.com/cybertron/keepalived-log-parser

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>