802aa99c1b
Made paths to include files relative to doc source. This is needed for downstream builds and is good practice for reusability. Fixed some include statements with broken syntax. Added missing section labels to include file. Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: I0423c2008445b49e0bb60b9690925041d7acd6f6 Signed-off-by: Ron Stone <ronald.stone@windriver.com>
1.9 KiB
Data Networks in OpenStack Overview
Data networks are used to model the L2 Networks that nodes' data, pci-sriov and pci-passthrough interfaces attach to.
Note
Data networks are required if you plan to deploy the openstack application or provide SR-IOV network interface access to container workloads.
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. Flat, VLAN and VXLAN type data networks are supported by the virtual switch. For details on creating data networks and assigning them to node interfaces, see the following documentation:
Adding Data Networks Using the CLI <adding-data-networks-using-the-cli>Assigning a Data Network to an Interface <assigning-a-data-network-to-an-interface>Removing a Data Network Using the CLI <removing-a-data-network-using-the-cli>
VXLAN Data Networks are specific to application.
Segmentation ID ranges for VLAN and VXLAN data networks are defined
through OpenStack Neutron commands, see Adding Segmentation Ranges Using the CLI
<adding-segmentation-ranges-using-the-cli>.
partner