<div dir="ltr">Great link Lorin, thanks! I'll try Darragh's ideas today.</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/8/21 Lorin Hochstein <span dir="ltr"><<a href="mailto:lorin@nimbisservices.com" target="_blank">lorin@nimbisservices.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>Juan:</div>
<div>
<br>
</div>
<div>Check out this blog post from Darragh O'Reilly about how to configure access to the metadata service when not using the l3-agent:</div>
<div>
<br>
</div>
<div>
<span style="font-family:'.HelveticaNeueUI';font-size:15px;line-height:19px;white-space:nowrap"><a href="http://techbackground.blogspot.com/2013/06/metadata-via-dhcp-namespace.html?m=1" target="_blank">http://techbackground.blogspot.com/2013/06/metadata-via-dhcp-namespace.html?m=1</a></span>
</div>
<br>
<br>
<div style="display:block">
<br>
</div>
<div style="display:block">Lorin<br><div>—<br>Sent from <a href="https://www.dropbox.com/mailbox" target="_blank">Mailbox</a> for iPhone</div></div><div><div class="h5">
<br>
<span style="display:inline">On Wed, Aug 21, 2013 at 4:56 PM, Juan José Pavlik Salles <<a><u></u>jjpavlik@gmail.com<u></u>="mailto:jjpavlik@gmail.com"></a>> wrote:<br></span>
<blockquote class="gmail_quote">
<div dir="ltr">Hi guys, i'm trying to get my metadata working with quantum. I don't have L3-agent and i'm using provider network with ovs and vlans. So far i have quantum-dhcp working great and my VMs get IP with no problems, but during boot they get stuck trying to access to the metadata service.<div>
<br></div><div>Is it possible to access to the metadata service without using quantum-l3-agent? </div><div><br></div><div>My network node runs quantum-server, quantum-dhcp-agent, quantum-openvswitch-agent and quantum-metadata-service. I've configured metada_agent like this:</div>
<div><br></div><div><div>[DEFAULT]</div><div># Show debugging output in log (sets DEBUG log level output)</div><div>debug = True</div><div>verbose = True</div><div><br></div><div># The Quantum user information for accessing the Quantum API.</div>
<div>auth_url = <a href="http://172.19.136.1:35357/v2.0" target="_blank">http://172.19.136.1:35357/v2.0</a></div><div>auth_region = RegionOne</div><div>admin_tenant_name = service</div><div>admin_user = quantum</div><div>
admin_password = yedAA567</div>
<div><br></div><div># IP address used by Nova metadata server</div><div>####cambiar esto!!! a una IP balanceada, posiblemente 172.19.136.1</div><div>nova_metadata_ip = 172.19.136.12</div><div><br></div><div># TCP Port used by Nova metadata server</div>
<div>nova_metadata_port = 8775</div><div><br></div><div># When proxying metadata requests, Quantum signs the Instance-ID header with a</div><div># shared secret to prevent spoofing. You may select any string for a secret,</div>
<div># but it must match here and in the configuration used by the Nova Metadata</div><div># Server. NOTE: Nova uses a different key: quantum_metadata_proxy_shared_secret</div><div># metadata_proxy_shared_secret =</div><div>
metadata_proxy_shared_secret = XXXX</div><div><br></div><div>What else should i do? I still get </div><div><br></div><div> 20130821 20:29:36,057 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [22/120s]: http error [504]</div>
<div>20130821 20:29:45,117 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [31/120s]: http error [504]</div>
<div>20130821 20:29:55,181 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [41/120s]: http error [504]</div>
<div>20130821 20:30:04,241 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [50/120s]: http error [504]</div>
<div>20130821 20:30:14,308 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [60/120s]: http error [504]</div>
<div>20130821 20:30:23,369 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [69/120s]: http error [504]</div>
<div>20130821 20:30:34,436 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [80/120s]: http error [504]</div>
<div>20130821 20:30:43,505 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [89/120s]: http error [504]</div>
<div>20130821 20:30:54,577 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [101/120s]: http error [504]</div>
<div>20130821 20:31:03,636 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [110/120s]: http error [504]</div>
<div>20130821 20:31:12,648 util.py[WARNING]: '<a href="http://169.254.169.254/20090404/metadata/instanceid" target="_blank">http://169.254.169.254/20090404/metadata/instanceid</a>' failed [119/120s]: socket timeout [timed out]</div>
<div><br></div><div>during boots.</div><div><br></div><div>Somehow my network node should take this requests to 169.254.169.254, i have no idea how to do that. </div><div><br></div><div>Thanks!</div><div><div><br></div>-- <br>
<div dir="ltr">Pavlik Salles Juan José</div>
</div></div></div>
</blockquote>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Pavlik Salles Juan José</div>
</div>