Clarification on docs for self service connectivity
I followed the install guide for Liberty on CentOS to the letter and can boot an instance on a self-service network, but I can _not_ communicate with that instance (other than directly through its netns on the compute node itself).
Looking at the self-service connectivity diagram at
http://docs.openstack.org/liberty/ins...
I traced over the network connectivity and all interfaces I see in my setup match the one in the docs with one EXCEPTION... what I do not see is the qg to public-bridge port tap pair going from the qrouter namespace, in my case my qrouter namespace shows only the private vNIC interface that is connected to the private bridge (see http://paste.openstack.org/show/483298/), so my public and private networks are essentially isolated.
Can you shed some light on what may be going on?
None of the neutron logs show relevant issues. I have also tried creating the veth pair manually and inserting them but somehow it didn't seem to be sufficient to route the traffic from the public to private nets.
I'm also attaching the output of iptables -L -t nat on the controller node as well as against the router namespace http://paste.openstack.org/show/483299/), I'd be happy to provide more details as this has been bugging me for some time now.
Thanks!
Update: Oddly enough I can get connectivity if I create a unicast vxlan channel between the controller and compute node, which leads me to think that the connectivity issue I encountered was with the obscure l2population and vxlan drivers, does anyone have any insights on how the vxlan net is setup
I think l2pop is still not generally recommended for usage. Do you have a very specific need to enable the driver? If not, you may be better off avoiding it.