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.6 KiB
VXLAN Data Networks
Virtual eXtensible Local Area Networks () data networks are an alternative to data networks.
A data network is implemented over a range of Network Identifiers (.) This is similar to the option, but allows multiple data networks to be defined over the same physical network using unique defined in segmentation ranges.
Packets sent between over virtual project networks backed by a data network are encapsulated with IP, , and headers and sent as Layer 3 packets. The IP addresses of the source and destination compute nodes are included in the outer IP header.
starlingx
supports two configurations for :
partner
- Dynamic , see
Dynamic VXLAN <dynamic-vxlan>
- Static , see
Static VXLAN <static-vxlan>
Before you can create project networks on a provider network, you must define at least one network segment range.
Note
Static VXLAN is limited to one data network, and if configured, it must be enabled on all openstack-compute labeled nodes.
Dynamic VXLAN <dynamic-vxlan>
Static VXLAN <static-vxlan>
Differences Between Dynamic and Static VXLAN Modes <differences-between-dynamic-and-static-vxlan-modes>