Create OVS vlan101 and deploy instance-5 minutes a day to play with OpenStack (139)

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

before we created the OVS vlan100 and deployed instance, today continue creating vlan101.

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

The subnet IP address is 172.16.101.0/24.

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

What has changed in the underlying network

Neutron automatically creates an interface "tap1820558c-0a" vlan100 DHCP on the Br-int bridge.

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

Now, the network structure is as follows:

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

Connect the instance to the VLAN101

Launch new instance "CIRROS-VM3", network selection vlan101.

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

The IP assigned to the CIRROS-VM3 is 172.16.101.103.

650) this.width=650; "Src=" http://7xo6kd.com1.z0.glb.clouddn.com/ Upload-ueditor-image-20170117-1484632053655003094.png "alt=" Image615.png "/>

The CIRROS-VM3 is schedule to the compute node and the virtual network card is connected to the Br-int.

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

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

The current network structure is as follows:

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

The CIRROS-VM1 is located in the control node and belongs to vlan100.
The cirros-vm2 is located in the compute node and belongs to vlan100.
The CIRROS-VM3 is located in the compute node and belongs to vlan101.

CIRROS-VM1 and cirros-vm2 are in vlan100, and they can communicate.
CIRROS-VM3 in vlan101, unable to communicate with CIRROS-VM1 and CIRROS-VM2.

The above conclusions are beyond doubt, but we need to be more concerned about:
How does the Open vSwitch implement vlan100 and vlan101 isolation ?

We will analyze the problem in detail in the next section.

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

Create OVS vlan101 and deploy instance-5 minutes a day to play with OpenStack (139)