Deploy instance to VXLAN-5 minutes a day to play OpenStack (112)

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026488351033984.jpg "/>

In the previous section we created the Vxlan 100_net, which will deploy instance today and analyze the connectivity of the network.

Launch new instance "CIRROS-VM1", network selection vxlan100.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026488761089794.jpg "/>

The IP assigned to the CIRROS-VM1 is 172.16.100.3.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026488933035253.jpg "/>

The CIRROS-VM1 is schedule to the control node, the corresponding tap device is TAP099CAA87-CD, and connected to bridge brq1762d312-d4.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489070030208.jpg "/>

The structure of the current vxlan100 is as follows:

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489233043751.jpg "/>

Continue to launch the instance cirros-vm2 in the same way, assigning the IP to 172.16.100.4.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489473056264.jpg "/>

The CIRROS-VM2 is schedule to the compute node, the corresponding tap device is TAP457CC048-AA, and connected to bridge brq1762d312-d4.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489603043136.jpg "/>

Because there is no HDCP service on the compute nodes, there is no corresponding tap device.
In addition, bridge's name is consistent with the control node, both Brq1762d312-d4, indicating the same network.

The structure of the current vxlan100 is as follows:

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026489804002274.jpg "/>

CIRROS-VM1 (172.16.100.3) and cirros-vm2 (172.16.100.4) are located in different nodes, connected by vxlan100, PING to verify connectivity below.
Ping 172.16.100.4 in the CIRROS-VM1 console

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026490208057732.jpg "alt=" Image609.png "/>

As we expected, the ping succeeded.

For routing and floating IPs between multiple Vxlan implementations are very similar to VLANs and are not covered here, see the previous VLAN section.

In the next section we discuss the mechanism for improving VXLAN efficiency-L2 Population.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20161113-1479026490402042486.jpg "alt=" Blob.png "/>

Deploy instance to VXLAN-5 minutes a day to play OpenStack (112)