Bug 1562171

Summary:	[RFE] Full support for multi-tenant networking in bare metal provisioning
Product:	Red Hat OpenStack	Reporter:	Dmitry Tantsur <dtantsur>
Component:	openstack-ironic	Assignee:	Dmitry Tantsur <dtantsur>
Status:	CLOSED ERRATA	QA Contact:	Arkady Shtempler <ashtempl>
Severity:	high	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	achernet, bfournie, dradez, dtantsur, jamsmith, mburns, racedoro, rhel-osp-director-maint, srevivo, tfreger
Target Milestone:	Upstream M2	Keywords:	FutureFeature, Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-ironic-11.0.1-0.20180710182436.d29dab2.el7ost	Doc Type:	Enhancement
Doc Text:	This update introduces multi-tenant bare metal networking with the "neutron" network interface. By configuring the bare metal nodes with the "neutron" network interface, an operator can enable the users to use isolated VLAN networks for provisioning and tenant traffic on bare metal nodes.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:49:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1335995, 1565622
Bug Blocks:

Description Dmitry Tantsur 2018-03-29 17:05:06 UTC

It was introduced as TechPreview in https://bugzilla.redhat.com/show_bug.cgi?id=1335995. We need QE coverage and documentation for make it fully supported. Ideally, we need more ML2 plugin vendors on board with it. Even better, a generic ML2 plugin capable of working with ironic.

Comment 5 Arkady Shtempler 2018-11-28 14:34:49 UTC

Verified by:
https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/workitem?id=RHELOSP-40439

Comment 10 errata-xmlrpc 2019-01-11 11:49:20 UTC

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/RHEA-2019:0045