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

[TP] OVN Kubernetes secondary L2 overlay: IPAM

XMLWordPrintable

    • cnv-ovn-k-multi-ipam
    • Hide
      • D/S test automation
      • D/S documentation covering this as a part of our OVN Kubernetes page, explaining the difference between CNI IPAM used for Pods and the OVN DHCP IPAM used for VMs
      • IPv4 range defined on OVN Kubernetes secondary networks ** using the existing "subnets"  attribute is supported for VMs
      • VMs are able to get an IP from this subnet
      • The IP sticks to a VM during live-migration
      • The IP sticks to a VM even if it is powered off for as long as the VM object exists
      • (stretch) Pods and VMs can share a single IP pool
      • (stretch) A specific IP can be requested by user (network selection elements).
      Show
      D/S test automation D/S documentation covering this as a part of our OVN Kubernetes page, explaining the difference between CNI IPAM used for Pods and the OVN DHCP IPAM used for VMs IPv4 range defined on OVN Kubernetes secondary networks ** using the existing "subnets"  attribute is supported for VMs VMs are able to get an IP from this subnet The IP sticks to a VM during live-migration The IP sticks to a VM even if it is powered off for as long as the VM object exists (stretch) Pods and VMs can share a single IP pool (stretch) A specific IP can be requested by user (network selection elements).
    • Red
    • To Do
    • CNV-16692 - Networking OVN and UDN Integration
    • CNV-16692Networking OVN and UDN Integration
    • 19% To Do, 2% In Progress, 79% Done
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready
    • Technology Preview
    • Hide

      For awareness. Due to shift of 4.18 priorities, we are putting our 4.17 work on pause. I will remove the target release after the next leads call....

      Show
      For awareness. Due to shift of 4.18 priorities, we are putting our 4.17 work on pause. I will remove the target release after the next leads call....
    • Proposed

      Goal

      Provide IPAM to customers connecting VMs to OVN Kubernetes secondary networks.

      User Stories

      • As a developer running VMs,
        I want to offload IPAM to somebody else,
        so I don't need to manage my own IP pools, DHCP server, or static IP configuration.

      Non-Requirements

      • IPv6 support is not required.

      Notes

      • KubeVirt cannot support CNI IPAM. For that reason we cannot utilize the current implementation of IP management in OVN Kubernetes
      • OVN supports IPAM, where an IP range is defined per port, and the port then offers assigned IP to the client using DHCP. We can use this

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue <link to GitHub Issue>
      DEV Upstream code and tests merged <link to meaningful PR>
      DEV Upstream documentation merged <link to meaningful PR>
      DEV gap doc updated <name sheet and cell>
      DEV Upgrade consideration <link to upgrade-related test or design doc>
      DEV CEE/PX summary presentation label epic with cee-training and add a <link to your support-facing preso>
      QE Test plans in Polarion https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-10864
      QE Automated tests merged <link or reference to automated tests>
      DOC Downstream documentation merged <link to meaningful PR>

       

              mduarted@redhat.com Miguel Duarte de Mora Barroso
              phoracek@redhat.com Petr Horacek
              Yossi Segev Yossi Segev
              Votes:
              1 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: