OpenStack parameters
Here’s a set of parameters for OpenStack deployment
Management VLAN (BLUE)
Management IP Pool
Management VLAN Ports
(used for openstack management traffic)
Data Ports
(used by tenants)
199
192.168.199.0/24
12,13,14,15
44,45,46,47
# Create the virtual network for OpenStack traffic
CLI (network-admin@aquila25) > vnet-create name openstack-mgmt scope fabric vlans 99
vnet-mgr-storage-pool pool-disk4
Use DHCP for bringing up the nodes:
# Create the IP pool
CLI (network-admin@aquila25) > ip-pool-create name openstack-mgmt-pool vnet openstackmgmt start-ip 192.168.99.1 end-ip 192.168.99.254 netmask 24 plan 99
Pool created successfully
# Create DHCP for OpenStack nodes (compute and controller nodes)
CLI (network-admin@aquila25) > dhcp-create name openstack-mgmt-dhcp vnet openstack-mgmt
initial-ip-pool openstack-mgmt-pool
# Create OpenStack instance
this creates OpenStack agent running on the switch and reserves VLANs (1000-2000 in this case) to be used by
the OpenStack controller.
CLI (network-admin@aquila25) > openstack-create name openstack-centos vnet openstack-mgmt
port 25000 vlans 1000-2000 release havana
# openstack-controller-create command and the associated options
CLI (network-admin@aquila25) > help openstack-controller-create
openstack-controller-create
name name-string
between 0 and 2 of the following options:
extensions|no-extensions
storage-pool storage-pool name
any of the following options:
storage storage-number
# Create the controller
CLI (network-admin@aquila25) > openstack-controller-create name openstack-centos storage 100G extensions
Note the initial prep for setting up the OpenStack infrastructure remains the same. The last command
‘OpenStack-controller-create’ is interesting. If we dissect this further, this command performs heavy lifting
and enables the administrator to deploy a built in Centos OpenStack controller (customizes the controller based
on some of the parameters provided, configures the different OpenStack control components, installs the
Pluribus OpenStack plugin, attaches storage etc). This whole process takes around 10-15 minutes. While we
don’t expect this to be exactly what is required in a deployment, it provides administrators a foundation to start
tweaking OpenStack.
With the OpenStack controller configured, the compute nodes can be PXE-booted using the on-board Centos
images and the Pluribus OpenStack installer would ensure that compute nodes are automatically configured (to
be a part of the OpenStack setup)
The end-result on the CLI is shown below (as the nodes are added to the OpenStack deployment, they are
visible in the CLI along with their status information):
CLI (network-admin@ aquila25) > openstack-node-show
openstack-name hostname
addr
type
status
---------------------------------------------------------------------------------------------------openstack-centos controller
192.168.199.2 controller
online
openstack-centos
compute-192-168-199-3
192.168.199.3
compute
online
openstack-centos
compute-192-168-199-5
192.168.199.5
compute
online