Access to extranet ML2 configuration-5 minutes a day to play OpenStack (103)

Communication between instance in different VLANs can be achieved through router.

The next question to be explored is how instance communicates with the external network.

The external network here refers to a network outside the tenant network. A tenant network is a network created and maintained by Neutron. The external network is not created by Neutron. In the case of a private cloud, the external network usually refers to the corporate intranet, and if it is a public cloud, the external network usually refers to the Internet.

specifically to our experimental network environment: compute nodes and Control nodes ETH1 provides a tenant network, and IP segment tenants are free to set up. The control node eth2 connection is the external network, the IP network segment is 10.10.10.0/24. As shown in the following:

Configuration Preparation

In order to connect to an external network, you need to tell the Neutron the type of external network and the corresponding physical network card in the configuration file. Because an external network is a physical network that already exists, it is generally a flat or VLAN type.

Here we name the label for the external network "external". If the type is flat, the control node/etc/neutron/plugins/ml2/ml2_conf.ini is configured as follows:

If the type is VLAN, configure the following:

After you modify the configuration, you need to restart the neutron related services.

In our network environment, the external network is the flat type. In the next section we will show you how to create an external network ext_net.

Access to extranet ML2 configuration-5 minutes a day to play OpenStack (103)