BTW security group/rule are open for SSH access from outside of
openstack setup. Also, when we assign floating IPs to these unreachable
instances, we are able to access instance from outside. So to summarize,
query is how to configure quantum to make sure assigned project subnet
is reachable from outside of openstack setup/network? In traceroute we
see that traffic is routed correctly till quatum node but quatum doesn't
add any route for assigned project subnets in IP tables (but only for
floating range).
On 4/18/2013 1:43 PM, Aniket wrote:
Hello All,
We want help with Quantum config issue we are facing. We have
basically multi node deployment of openstack insternally (Essex
release). Quantum is on separate node and we have OVS plugin deployed.
We have entire 10.43.0.0/16 routable to our openstack setup and we use
10.43.10.X/24 for all openstack nodes. We want to have this config
such that every project/user will have dedicated subnet allocated
(e.g. one user will have 10.43.20.X and other can have 10.43.30.X and
so on). While we are able to create such a config, we find that when
user launches instances, he gets DHCP IPs in his allocated subnet for
the project but this instance IP is not reachable from outside of
quantum node. We have quantum's (virtual) router created/added for
10.43.10.x/24 subnet.
Are we missing anything obvious? Any pointers?
Thanks,
Aniket
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp