Bug 1406102

Summary:	[RFE][spine-leaf] Allow defining composable networks in director
Product:	Red Hat OpenStack	Reporter:	Ramon Acedo <racedoro>
Component:	openstack-tripleo-heat-templates	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	high	Docs Contact:
Priority:	high
Version:	12.0 (Pike)	CC:	abdelhadi.chari, akarlsso, bfournie, brault, cpaquin, dsneddon, dtantsur, dyasny, ealcaniz, ecv-redhat, gkeegan, jjung, kbasil, lmiccini, mariel, mburns, mcornea, mrussell, rhel-osp-director-maint, rhosp-bugs-internal, sasha, sclewis, shardy, tvignaud, tvvcox
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/tripleo/+spec/composable-networks
Whiteboard:	upstream_milestone_pike-3 upstream_definition_drafting upstream_status_good-progress
Fixed In Version:	openstack-tripleo-heat-templates-7.0.3-0.20171023134947.8da5e1f.el7ost	Doc Type:	Enhancement
Doc Text:	Director now supports the creation of custom networks during the deployment and update phases. These additional networks can be used for dedicated network controllers, Ironic baremetal nodes, system management, or to create separate networks for different roles. A single data file ('network_data.yaml') manages the list of networks that will be deployed. The role definition process then assigns the networks to the required roles.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 20:57:54 UTC	Type:	Feature Request
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:	1547088
Bug Blocks:	1281573, 1214284, 1241596, 1389435, 1396159, 1442136, 1459148, 1497893, 1615663

Description Ramon Acedo 2016-12-19 17:56:01 UTC

Currently, we can only use the networks that are defined in the TripleO templates (i.e. control plane, external, internal API, tenant, storage, storage management and generic management).

A user might require additional networks or might want to label a network to reflect its role. To achieve this, director should allow the user to compose networks for using in the Overcloud.

Comment 1 Ramon Acedo 2017-01-03 11:08:51 UTC

Some related upstream work: https://review.openstack.org/#/c/409921/

Comment 7 Ramon Acedo 2017-05-24 10:19:43 UTC

Steve, are there any other patches required to complete the composable networks work after OpenStack Gerrit patch 409921 was merged?

Comment 12 Bob Fournier 2017-07-21 14:03:22 UTC

*** Bug 1381704 has been marked as a duplicate of this bug. ***

Comment 15 Alexander Chuzhoy 2017-11-14 16:08:12 UTC

Verified:

Environment:
openstack-tripleo-heat-templates-7.0.3-0.20171024200825.el7ost.noarch

Successfully deployed OC with:
composable networks for all roles.
IPv6 composable networks.
predictable IP on ipv4 and ipv6 networks.

Comment 19 errata-xmlrpc 2017-12-13 20:57:54 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-2017:3462

Comment 20 Bob Fournier 2018-01-08 15:09:57 UTC

*** Bug 1361714 has been marked as a duplicate of this bug. ***