Uploaded image for project: 'OpenStack as Infra'
  1. OpenStack as Infra
  2. OSASINFRA-2764

NFV UX improvements - 4.11

XMLWordPrintable

    • NFV UX improvements
    • Improvement
    • False
    • False
    • Done
    • OCPPLAN-6495 - ShiftonStack Enable Telco/NFV 5G core and edge/RAN
    • Impediment
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Before anything else, please read the spike.

      Background

      In 4.10, we started to support OVS-DPDK workers by documenting and testing all the necessary steps to make it work on both UPI and IPI.
      However, the process is all manual and involves:

      • Configuring vhostuser on the right NIC in the workers so the NICs use VFIO-PCI driver
      • Creating a directory to mount config-drive on the workers
      • Enable vfio-noiommu on the workers, since QEMU doesn't support yet virtualized NOIOMMU (subject to change in the future).
      • Manage the workers Machinesets and their scale (ie scale down workers and scale up with the new machineset so they're SR-IOV capable)

      Also, in some use-cases (e.g. SR-IOV OVS-HW offload), the SR-IOV network webhook has to be disabled in order to let us create a SriovNetworkNodePolicy without error. Some work can be done in this webhook to support that use case.

      Goals

      • Document in both upstream (github/installer) and downstream (doc.openshift.com) these steps (this task is supposed to be done in 4.10, but we need to make sure everything is well documented)
      • Make sure the webhook works fine when OVS-HW offload is configured in the SriovNetworkNodePolicy
      • Design (in a document) an operator for OpenStack (e.g. OAO - OpenStack Addon Operator): what the operator would do and NOT do, how it would work, a proposal CRD, etc. And then present it to the DFG:NFV; collaborate and come to a joint decision to work on it or not.
      • If we decide that an operator is needed, propose it as an openshift/enhancements and socialize it with the OpenShift community
      • In the meantime and if time permits, we can prototype a basic operator, that wouldn't be supported in 4.11 anyway.

       

      Acceptance Criteria

      • Documentation of the manual steps are all documented (task from 4.10 that needs to be confirmed and/or improved in 4.11)
      • The SR-IOV network operator webhook can be enabled for all our use-cases
      • OAO proposal is documented, and presented to the OpenStack NFV team
      • (optional) Enhancement is proposed and engagement is made with OpenShift community
      • (optional) Prototype is demonstrating a basic feature (e.g. configuring vhostuser for the DPDK use-case)

          1.
          QE Tracker Sub-task Closed Undefined Jon Uriarte
          2.
          TE Tracker Sub-task Closed Undefined Unassigned
          3.
          TE Tracker Sub-task Closed Undefined Unassigned
          4.
          Docs Tracker Sub-task Closed Undefined Max Bridges
          5.
          PX Tracker Sub-task Closed Undefined Unassigned

              mdemaced Maysa De Macedo Souza
              emacchi@redhat.com Emilien Macchi
              Ziv Greenberg Ziv Greenberg
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: