The Nuage ML2 plug-in should support multi-tenancy for bare metal nodes as described in the upstream documentation: https://docs.openstack.org/ironic/latest/admin/multitenancy.html https://docs.openstack.org/project-install-guide/baremetal/draft/configure-tenant-networks.html It should also support Neutron Port Groups to configure LAG: https://docs.openstack.org/ironic/latest/admin/portgroups.html These RFE should identify and report gaps to implement and/or fix for a fully supported BMaaS (bare metal multi-tenancy) with the Nuage ML2 plug-in using OSP. Nuage will verify this functionalities with OSP 11 and the Nuage VSG and WBX ToR Switch. These are the features to be verified, as reported by the Nuage team: - Support for Nuage VSG and WBX ToR Switch - Support for Introspection (LLDP or manual) and Provisioning networks - Multi-tenant networks for ironic - Bare metal connection as bridge vport - Port Security Extension - Security Groups support for provisioning and tenant networks - VLAN Transparency (per port option) - VLAN Trunking (per port option) - Port Groups (LAG or MC-LAG on ToR Switch)
This is TestOnly of the Nuage ML2 driver with Multi-Tenant support. Multi-Tenant support in OSP-13 is TechPreview. Adding the Fixed in Version and component associated with the support and moving this to ON_QA.
The content for this fix is included in OSP 13 RC which is available on the Red Hat OpenStack Platform beta channels currently. Any efforts to verify that these bugs have been fixed would be appreciated.
Install OSP13 and verfied that openstack-tripleo-heat-templates version 8.0.0 or higher was installed. Please reopen if this issues persists.
Brad - as this is OtherQA I think it should be verified by Nuage.
Per Bob's comment moving it back to ON_QA. need to have Nuage to verify this bug.
Hi Mark - I was wondering if there's been any progress on the testing or if you have a date for completion? Thanks!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0448