Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-640

Revisit design for 3rd party integration for Neutron

XMLWordPrintable

    • Neutron 2023Q4, Neutron 2024Q1
    • 2024Q1
    • Networking; Neutron

      This spike is to revisit integration points that we are going to provide for 3rd parties.

       

      Context: we already support extraMounts in CRDs for neutronapi to mount plugin and config code into the pods running neutron-server. That may be enough for multiple cases, but it may be an incomplete solution. E.g.

       

      • extraMounts require HostPath mount, which has its own issues (e.g. AFAIU it implies additional privileges for the pods?)
        • can we migrate 3rd parties to use PVCs to carry their plugin code?
      • EDP story is unclear: do we provide documentation on how to extend EDP nodes with custom services?
      • There are some hook entrypoints in our EDP services, e.g. rootwrap.d directory is added to filters_path for our neutron agents, under assumption that something external (3rd party?) will add more filters there. Are these needed?

       

      The result of this spike will be an agreement on the list of integration points needed for 3rd parties.

            ihrachys Ihar Hrachyshka
            ihrachys Ihar Hrachyshka
            rhos-dfg-networking-squad-neutron
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: