Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-35124

UI: OVN Kubernetes multi-homing in CNV: IPAM

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • CNV User Interface
    • ui-ovnk2-ipam
      • Subnet can be specified in the NAD dialog
      • IP from the subnet is assigned to each VM requesting it
      • The IP is persistent between VM restarts
    • To Do
    • 67% To Do, 33% In Progress, 0% Done
    • doc-ready, po-ready

      Goal

      Allow UI users to specify a subnet of their OVN Kubernetes localnet and L2 overlay network attachment definitions.

      User Stories

      • As an admin,
        I want to specify a subnet when defining a secondary OVN Kubernetes network,
        so VMs connected to that get assigned with an IP without developers needing to manage them.

      Non-Requirements

      • <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

      Notes

      • The API is still being designed.

        1.
        		 upstream roadmap issue Sub-task New Normal Unassigned
        2.
        		 upstream documentation Sub-task New Normal Unassigned
        3.
        		 upgrade consideration Sub-task New Normal Unassigned
        4.
        		 CEE/PX summary presentation Sub-task New Normal Unassigned
        5.
        		 test plans in polarion Sub-task New Normal Unassigned
        6.
        		 automated tests Sub-task New Normal Unassigned
        7.
        		 downstream documentation merged Sub-task New Normal Unassigned

            aturgema Aviv Turgeman
            phoracek@redhat.com Petr Horacek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: