Connect instance to flat_net-5 minutes a day to play with OpenStack (88)

In the previous section we created "Flat_net", which will deploy instance and verify connectivity in this network.

Launch the new instance "CIRROS-VM1", select Network Falt_net.

The IP assigned to the CIRROS-VM1 is 172.16.1.103.

The CIRROS-VM1 is schedule to the control node, the corresponding tap device is TAPC1875C7F-CB, and is already connected to bridge.

The structure of the current flat_net is as follows:

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

The CIRROS-VM2 is schedule to the compute node, the corresponding tap device is tapfb3fb197-24, and connected to bridge.

Here are two points to remind:

1. Because there is no HDCP service on the compute nodes, there is no DHCP-corresponding tap device in Brctl show.

2. The name of bridge on the compute node is consistent with the control node, both BRQF153B42F-C3, indicating the same network.

The structure of the current flat_net is as follows:

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

As we expected, the ping succeeded.

Flat network. The next section will begin in-depth discussion of the many previous sessions involved:
Instance how do I get IP from the Neutron DHCP service?

Connect instance to flat_net-5 minutes a day to play with OpenStack (88)