-
Spike
-
Resolution: Done
-
Major
-
None
-
None
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.
- causes
-
OSPRH-3678 As a partner, I want to be able to integrate Neutron with my custom ML2 driver and SDN back end [Tech preview]
- Resolved
- relates to
-
OSPRH-684 Remove unnecessary privileges from neutron operator
- Closed
- links to