OpenStack ecosystem integration limitations are as follows:
- Only green field deployment is supported.
- There is an operation in Neutron to turn off routers. This operation is not supported by Extreme OpenStack support (L3 plugin or flavor), because SLX devices do not support the disabling of routers.
- EFA backup impacts OpenStack operations.
The EFA backup process is scheduled for midnight daily, by default. Any OpenStack operations that are initiated while the EFA backup is in progress can result in failures.
To recover, clean up any failed entries and retry OpenStack operations after the EFA backup process is complete.
EFA backup can be turned off or rescheduled to times that do not conflict with operations.
For more information, see the
efa system settingscommand in the Extreme Fabric Automation Command Reference, 3.1.0 .
- Tenant VRF entities stuck in the
vrf-device-sr-delete-pendingstate must be deleted for recovery. Issue the efa openstack debug router delete --router-id <router-id> command to clear the erroneous entries in the tenant. The efa-sync execute command on the Neutron side synchronizes the routers, router-ports, and route entries to the EFA.
OpenStack ecosystem integration dependencies are as follows:
- Non-Clos (2-node, 4-node, and 8-node)
- 3-stage Clos (leaf or spine nodes)
- 5-stage Clos (leaf, spine, or super-spine nodes)
- Compute nodes (connected to every leaf node in MCT and non-MCT configurations)