The current RHOSO setup deploys OVN operator and configures Neutron to use ML2/OVN. It also deploys OVN services (ovn-controller, ovn-metadata-agent) on EDP nodes.

As a partner shipping a custom Neutron ml2 driver, I would like to be able to deploy RHOSO with it integrated. The integration should make it possible to avoid deploying OVN components in the cluster. It should also allow to deploy needed SDN back end components for OCP workers and EDP nodes. Finally, the integration between back end components and the ml2 driver should be possible (configuration files, as well as means to communicate with the back end, e.g. through TCP or UNIX sockets.)

Security implications of driver-to-back end should be considered. This includes securing file based or Internet sockets for communication; as well as the means to pass custom configuration into neutronApi containers. (extraMounts vs defaultConfigOverride - the latter is not secure; the former allows to mount secrets.)

The work items for this Epic will include documentation explaining step-by-step what should be done to do the integration; also necessary changes to operators should be applied to untangle RHOSO from OVN choice of back end, where needed.

This Epic is foundational to actual integrations executed by partners. The testing will not be E2E; we'll cover separate integration points in functional and kuttl tests as needed.

There will be no user-visible documentation updated as a result of this Epic. Specific integration guides for each supporter 3rd party driver will be tracked elsewhere.