
上QQ阅读APP看书,第一时间看更新
Configuring Neutron to use the VLAN type driver
The ML2 plugin needs to be configured in order to use VLAN as the network type for all the tenant networks.
Getting ready
The ML2 plugin has a configuration file setting that needs to be updated so that the tenants can use VLAN as the tenant network type.
How to do it…
The following steps will show you how to configure VLAN as the type driver and tenant network type:
- With the appropriate credentials, SSH into the node where the Neutron server is running. In our setup, it will be the Controller and Network node.
- Open the Neutron ML2 plugin configuration file using your desired editor. For example, the command for vi editor will be as follows:
openstack@controller:~$ sudo vi /etc/neutron/plugins/ml2/ml2_conf.ini
- In the
[ml2]
section of the file, configure VLAN as the type driver and network type:[ml2] ... type_drivers = vlan tenant_network_types = vlan
- Restart the Neutron and Open vSwitch services on the Controller and Network node of our setup, using the following commands:
openstack@controller:~$ sudo service neutron-server restart openstack@controller:~$ sudo service openvswitch-switch restart openstack@controller:~$ sudo service neutron-plugin-openvswitch-agent restart
- The first three steps have to be repeated for the compute node in our setup as shown previously. The command to restart OVS on the compute node is:
openstack@compute:~$ sudo service openvswitch-switch restart
How it works…
During the startup, the Neutron server will load the core plugin, which in our case is the ML2 plugin. As the ML2 plugin allows multiple types of networks, it uses type_drivers
to check which network type drivers to load. Finally, each tenant with a non-administrative role can use only certain network types. The tenant_network_types
attribute indicates the network types.