Breqwatr's self-service portal binds to the VIP on this address, and is used for Cloud consumers to access and use the cloud portal.
Openstack's public API endpoints. Breqwatr Nodes hold IPs on this address. This network or the Management network should have the default gateway. Outbound internet access is recommended.
Openstack internal APIs and undercloud services such as the database use this network. It should not be accessible to cloud consumers. Switces should trunk this network only to Breqwatr nodes.
This network should have outbound access to any resources you want your cloud guests to have access to, such as the internet or internal LAN networked services. All project routers receive an interface on this network for outbound PAT. All floating IP addresses granted to guests land on this network. Any VLAN provider networks created in the cloud will use the same interfaces as this network.
Breqwatr's storage software uses this dedicated VLAN. It needs to be trunked to all Breqwatr storage nodes and the BMC. It's best to use a dedicated NIC for this network when possible, as the link can get saturated during heavy use. For performance reasons MTU 9000 is recomended - be sure it's configured accross all switches connecting the nodes.
Thank you. Cloud Configuration Submitted.