Open Stack

>> Unless you are running RDO which starts the daemon with a hardcoded --configfile to ovs_neutron_plugin.ini
>> As mentioned in the puppet review.
>I tested with Ubuntu Cloud Archive and it is the same.
>
>As you seem to have encountered this problem too, can you provide
>details about how you install OpenStack on RDO? Did you install and
>configure OpenStack with Packstack? What wasn't working? Which configs
>weren't read?

We are using our own puppet recipes to install/maintain OpenStack.
I just followed the documentation on how to use ML2:
http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-compute-node.html

Which says:
Create symlink from /etc/neutron/plugin.ini to /etc/neutron/plugins/ml2/ml2_conf.ini

After some wondering about why things did not work as expected I discovered that the daemon was not using the config file...

I also noticed I need to add the following to the ml2_conf to get it working with openvswitch (using vlans):
[ovs]
bridge_mappings = default:br-eth1

There is also the point that for security groups you need a placeholder firewall_driver to get it to work
 (which is in the docs but not in the included/upstream ml2 ini example file) :
[securitygroup]
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver (or some dummy value)

It seems that there is still some work left on documenting actual working configurations.
Usually I just go to the configfile example in github to look at all the possible options but, as said, that is far from the complete story:
https://github.com/openstack/neutron/blob/master/etc/neutron/plugins/ml2/ml2_conf.ini

Cheers,
Robert van Leeuwen