<html><head><style data-externalstyle="true">
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
</style><style><!--
.EmailQuote {
padding-left:4pt;
margin-left:1pt;
border-left-color:rgb(128, 0, 0);
border-left-width:2px;
border-left-style:solid;
}
--></style></head><body><div data-externalstyle="false" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:16px;"><div>OK, I included the ‘q-meta’ service in the Devstack localrc, stopped and completely removed the packages (and associated files) installed by Devstack on the machine, and reinstalled Devstack. I do now see the ’q-meta’ service running in the screen log files. I also added a rule to iptables’ nat table to DNAT 169.254.169.254:80 to <host_ip>:8775. However, when I start an Ubuntu UEC image, I’m still getting time outs on the URL for the metadata:</div><div><a href="http://paste.openstack.org/show/29010/">http://paste.openstack.org/show/29010/</a></div><div> </div><div>Am I still doing something wrong? I still have Quantum with overlapping ranges enabled, but I took Mark’s response below to mean that Devstack with ‘q-meta’ would handle this...</div><div data-focusfrompointer="true"> </div><div data-focusfrompointer="true">Thanks,</div><div data-focusfrompointer="true">Will</div><div> </div> <div style="border-top-color: rgb(225, 225, 225); border-top-width: 1px; border-top-style: solid;" data-focusfrompointer="true"> <strong>From:</strong> Will Dennis<br> <strong>Sent:</strong> January 3, 2013 5:05 PM<br> <strong>To:</strong> Mark McClain<br> <strong>CC:</strong> openstack@lists.launchpad.net<br> <strong>Subject:</strong> Re: [Openstack] VMs not able to contact metadata service<br> </div> <div> </div>
<font size="2"><span style="font-size: 10pt;"><div class=" PlainText">Thanks for your response, Mark. Can you confirm that the 'q-meta'<br>
service works in Devstack if Devstack was installed about a week or two<br>
ago (we do have the 'RECLONE=yes' option set in localrc) or must we pull<br>
latest from git again?<br>
<br>
Best,<br>
Will<br>
<br>
-----Original Message-----<br>
From: Mark McClain [<a tabindex="-1" href="mailto:mark.mcclain@dreamhost.com">mailto:mark.mcclain@dreamhost.com</a>] <br>
Sent: Thursday, January 03, 2013 12:55 PM<br>
To: Will Dennis<br>
Cc: openstack@lists.launchpad.net<br>
Subject: Re: [Openstack] VMs not able to contact metadata service<br>
<br>
Will-<br>
<br>
The metadata service in Folsom will only work when overlapping IP ranges<br>
are disabled (see:<br>
<a tabindex="-1" href="http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limit">http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limit</a><br>
ations.html). For Grizzly, we have added metadata service for<br>
overlapping networks. This feature is currently available in devstack<br>
when you enable the q-meta service.<br>
<br>
mark<br>
<br>
On Jan 2, 2013, at 11:10 PM, Willard Dennis <wdennis@nec-labs.com><br>
wrote:<br>
<br>
> Hello all,<br>
> <br>
> I am running Folsom with Quantum v2, via Devstack. Am trying to use<br>
Ubuntu UEC image to spawn VMs, but when the VM instance boots, it is not<br>
able to contact the metadata server in order to (among other things)<br>
inject the public key needed in order for me to be able to SSH into the<br>
instance. See <a tabindex="-1" href="http://paste.openstack.org/show/28764/">http://paste.openstack.org/show/28764/</a> for a log snippet<br>
if needed.<br>
> <br>
> Following the (incorrect, bug reported) instructions found at<br>
<a tabindex="-1" href="http://docs.openstack.org/folsom/openstack-compute/admin/content/configu">http://docs.openstack.org/folsom/openstack-compute/admin/content/configu</a><br>
ring-openstack-compute-basics.html#enabling-access-to-vms-on-the-compute<br>
-node (search for "If you want to use the 10.04 Ubuntu Enterprise Cloud<br>
images" to get to the instructions, and change the metadata port from<br>
the incorrect '8773' to the correct '8775') I added the rule into<br>
iptables, with no luck... I still cannot reach the metadata server at<br>
169.254.169.254:80. When I dump the iptables rules for the 'nat' table,<br>
I see that my added rule is being hit, but it's still not working:<br>
> <br>
> $ sudo iptables -t nat -L -v -n<br>
> Chain PREROUTING (policy ACCEPT 982 packets, 159K bytes)<br>
> pkts bytes target prot opt in out source<br>
destination <br>
> 210 27054 nova-compute-PREROUTING all -- * * 0.0.0.0/0<br>
0.0.0.0/0 <br>
> 17 1020 DNAT tcp -- * * 0.0.0.0/0<br>
169.254.169.254 tcp dpt:80 to:xxx.xx.xx.xx:8775 <<<<< (target IP<br>
addr redacted)<br>
> 3078 520K nova-api-PREROUTING all -- * * 0.0.0.0/0<br>
0.0.0.0/0<br>
> <br>
> I searched and found this thread from this list: <br>
> <a tabindex="-1" href="http://www.mail-archive.com/openstack%40lists.launchpad.net/msg16569.htm">http://www.mail-archive.com/openstack@lists.launchpad.net/msg16569.htm</a><br>
> l Does this mean that the Nova metadata service cannot be used with <br>
> Quantum when using multiple tenant networks (L3 arch)? (this is the <br>
> model that Devstack implements in my setup) If the above is true, can <br>
> I revert to another supported configuration (and kindly give me a <br>
> pointer as to how?) Finally, any plans to fix the metadata service so <br>
> that it will work with Quantum's L3 service, and enable this out of <br>
> the box with Devstack? (dare to dream :)<br>
> <br>
> Thanks and regards,<br>
> Will<br>
> _______________________________________________<br>
> Mailing list: <a tabindex="-1" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> Post to : openstack@lists.launchpad.net<br>
> Unsubscribe : <a tabindex="-1" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
> More help : <a tabindex="-1" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a tabindex="-1" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
Post to : openstack@lists.launchpad.net<br>
Unsubscribe : <a tabindex="-1" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
More help : <a tabindex="-1" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
</div></span></font>
</div></body></html>