Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/25/2014 12:45 PM, Raphael Ribeiro wrote:
> Hi Heiko, I already have done this too, unfortunately the error
> persists.

I faced very similar (quite likely the same) problem, and after some
wall-banging and help from this list got things going:

https://github.com/droopy4096/openstack-ng/tree/multinode

what you are interested in is under roles/neutron-*/templates and
roles/nova-*/templates (config file templates) and the rules that
apply those configs are under roles/*/tasks .

There were quite a few places I had to touch to get things going, but
in general:

* make sure neutron knows about nova and nova knows about neutron
* with RDO there is a workaround that I had to resort to which is to
play with vif_plugging* and neutron notification to nova: see thread
"neutron, nova and vif_plugging_* in nova.conf"
* DB configuration needs to be present in neutron plugin files (and it
looks like neutron.conf may not need it).
* ovs plugin still needs to be configured even though it looks like
you're only configuring ml2
* AMQP (in my case -qpid) pointers need to be present in all proper places
* keystone pointers need to be populated everywhere

My templates are straight copies from RDO configs with values plugged
in, so if you're using RDO - run the diff to see what needs changing.

If you're brave enough - you can try to run above ansible-playbook to
set things up in a VM and inspect the result if you have CentOS 6.x
image around. I'm still working on that stuff so things are rough
around the edges and some are plain non-implemented, however keystone,
glance, nova and neutron seem to be working as expected (I can spin up
networks and VMs attached to them and route them out via public
interface no problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTqyboyDrVuGfS98QRAkm5AJ9qmsfs2MYbGte73RWTUIWGMQozzQCguw+2
2rfrM74h1k+BrH/yWeWyM8g=
=E2cl
-----END PGP SIGNATURE-----

-- 
    This communication is intended for the use of the recipient to whom it
    is addressed, and may contain confidential, personal, and or privileged
    information. Please contact us immediately if you are not the intended
    recipient of this communication, and do not copy, distribute, or take
    action relying on it. Any communications received in error, or
    subsequent reply, should be deleted or destroyed.
---