waiting for metadata service at http://169.254.169.254/2009-04-04/meta-data/instance-id
My architecture:
Host "Jack" Machine : nova-API , nova-objecstore , MySql [eth0:172.16.2.78]
Host "Absolut" Machine: nova-networkk , nova-scheduler [eth0:172.
Host "Dewars" Machine: nova-compute [eht0:192.168.2.2]
http://
=======
--dhcpbridge_
--dhcpbridge=
--logdir=
--state_
--verbose
--s3_host=
--rabbit_
--cc_host=
--ec2_url=http://
--fixed_
--network_size=256
--FAKE_
--routing_
--verbose
--sql_connectio
--network_
=======
My project network is 172.16.2.0/24 1 256
I use same nova.conf in three machine............
I can run up instance on nova-compute nocde Dewars(where is my expectation)
That means nova-scheduler works correctly.
But I can not ssh into instance , so I "euca-get-
Following is the abnormal point:
<pre>
wget: can't connect to remote host (169.254.169.254): Network is unreachable
cloud-userdata: failed to read instance id
===== cloud-final: system completely up in 40.92 seconds ====
wget: can't connect to remote host (169.254.169.254): Network is unreachable
wget: can't connect to remote host (169.254.169.254): Network is unreachable
wget: can't connect to remote host (169.254.169.254): Network is unreachable
instance-id:
public-ipv4:
local-ipv4 :
=> First-Boot Sequence:
</pre>
so check iptables-save
<pre>
# Generated by iptables-save v1.4.4 on Fri Mar 11 16:07:04 2011
*filter
:INPUT ACCEPT [155611:12350389]
:FORWARD ACCEPT [37385:4028058]
:OUTPUT ACCEPT [293426:20445095]
:nova-local - [0:0]
-A FORWARD -j nova-local
-A FORWARD -o br100 -j ACCEPT
-A FORWARD -i br100 -j ACCEPT
-A FORWARD -i eth1 -j ACCEPT
COMMIT
# Completed on Fri Mar 11 16:07:04 2011
# Generated by iptables-save v1.4.4 on Fri Mar 11 16:07:04 2011
*nat
:PREROUTING ACCEPT [3154:373388]
:POSTROUTING ACCEPT [950:58074]
:OUTPUT ACCEPT [758:47011]
:SNATTING - [0:0]
-A POSTROUTING -s 172.16.2.0/24 -d 172.16.2.0/24 -j ACCEPT
-A POSTROUTING -s 172.16.2.0/24 -d 10.128.0.0/24 -j ACCEPT
-A POSTROUTING -o eth0 -j MASQUERADE
-A POSTROUTING -j SNATTING
-A SNATTING -s 172.16.2.0/24 -j SNAT --to-source 172.16.2.78
COMMIT
# Completed on Fri Mar 11 16:07:04 2011
</pre>
"-A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 172.16.2.79:8773"
I think this line is wrong , nova-api is on 172.16.2.78
=======
I try to rewrite linux_net.py , fixed matadata destination address to 172.16.2.78:8773
At this time , on Dewars(
#curl http://
root@Dewars:
1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04
=======
And run up several instance , try to get console out put .....
there's something different from before....
it's "url error"
cloud-init running: Fri, 11 Mar 2011 08:54:08 +0000. up 65.26 seconds
waiting for metadata service at http://
08:54:08 [ 1/100]: url error [[Errno 101] Network is unreachable]
08:54:09 [ 2/100]: url error [[Errno 101] Network is unreachable]
08:54:10 [ 3/100]: url error [[Errno 101] Network is unreachable]
08:54:11 [ 4/100]: url error [[Errno 101] Network is unreachable]
08:54:12 [ 5/100]: url error [[Errno 101] Network is unreachable]
08:54:13 [ 6/100]: url error [[Errno 101] Network is unreachable]
08:54:15 [ 7/100]: url error [[Errno 101] Network is unreachable]
=======
Should I set any other --flag in nova.conf to match my architecture?
does my hardware architecture is wrong for NOVA ?
Does anyone success to isolate nova-network? if so , could you plz show me your nova.conf ?
=======
My install procedure:
Host "Jack"
https:/
but delete packages "nova-network" and "nova-scheduler" in script
Host "Absolut"
install package "nova-network" , "nova-scheduler" , "dnsmasq" , "python-mysqldb" , "bridge-utils"
Host "Dewars"
https:/
=======
Question information
- Language:
- English Edit question
- Status:
- Expired
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: