Bug 1895317

Summary:	[DOCS][spine-leaf] Document how to add a new leaf/subnet into undercloud.conf
Product:	Red Hat OpenStack	Reporter:	Bogdan Dobrelya <bdobreli>
Component:	documentation	Assignee:	Greg Rakauskas <gregraka>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	gregraka, igallagh, jamsmith, mgeary, rheslop
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-18 22:32:15 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:

Description Bogdan Dobrelya 2020-11-06 10:28:17 UTC

Description of problem:
For DCN setups in particular, it is not clear how to add a new site into existing deployment. AFAIK that involves creating new leaf in the existing spine-leaf setup, then adding computes there, and finally placing them into a new AZ.

That bug is focused on providing documentation on how to add a new subnet into undercloud.conf and apply that change into existing spine-leaf setup. That can be general networking documentation, not necessarily the DCN-specific one.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
See also: http://post-office.corp.redhat.com/archives/rhos-tech/2020-August/msg00292.html

Comment 6 Greg Rakauskas 2022-04-18 22:32:15 UTC


*** This bug has been marked as a duplicate of bug 1594606 ***