Create OVS Local Network-Play 5 minutes a day OpenStack (129)

In the previous section we completed the preparation of the OVS, and this section starts with the most basic local network.
The local network is not connected to any of the host's physical network cards, and traffic is limited to the host, and no VLAN ID is associated with it.

Create the first local network

Below we create the local network through the Web GUI.

Go to menu Admin-Networks and click on the "Create Network" button.

The Create page is displayed.

"Provider Network Type" select "Local", click "Create Network", First_local_net created successfully.

Click on the First_local_net link, go to the Network Configuration page, there is no subnet, click the "Create Subnet" button.

Set the IP address to "172.16.1.0/24".

Click "Next".

Tick "Enable DHCP" and the IP pool is set to "172.16.1.2,172.16.1.99". Click "Create" and the subnet is created successfully.

At the same time Devstack-controler the DHCP service for this subnet is already Active.

what has changed in the underlying network?

The process of creating a OVS local network is no different from Linux Bridge.
This is because Neutron has abstracted different driver, but the underlying implementation is definitely a difference.
So, let's figure out what's changed in the underlying network.

Open the shell terminal of the control node and use Ovs-vsctl Show to view the status of the current open vSwitch.

You can see that Neutron automatically created port "Tap7970bdcd-f2" on the Br-int Bridge.

It is known from the name that the port corresponds to the DHCP interface of local_net.

Like Linux bridge driver, DHCP devices are also placed in namespaces.

The network structure is as follows:

In the next section we will deploy instance to first_local_network and look again at the changes in this network topology diagram.

Create OVS Local Network-Play 5 minutes a day OpenStack (129)