Setting up your cloud to work in a VLAN tagged environment.
VLAN Manager networking is the default networking mode in OpenStack. It provides a private network segment for each project’s instance that can be accessed via a dedicated VPN connection from the Internet.
When VLAN mode is configured, each project (or tenancy) has its own VLAN and network assigned to it. Any intermediary physical switches must, however support 802.1q VLAN tagging, for this to operate.
VlanManager tries to address two main flaws of flat managers, those being:
Virtual switches in our sandbox environment support, VLAN tagging.
To begin with, ensure you’re logged into the controller. If this was created using Vagrant, we can access this using the following command:
vagrant ssh controller
If using the controller host created in Starting Openstacek Comput, we will have three interfaces in our virtual instance:
eth0 is a NAT to the host running VirtualBox
eth1 is our floating (public) network (172.16.0.0/16)
eth2 is our fixed (private) network (10.0.0.0/8)
In a physical production environment, that first interface wouldn’t be present, and references to this NATed eth0 in the following section can be ignored.
To configure VLAN Manager carries out the following steps:
up ifconfig eth2 up
sudo /etc/init.d/networking restart
sudo restart nova-compute sudo restart nova-network
. novarc keystone tenant-list
This shows output like the following:
VLAN Manager networking is the default mode. For a private cloud environment, in networks accustomed to VLANs, this option is the most flexible. It allows for per-project and secure networking by using VLANs. If you do not have a — network_manager flag in your /etc/nova/nova.conf file, OpenStack Compute will default to VlanManager.
Creating the network is no different in any of the managers; in this instance, with VlanManager, the private network is assigned to a VLAN that is specified in the — vlan=100 option. We then associate this network and VLAN with our cookbook project, by specifying the ID of that tenant, using the –project.
On our OpenStack Compute host, this creates an interface named vlan100, which is the tagged interface to eth2, as specified in —vlan_interface from
Get Updates on Tech posts, Interview & Certification questions and training schedules