Template:

Networking Definition of Planned

Epic Template descriptions and documentation 

Epic Goal

Manage Openshift Virtual Machines IP addresses from within the SDN solution provided by OVN-Kubernetes.

Why is this important?

Customers want to offload IPAM from their custom solutions (e.g. custom DHCP server running on their cluster network) to SDN.

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)

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

Sizing

• M (1 eng. 2 sprints)

 Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement
  details and documents.
• IPv4 range can be defined on OVN Kubernetes secondary network.
• VMs are able to get a IP from this subnet.
• The IP sticks to a VM during live-migration.
• The IP sticks to a VM even if it is temporarily shut down.

Dependencies (internal and external)

1.

...

Notes

• This epic serves for prioritization in SDN backlog, and as a capacity blocker for OVN Kubernetes maintainers to review the IPAM work otherwise done by the CNV team
• Implementation tasks should be filed under CNV-24260