Connect instance to second_local_net-5 minutes a day to play with OpenStack (85)

Today is the last section of the local network, and we will verify the connectivity of the two local network.

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

The IP assigned to the CIRROS-VM3 is 172.16.1.102.

The CIRROS-VM3 is schedule to the control node, and the corresponding tap device is tap5395d19b-ed.

The console shows that CIRROS-VM3 has successfully received the IP address 172.16.1.102 from DHCP.

But CIRROS-VM3 cannot Ping to CIRROS-VM1.

This is expected because CIRROS-VM3 and CIRROS-VM1 are located in different local networks and are not connected, even if both are located on the same host.

The network structure is as follows:

Summary

Here the local network knowledge point has been discussed, make a summary of it.

1. Instance in the same local network can communicate.
2. Instance in a different local network cannot communicate.
3. A local network can be located in only one physical node and cannot span nodes.


local network can be used as a starting point for learning more complex network types such as flat, VLANs, Vxlan, etc. Reduce the learning difficulty of Neutron.

Connect instance to second_local_net-5 minutes a day to play with OpenStack (85)