Bug 1594606 - [Docs][EPIC][RFE] Document updates to spine and leaf topology
Summary: [Docs][EPIC][RFE] Document updates to spine and leaf topology
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: async
: 16.2 (Train on RHEL 8.4)
Assignee: Greg Rakauskas
QA Contact: Alex Katz
URL:
Whiteboard: docs-accepted
: 1895317 (view as bug list)
Depends On: 1214284
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-24 23:37 UTC by Lucy Bopf
Modified: 2022-05-02 18:49 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-02 14:56:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2659 0 None None None 2022-03-23 17:59:13 UTC

Description Lucy Bopf 2018-06-24 23:37:07 UTC
(The following details are taken directly from a documentation detail plan completed by Content Strategy and function design leads)

User story: 
As an OSP data center operator, I need to be able to deploy Openstack on top of a L3 spine and  leaf network topology to limit the broadcast domain between racks, allowing for large scalability and more efficient network utilization so Iā€™m not having needless traffic propagating across data center (each rack is self contained)

Purpose of function: 
Customers are requesting that we support a L3 leaf-spine network topology, where (usually) ToR-leaf switches have a L3 routed link via the spine switches to each other. In this topology, each rack will have hosts in different subnets. Currently the director supports just one "Management" network, one "Storage" network, etc. With this topology, multiple "Management", "Storage", etc, networks should be supported.  In addition, we just support one "Provisioning" network for the provisioning via PXE boot. This should also be addressed, for example requesting setting up DHCP relays in the network.

Documentation requirement:
- Preparatory work, configure:
  - configuration file,
  - composable networks
  - composable roles
  - switches and routing 
- Prepare data center DHCP relay & routing, switch setup
- Constraints of setup
- Port information for understanding routing
- Routers info for each leaf
- Networking configuration info to enable routers in Neutron
- Parameters for roles, networks, etc. (environment file for director)
- How to verify for proper installation
  - Network configuration
  - Log on check correct use of IP and multiple networks
- How to add a new leaf

Comment 2 Lucy Bopf 2018-06-24 23:41:10 UTC
Assigning (officially) to Dan for review.

Dan, I know you have been working on this already, so please update with the current status.

Comment 9 Greg Rakauskas 2022-04-18 22:32:15 UTC
*** Bug 1895317 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.