I am currently seeing that if the VM tries to connect to the meta-data server during bootup, its not able to connect. I believe this is because we are not yet doing the iptables configuration for this, but just wanted to confirm.
Thanks!
devstack support for l3 hasn't merged yet, so this isn't supposed to work quite yet.
hi sumit, are you using quantum v1 or v2? If v1, this should work, as the nova-network gateway device should have the nat rule set. If v2, then yes, this won't work until the l3-gateway stuff i'm working on lands. Will have it available for review monday, I hope :)
hi sumit, are you using quantum v1 or v2? If v1, this should work, as the nova-network gateway device should have the nat rule set. If v2, then yes, this won't work until the l3-gateway stuff i'm working on lands. Will have it available for review monday, I hope :)
Thanks Dan, yeah this is using v2. Just wanted to confirm that my understanding is right! :-)
Dan
Should this work with the latest devstack and folsom code? I tried with code from yesterday and still see the metadata problems when VM's are spun up with Quantum.
Eoghan
Can someone give an update on this? Is this working? I am still having issues.
I have got latest devstack as of 09/10/2012 and also defined Q_META_DATA_IP variable to local N-API server. I am just trying 1 node config only.
See the stack.sh is calling
quantum router-gateway-set $ROUTER_ID $EXT_NET_ID
I see the router and exteneral gatway but do not see any NAT rules created.
Asked: 2012-08-02 18:09:48 -0600
Seen: 86 times
Last updated: Sep 11 '12
