(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