Clone this wiki locally
See all, Barclamp List
This is a Creole document
The Nova barclamp provides a set of roles and recipes to install the Openstack Diablo compute system. The barclamp attempts to allow for integration with the other barclamps to provide a whole Openstack compute environment.
The Nova barclamp depends upon a mysql, keystone, and glance instances.
The Network Barclamp provides two roles. nova-multi-controller provides the access points and control functions of Nova. The scheduler, vnc-proxy, and api services run from this role. The nova-multi-controller also builds a rabbitmq server for the system to use. nova-multi-compute provides the compute services for Nova. Depending upon networking mode, the network and api services will be deployed upon both roles.
The barclamp provides a single nova cookbook. The cookbook is used for nova service construction.
The barclamp has the following parameters:
|MySQL||See 1||The instance of the MySQL barclamp to use for database|
|Keystone||See 1||The instance of the Keystone barclamp to use for identity|
|Glance||See 1||The instance of the Glance barclamp to use for image services|
|Verbose||true||Turn on nova debugging to the logs|
|Hypervisor||kvm||The hypervisor to choose from. Options are kvm or qemu|
|Use Tenant Vlans||false||Should Nova networking use VLans for each tenant.|
|DHCP Enabled||true||Should Nova hand out addresses by DHCP|
|High Availability Enabled||true||Should Nova use HA networking mode|
|Allow Same-Network Traffic||true||Network security option that isolates VMs from same network traffic|
|Number of Networks||1||The number of sub-networks to split the nova-fixed network into from the network barclamp|
|Network Size||256||The number of addresses in a single network|
- The system will build a list of barclamps and present them in the UI. The field is the string name of the instance.
- The Number of Networks times the Network Size should equal the total address space specified by nova-fixed in the Network barclamp.
Nova gives you the option to specify one of two hypervisors. kvm is used for real hardware and will take advantage of hardware acceleration. If Crowbar is running in virtual machines, Nova can still be used, but the qemu hypervisor will need to be used.
Nova has 5 networking modes. They are described in the following table.
|Tenant Vlans||DHCP Enabled||High Availablity||Description|
|false||false||false||This was known as Flat mode. It is one flat network with address injection to Ubuntu guests. Nova network runs on the controller node only|
|false||true||false||This is known as Flat-DHCP mode. It is the same as flat network mode, but dns-masq is used to DHCP boot guests.|
|false||true||true||This is known as HA Flat-DHCP mode. It used DHCP to inject addresses into the guests. Nova network and api are run on all nodes to make sure that routing works.|
|true||true||false||This is known as DHCP-VLAN Mode. It creates N number of networks of size X from the nova-fixed address range. The controller node acts as a router for each network. A custom vlan is created for each network.|
|true||true||true||This is HA DHCP-VLAN Mode. It is the same as DHCP-VLAN mode, but we run with HA settings and put nova-network and nova-api on each node and handle routing from the compute nodes.|
<Add Vish's picture here>
The Nova barclamp assumes that there is a functioning MySQL, Keystone, and Glance instance. The Nova barclamp does minimal setup and uses the keystone default users for initial access. The barlcamp also assumes that the Nova Dashboard Barclamp will be used to customize the deployment.
Useful Commands and Information
See the Nova guide at http://docs.openstack.org/diablo/openstack-compute/admin/content/ or the Nova Dashboard.
Limitations and/or Futures