Heyup good folk of OpenStack,<br>I'm having the same issue as Sina. My configuration seems to look OK (I have an instance, with IP that can ping its default route to on an internal network) but I get the failure to contact the metadata server with the explanation that Sina gave.<br>
<br>In my /var/log/quantum/l3_agent.log I have the following: <a href="http://paste.openstack.org/show/24801/">http://paste.openstack.org/show/24801/</a><br>There's also a paste of an iptables output that I would've expected to see the DNAT rules in.<br>
<br>What am I missing?<br><br>Cheers,<br>Kev<br><div class="gmail_extra"><br><br><div class="gmail_quote">On 7 November 2012 14:35, Choe, Cheng-Dae <span dir="ltr"><<a href="mailto:whitekid@gmail.com" target="_blank">whitekid@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">- DNAT rule to metadata server is done by l3_agent. but your node configuration has no l3_agent<div>
- and metadata_ip configuration can find l3_agent.ini.<br><div><br><div><div><div>2012. 11. 7., 오후 9:15, Sina Sadeghi <<a href="mailto:sina@aptira.com" target="_blank">sina@aptira.com</a>> 작성:</div><br><blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000">
<font size="-1">Hello all,<br>
<br>
<font size="-1"><div><div class="h5">I thought I would giv</div></div><font size="-1">e quantum a
shot <font size="-1">and I've got a 50-60% work<font size="-1">ing configuration<font size="-1">, but having
trouble understanding where to go from here as the docs
are <font size="-1">pretty sparse.<div><div class="h5"><br>
<br>
<font size="-1">Ubuntu 12.04.1 + "ubuntu cloud
archive" <font size="-1">folsom repo</font></font><br>
<br>
</div></div><font size="-1"><div><div class="h5">node A: nova-api, nova-scheduler,
quantum-server, quantum-plug</div></div><font size="-1">in-openvswitch<br>
<font size="-1"><div><div class="h5">node B: nova-compute,
nova-api-metadata, quantum-dhcp-agent<font size="-1"><font size="-1">, quantum-plug<font size="-1">in-openvswitch-agent</font><br>
node C: nova-compute, </font></font></div></div><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1">nova-api-metadata,
quantum-dhcp-agent<font size="-1"><font size="-1">,
quantum-plug<font size="-1">in-openvswitch-agent<br>
<br>
configured as
follows:<br>
<br>
<font size="-1">quantum.conf:<br>
<font size="-1"><div><div class="h5">...<br>
core_plugin =
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2<br>
...<br>
<br>
</div></div><font size="-1">ovs_quantum_plugin.ini:<br>
<font size="-1">...</font><br>
<font size="-1"><div><div class="h5">tenant_network_type=vlan<br>
network_vlan_ranges
=
default:2000:3999<br>
</div></div><font size="-1">integration_bridge
= br-int<br>
<font size="-1">bridge_mappings
=
default:br-eth3<br>
<font size="-1">...<br>
<br>
<font size="-1">node
B,C `ovs-vstl
list-br`:<font size="-1"><br>
br-eth3<br>
br-int<br>
<br>
<font size="-1"><div><div class="h5">node
B,<font size="-1">C
`ovs-vsctl
list-ports
br-int`:<font size="-1"><br>
<font size="-1">int-br-eth3
(created by
quantum?)</font><br>
</font></font><br>
</div></div><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1"><font size="-1">node
B,<font size="-1">C
`ovs-vsctl
list-ports
br-eth3`:<br>
<font size="-1">eth3
(added by me)</font><br>
<font size="-1">phy-br-eth3
(created by
quantum?)<br>
<br>
<font size="-1"><div><div class="h5">eth3
is <font size="-1">a
NIC which is
connected to a
<font size="-1">switchport
accept<font size="-1">ing
VLAN
2000:3999. It
has no IP
assigned
currently.</font></font></font><br>
<br>
When I start <font size="-1">the
<font size="-1">12.04
ubuntu
"cloud-image"</font></font>
in the
dashboard, it
successfully
boots and
obtains an IP
address as
seen in the co</div></div><font size="-1">nsole
output:<br>
<font size="-1"><div><div class="h5">cloud-init-nonet
waiting 120
seconds for a
network
device.<br>
<br>
ci-info: lo
: 1
127.0.0.1
255.0.0.0
.<br>
ci-info: eth0
: 1
192.168.253.5
255.255.255.0
fa:16:3e:80:33:71<br>
ci-info:
route-0:
0.0.0.0
192.168.253.1
0.0.0.0
eth0 UG<br>
ci-info:
route-1:
192.168.253.0
0.0.0.0
255.255.255.0
eth0 U<br>
<br>
However,
immediately
after that
output I see
this<br>
<br>
</div></div><font size="-1"><div><div class="h5">2012-11-07
11:27:29,598 -
util.py[WARNING]:
'<a href="http://169.254.169.254/2009-04-04/meta-data/instance-id" target="_blank">http://169.254.169.254/2009-04-04/meta-data/instance-id</a>'
failed
[3/120s]: url
error [[Errno
113] No route
to host]<br>
<br>
<font size="-1">which
runs until it
times out.</font><br>
<br>
In older
versions of </div></div><font size="-1">OpenStack,
when I ran
'iptables<font size="-1">-save
| grep 169<font size="-1">.2<font size="-1">54.169.254'
on a <font size="-1">metadata</font>
server I was
used to seeing
a rule show <font size="-1">up
which
translate<font size="-1">d</font>
that 169
address to the
<font size="-1">variable
assigned by
meta<font size="-1">data_host
in nova.conf</font></font>,
but <font size="-1">I
note that <font size="-1">ru<font size="-1">le
doesn't show
up</font></font>
in this
version of
nova? I added
the old rule
in (to see
what would
happen<font size="-1">)
but the result
was the same<font size="-1">,
still no route
to ho<font size="-1">st.</font></font></font><div><div class="h5"><br>
<br>
What<font size="-1"> <font size="-1">steps
do I need to
take here to <font size="-1">allow
my instance to
retrieve its
metadata? I</font></font></font><font size="-1">s my
quantum
misconfigured
somehow?</font>
Perhaps </div></div><font size="-1">I
need to go
back and
reconfigure m<font size="-1">y
switch port (<font size="-1">for
example, there
is no <font size="-1">real
192.168.253.1
gw, but does
the<font size="-1">re
need to be for
the instance
to sim<font size="-1">ply
fetch metdata)</font></font></font>?
<font size="-1">After
that, what
steps do I
need to take
to get the VM
connected to <font size="-1">the
rest of the
world<font size="-1">? <font size="-1">Is
the<font size="-1">
quantum-l3-agent
the onl<font size="-1">y
real choice
right now?<br>
<br>
<font size="-1">Thx.</font><br>
</font></font><br>
<div>-- <br>
<font face="Helvetica"><div><div class="h5"><br>
--<br>
<b>Sina Sadeghi</b><br>
Lead Cloud Engineer<br>
</div></div><span><logo.jpg></span><div class="im"><br>
<b>Aptira Pty Ltd</b><br>
1800 APTIRA<br>
<a href="http://www.aptira.com/" target="_blank">aptira.com</a><br>
<a href="https://twitter.com/#/aptira" target="_blank">Follow @aptira</a><br>
</div></font><br>
</div>
</font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Kevin Jackson<br>@itarchitectkev<br>
</div>