Vish, if you could help.
I realized that all internal route of my vms point to cloudcontroller. if I
change the default route to node address everything works perfectly.
How can I make the node IP the default route?
Thanks for all help!
On Wed, Dec 19, 2012 at 2:34 PM, Gui Maluf
Found out!
I'd a /etc/dnsmasq-nova.conf file defining the default route as my
controller node! now everything is working perfectly! :D
On Thu, Dec 20, 2012 at 11:07 AM, Gui Maluf guimal...@gmail.com wrote:
Vish, if you could help.
I realized that all internal route of my vms point to
There should be a redirect in iptables from 169.254.169.254:80 to $my_ip:8775
(where nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
b) if you do
sudo iptables -t nat -L -n v
do you see the forward rule? Is it getting hit properly?
Vish
On Dec 19, 2012, at
On Wed, Dec 19, 2012 at 1:13 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
There should be a redirect in iptables from 169.254.169.254:80 to
$my_ip:8775 (where nova-api-metadata is running)
So:
a) can you
curl $my_ip:8775 (should 404)
CloudController and Nodes awnser in the same
Are you sure your network has multi_host = True? It seems like it isn't, since
the gateway listed by the guest is 10.5.5.32
In multi_host mode each node should be getting an ip from the fixed range and
the guest should be using that as the gateway.
Vish
On Wed, Dec 19, 2012 at 1:13 PM,
Yes, it's in multi_host=true. In nova.conf and in the database multi_host
is set to True. 10.5.5.32 isn't the gateway, instead is the private network.
LoL
Out of nothing my instances can now reach metadata. But when I login and
ping www.google.com VM can resolv name but there is no answer back,
6 matches
Mail list logo
