Openstack Dashboard is a lot more than just an interface to our instances. It allows an administrator to configure environments, Users, and tenants.
Tenants are known as Projects within the OpenStack Dashboard. Adding new tenants that users can be members of is achieved quite simply in OpenStack Dashboard. For a VLAN MANAGED environment, it also involves assigning an appropriate private network to that new tenant by using the console. To do this, we must log into OpenStack Dashboard as a user with admin privileges and also log in to Shell on our OpenStack Controller API server.
Load a Web browser, point it to our OpenStack Dashboard address at http://172.16.0.200/horizon, and log in as a user, such as the demo user created in Adding Users recipe of Keystone Openstack Identity Service, with the password openstack.
If using the VLAN Manager under Nova network, we need to run some commands to tie our VLAN private networks to our tenants as this isn’t possible under the OpenStack Dashboard. To do this, log on to a shell on our Controller host. If this was created using Vagrant run the following command:
vagrant ssh controller
To add a new tenant to our OpenStack environment, carry out the following steps:
If our OpenStack environment has been set up by using the VLAN Manager in /etc/nova/nova.conf (the default when nothing is specified), run the following command in the Shell on our OpenStack Controller server:
This creates an IP range on a specific VLAN that we have associated with our horizon tenant. Once successful, our new tenant is available to use.
OpenStack Dashboard is a feature rich interface that complements the command-line options available to you when managing our OpenStack environment. This means we can simply create a tenant (Ubuntu’s interface refers to this a project), to which users can belong to, within OpenStack Dashboard.
When creating new tenants under a VLAN Manager configured OpenStack network, we assign an IP address range and specific VLAN ID to this tenant. If we assign a new VLAN, please ensure you configure your hardware switches accordingly, so that the private network can communicate by using this new VLAN ID. Note that we use the following parameters with nova-manage, the command used when configuring a network to match our new tenant:
What we have done is, named this private network appropriately, matching our tenancy. We have created a new VLAN so that traffic is encapsulated in a new VLAN, separating this traffic from other tenants. We finally specified the ID of the tenancy that was returned when we created the tenant through OpenStack Dashboard.
Get Updates on Tech posts, Interview & Certification questions and training schedules