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

OVN Kubernetes multi-homing in CNV: Localnet scheduling

XMLWordPrintable

    • cnv-ovn2k-localnet-scheduling
    • Product / Portfolio Work
    • To Do

      .Goal

      Make sure that that VMs requesting a localnet network get scheduled on a node that can provide necessary network resources.

      User Stories

      • As a developer,
        I want my VM requesting localnet to land on a node that has required bridge and ovn-bridge-mapping set,
        so my VM has the required connectivity.
      • As a cluster administrator,
        I want this scheduling to be managed dynamically by the platform,
        so I don't have to keep track of properly configured nodes, label them, and tell developers what node selector to use in their VMs requesting specific NADs.

      Non-Requirements

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

      Notes

      • Ideally this would be handled by OVN Kubernetes alone. Alternatively we could develop a standalone marker similar to OVS and bridge markers.

          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 Closed 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

              phoracek@redhat.com Petr Horacek
              phoracek@redhat.com Petr Horacek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: