3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
1.6 KiB
Executable File
Overview
Data networks are used to model the L2 Networks that nodes' data, pci-sriov and pci-passthrough interfaces attach to.
A Layer 2 physical or virtual network or set of virtual networks is used to provide the underlying network connectivity needed to support the application project networks. Multiple data networks may be configured as required, and realized over the same or different physical networks. Access to external networks is typically granted to the openstack-compute labeled worker nodes using the data network. The extent of this connectivity, including access to the open internet, is application dependent.
Data networks are created at the level.
Segmentation ID ranges, for and data networks, are defined through
OpenStack Neutron commands, see Add Segmentation Ranges Using
the CLI <adding-segmentation-ranges-using-the-cli>.
For details on creating data networks and assigning them to node interfaces, see the documentation:
Add Data Networks Using the CLI <adding-data-networks-using-the-cli>Assign a Data Network to an Interface <assigning-a-data-network-to-an-interface>Remove a Data Network Using the CLI <removing-a-data-network-using-the-cli>
partner