openstack team mailing list archive

[<Gregory_Althaus@xxxxxxxx>]

Hi,

I've checked in an updated barclamp for nova.  This has options cleaned up and simplified (I think).  Paul and I have been working on the networking options.

There are now six networking options and three proposal references.  That is all the config that you really need to mess with on working with Nova.  Most can be defaulted.  I need to think about this a little more.

The three proposal references:
Glance,
Keystone,
Mysql

You need one of each those before you can run nova.  The create proposal routine will take the first of them if they exist.  You should be able to take the defaults on all of the barclamps to get a running system. (mysql, keystone, glance, nova_dashboard, nova should work).

The six network options are:
dhcp_enabled - true - Tells nova to run dhcpmasq to hand out addresses.  The other method uses injection to put the address into the system (this only works for Ubuntu guests).
tenant_vlans - true -Tells nova to use custom vlans for each keystone tenant.  The networks are automatically assigned until they are exhausted.
ha_enabled - true - Tells nova to run the system in HA networking mode.  This means run a network and an api service on each compute node to remove a single point of failure issue.

num_networks - 1 - Tells nova the number of networks that can be carved out of nova-fixed network
network_size - 256 - The size of the networks to carve out.  This should be a power of two number.

allow_same_net_traffic - false - Tells nova to allow same net traffic among vms on the same net.  The default is more secure.  You can use security groups to get around some of this.

NOTES:
While the first three options define 8 possible modes, only 6 are actually useable.  If tenant_vlans is true, then dhcp_enabled must be true as well.  Nova doesn't have a concept of running custom vlans without DHCP.

The num_networks and network_size need to define a network scheme that is contained in the nova_fixed network.  The default nova_fixed is a class C address space (256 addresses).  This means that 1 256 address network can be defined, or 2 128 address networks, or 4 64 address networks, ....   Making the nova_fixed address space bigger or smaller will require changes to these two variables.

Thanks,
Greg