Your OpenStack environment must have an efficient, scalable, and manageable network infrastructure that addresses your immediate business needs and future growth. All nodes must communicate with each other through allocated networks.
Understanding the networking configuration options helps you design the best configuration for your Compute instances.
You can choose to either install and configure nova-network or use the OpenStack Networking service (neutron).
Tenants in OpenStack are a way of keeping user’s cloud resources separate and are also referred to as projects within Nova Network. In a tenant, there are a number of images, instances, and its own network resources assigned to it. When we create a tenant, we assign it its own VLAN with its own private and public ranges. For example, we may wish to create a development tenancy that is separate from the performance testing tenancy and live tenancies.
Nova Networking uses the phrase project, which is synonymous to tenants created with keystone, as such the two terms are interchangeable when referring to projects.
To begin with, ensure you’re logged in to the Controller server (our OpenStack VirtualBox Virtual Machine, controller, created in Starting Openstack Compute ). If this was created using Vagrant you can log into this box using the following command:
vagrant ssh controller
In order to configure per-project (tenant) IP ranges, carry out the following steps:
1. First, on our keystone client, list the current projects, as follows:
This returns a list of projects in our example.
keystone tenant-create --name=development
An example of running the previous command is shown as follows:
Creating IP address ranges for projects is done as part of creating new projects (tenants). We first create the project, which returns an ID that we use when creating that network, using the following syntax:
Get Updates on Tech posts, Interview & Certification questions and training schedules