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

UI for OVN Kubernetes: Primary user-defined networks

XMLWordPrintable

    • ui-ovn-primary-udn
    • 77
    • Hide
      • UserDefinedNetwork (UDN) can be created through the UI
      • ClusterUserDefinedNetwork can be created through the UI
      • (optional) When first entering a project, user is asked whether they want to define a UserDefinedNetwork for it
      • For namespaces with a NAD of `"type": "ovn-k8s-cni-overlay", "primaryNetwork": "true"`:
        • This NAD replaces the Pod network
        • When creating a VM from both Templates and Instance Types, VMs are defined with network request of UDN with the appropriate binding instead of pod network with masquerade
        • When editing requested networks on a VM, this new type of network is treated the same way Pod networks were - it can be requested once or not at all, and it cannot be hot-plugged
        • A specific IP address can be requested for the UDN interface of the VM. This address must be from the subnet of UDN. When requested, UI will create IPAMClaim CR and tie it to the VM
        • Creating a VM from a Template is not supported - InstanceTypes must be used
      Show
      UserDefinedNetwork (UDN) can be created through the UI ClusterUserDefinedNetwork can be created through the UI (optional) When first entering a project, user is asked whether they want to define a UserDefinedNetwork for it For namespaces with a NAD of `"type": "ovn-k8s-cni-overlay", "primaryNetwork": "true"`: This NAD replaces the Pod network When creating a VM from both Templates and Instance Types, VMs are defined with network request of UDN with the appropriate binding instead of pod network with masquerade When editing requested networks on a VM, this new type of network is treated the same way Pod networks were - it can be requested once or not at all, and it cannot be hot-plugged A specific IP address can be requested for the UDN interface of the VM. This address must be from the subnet of UDN. When requested, UI will create IPAMClaim CR and tie it to the VM Creating a VM from a Template is not supported - InstanceTypes must be used
    • Green
    • To Do
    • CNV-51201 - Integration between VMs and primary user-defined networks
    • CNV-51201Integration between VMs and primary user-defined networks
    • 50% To Do, 25% In Progress, 25% Done
    • dev-ready, po-ready, qe-ready, ux-ready
    • Hide

      In progress
       ...

      Show
      In progress  ...

      Goal

      Primary used-defined networks can be managed from the UI and the user flow is seamless.

      User Stories

      • As a cluster admin,
        I want to use the UI to define a ClusterUserDefinedNetwork, assigned with a namespace selector.
      • As a project admin,
        I want to use the UI to define a UserDefinedNetwork in my namespace.
      • As a project admin,
        I want to be queried to create a UserDefinedNetwork before I create any Pods/VMs in my new project.
      • As a project admin running VMs in a namespace with UDN defined,
        I expect the "pod network" to be called "user-defined primary network",
        and I expect that when using it, the proper network binding is used.
      • As a project admin,
        I want to use the UI to request a specific IP for my VM connected to UDN.

      UX doc

      https://docs.google.com/document/d/1WqkTPvpWMNEGlUIETiqPIt6ZEXnfWKRElBsmAs9OVE0/edit?tab=t.0#heading=h.yn2cvj2pci1l

      Non-Requirements

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

      Notes

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

              upalatuc@redhat.com Ugo Palatucci
              phoracek@redhat.com Petr Horacek
              Guohua Ouyang Guohua Ouyang
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: