<div dir="ltr">Well, I'm giving it up.<div><br><div>It is almost "impossible" to enable metadata with Folsom / Quantum / Single Flat...</div><div style><br></div><div style>I tried everything...</div><div style>
<br></div><div style>Even this do not help me:</div><div style><br></div><div style>Folsom-Quantum-metadata server issue:<br></div><div style><a href="https://answers.launchpad.net/quantum/+question/218237">https://answers.launchpad.net/quantum/+question/218237</a><br>
</div></div><div style><br></div><div style>Since I have now a working Quantum (without metadata) PoC, I'll try Grizzly from now... Unless someone help me more! =P</div><div style><br></div><div style>Now I'll take a look into this: <a href="http://cloudistic.me/blog/hacking-together-metadata-support-when-using-folsom-with-grizzly-quantum/">http://cloudistic.me/blog/hacking-together-metadata-support-when-using-folsom-with-grizzly-quantum/</a> - but, with Grizzly G3 + RC1...</div>
<div style><br></div><div style>Tks,</div><div style>Thiago</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 14 March 2013 18:21, Narayan Desai <span dir="ltr"><<a href="mailto:narayan.desai@gmail.com" target="_blank">narayan.desai@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Make sure that the metadata server has a route back to the VM. Traffic<br>
hitting that NAT rule ensures that data is flowing properly in one<br>
direction, but you need to make sure bits can flow back to establish a<br>
tcp connection. We had this problem running multiple nova-network<br>
servers.<br>
-nld<br>
<br>
On Thu, Mar 14, 2013 at 2:28 PM, Martinx - $B%8%'!<%`%:(B<br>
<div class="HOEnZb"><div class="h5"><<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>> wrote:<br>
> Daneyon,<br>
><br>
> Thanks! But, I'm not using L3, or GRE, or namespaces...<br>
><br>
> I read the<br>
> <a href="http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html" target="_blank">http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html</a><br>
> and I don't think my setup (Single Flat, no GRE, no L3) fits that case...<br>
><br>
> From my understandings, I'm not using overlapping IP's, since it is<br>
> disabled by default... Anyway, after forcing `allow_overlapping_ips to<br>
> False', nothing happens...<br>
><br>
> From the compute node, I can connect to metadata by running: `telnet<br>
> 10.32.14.232 8775' and / or `telnet 10.32.14.234 8775', both answer but,<br>
> doesn't work in the end...<br>
><br>
> I tried with metadata @ 10.32.14.232 (controller) and @ 10.32.14.234<br>
> (compute node with `nova-api-metadata') but, same broken result.<br>
><br>
> From within my instance, when I run: `telnet 169.254.169.254 80', I can see<br>
> the packages passing trough the NAT rule `169.254.169.254 tcp dpt:80<br>
> to:<a href="http://10.32.14.232:8775" target="_blank">10.32.14.232:8775</a>' but, the telnet connection times up.<br>
><br>
> Do I need the package `quantum-plugin-metaplugin' instead<br>
> `nova-api-metadata'? If yes, where, controller or on each compute node?<br>
><br>
> BTW, if I set `use_namespaces = False' in dhcp_agent.ini, my Instances<br>
> doesn't boots up anymore.<br>
><br>
> Maybe it is time to go with Grizzly RC1?<br>
><br>
> Anyway, I would like to finish everything I can with Quantum in Folsom,<br>
> before going to try Grizzly...<br>
><br>
> I really appreciate your help!!<br>
><br>
> Regards,<br>
> Thiago<br>
><br>
><br>
> On 14 March 2013 15:21, Daneyon Hansen (danehans) <<a href="mailto:danehans@cisco.com">danehans@cisco.com</a>><br>
> wrote:<br>
>><br>
>><br>
>> Take a look at the limitations section of the Quantum docs. You will need<br>
>> to set allow overlapping IP's to false and make sure you have bidirectional<br>
>> network connectivity between the metadata ip and the tenant private<br>
>> network(s). The L3 agent.ini also should be configured with the metadata<br>
>> ip. The docs cover these topics in more detail.<br>
>><br>
>> Regards,<br>
>> Daneyon Hansen<br>
>><br>
>> On Mar 14, 2013, at 12:11 PM, "Martinx - $B%8%'!<%`%:(B"<br>
>> <<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>> wrote:<br>
>><br>
>> Hi!<br>
>><br>
>> My Quantum Single Flat is almost working!<br>
>><br>
>> My Instance get an IPv4 without any problem but, the metadata isn't<br>
>> working...<br>
>><br>
>> What can I do?<br>
>><br>
>> My compute node have the `nova-api-metadata' package, nova.conf have<br>
>> `metadata_host = 10.32.14.234', the iptables `169.254.169.254' NAT rule is<br>
>> there too...<br>
>><br>
>> The Instance log shows:<br>
>><br>
>> Starting network...<br>
>> udhcpc (v1.20.1) started<br>
>> Sending discover...<br>
>> Sending select for 10.33.14.3...<br>
>> Lease of 10.33.14.3 obtained, lease time 120<br>
>> deleting routers<br>
>> route: SIOCDELRT: No such process<br>
>> adding dns 8.8.4.4<br>
>> adding dns 8.8.8.8<br>
>> cirros-ds 'net' up at 1.84<br>
>> checking <a href="http://169.254.169.254/2009-04-04/instance-id" target="_blank">http://169.254.169.254/2009-04-04/instance-id</a><br>
>> failed 1/20: up 1.87. request failed<br>
>> failed 2/20: up 13.98. request failed<br>
>> failed 3/20: up 26.02. request failed<br>
>> failed 4/20: up 38.06. request failed<br>
>> failed 5/20: up 50.09. request failed<br>
>> failed 6/20: up 62.13. request failed<br>
>> failed 7/20: up 74.16. request failed<br>
>> failed 8/20: up 86.20. request failed<br>
>> failed 9/20: up 98.24. request failed<br>
>> failed 10/20: up 110.27. request failed<br>
>> failed 11/20: up 122.31. request failed<br>
>> failed 12/20: up 134.34. request failed<br>
>> failed 13/20: up 146.38. request failed<br>
>> failed 14/20: up 158.41. request failed<br>
>> failed 15/20: up 170.45. request failed<br>
>> failed 16/20: up 182.49. request failed<br>
>> failed 17/20: up 194.52. request failed<br>
>> failed 18/20: up 206.56. request failed<br>
>> failed 19/20: up 218.59. request failed<br>
>> failed 20/20: up 230.63. request failed<br>
>> failed to read iid from metadata. tried 20<br>
>> no results found for mode=net. up 242.66. searched: nocloud configdrive<br>
>> ec2<br>
>> failed to get instance-id of datasource<br>
>> Starting dropbear sshd: generating rsa key... generating dsa key... OK<br>
>><br>
>> Any clue?<br>
>><br>
>> Thanks!<br>
>> Thiago<br>
>><br>
>><br>
>> On 13 March 2013 10:10, Daneyon Hansen (danehans) <<a href="mailto:danehans@cisco.com">danehans@cisco.com</a>><br>
>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> Regards,<br>
>>> Daneyon Hansen<br>
>>><br>
>>><br>
>>> On Mar 13, 2013, at 1:04 AM, "Martinx - $B%8%'!<%`%:(B"<br>
>>> <<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>> wrote:<br>
>>><br>
>>> Guys,<br>
>>><br>
>>> Here:<br>
>>> <a href="http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html" target="_blank">http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html</a><br>
>>><br>
>>> ...at the step "1. Install the L2 agent." but, what is the name of the<br>
>>> Ubuntu package (I'm using Folsom)?<br>
>>><br>
>>> ...apt-get install what?<br>
>>><br>
>>><br>
>>> quantum-plugin-openvswitch-agent<br>
>>><br>
>>><br>
>>> I thought that the Quantum L2 agent was the package<br>
>>> `quantum-plugin-linuxbridge' but, this doc uses OpenvSwitch... So, I'm<br>
>>> confused now...<br>
>>><br>
>>><br>
>>> As you know Quantum uses plugins to realize the network abstractions.<br>
>>> Some plugins (such as OVS) use an agent to collect information from the<br>
>>> Quantum db to implement the logical data model on the local vswitch.<br>
>>><br>
>>><br>
>>> The following packages "quantum-server quantum-plugin-openvswitch<br>
>>> quantum-plugin-openvswitch-agent quantum-dhcp-agent" will be enough for my<br>
>>> `controller+network node'?<br>
>>><br>
>>> That should work for flat networking implementations.<br>
>>><br>
>>><br>
>>> At the compute-node, I'll install only the<br>
>>> "quantum-plugin-openvswitch-agent", right?<br>
>>><br>
>>> Correct. That package should install the openvswitch and other<br>
>>> dependencies.<br>
>>><br>
>>><br>
>>> Tks,<br>
>>> Thiago<br>
>>><br>
>>><br>
>>> On 13 March 2013 00:58, Martinx - $B%8%'!<%`%:(B <<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Daneyon,<br>
>>>><br>
>>>> Thank you for your time! I'll check it!<br>
>>>><br>
>>>> I read that guide from Cisto once... Too complex.<br>
>>>><br>
>>>> I also, tried the following guides too, appears to be like the one from<br>
>>>> Cisco:<br>
>>>><br>
>>>><br>
>>>> <a href="https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst" target="_blank">https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst</a><br>
>>>><br>
>>>> and:<br>
>>>><br>
>>>> <a href="https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst" target="_blank">https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst</a><br>
>>>><br>
>>>><br>
>>>> Anyway, at first, I do not want L3 or GRE. Only the most basic setup<br>
>>>> (Flat / L2).<br>
>>>><br>
>>>> Do you know if my `controller+network node' server eth0 needs to be<br>
>>>> promisc?<br>
>>>><br>
>>>> Tks!<br>
>>>> Thiago<br>
>>>><br>
>>>><br>
>>>> On 13 March 2013 00:49, Daneyon Hansen (danehans) <<a href="mailto:danehans@cisco.com">danehans@cisco.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>> Make sure the quantum-dhcp and l3 agents are running and properly<br>
>>>>> configured. It sounds like either the q-dhcp agent is not functioning or<br>
>>>>> connectivity between the dhcp agent and vm is not functioning. If using GRE<br>
>>>>> tunnels, test connectivity between the tunnel endpoints. You should also<br>
>>>>> see the IP's of your tunnel peers in ovs-vsctl show. If your instance<br>
>>>>> spawns successfully, console into it and manually assign an IP and ping the<br>
>>>>> q-l3-agent and q-dhcp agent. You can follow this guide for deploying<br>
>>>>> Quantum with OpenvSwitch using GRE tunnels:<br>
>>>>><br>
>>>>><br>
>>>>> <a href="http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install" target="_blank">http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install</a><br>
>>>>><br>
>>>>> Regards,<br>
>>>>> Daneyon Hansen<br>
>>>>><br>
>>>>> From: Martinx - $B%8%'!<%`%:(B <<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>><br>
>>>>> Date: Tuesday, March 12, 2013 8:14 PM<br>
>>>>> To: "<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>" <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>>,<br>
>>>>> "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"<br>
>>>>> <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
>>>>> Subject: Re: [Openstack-operators] Help with simplest Quantum setup<br>
>>>>> possible...<br>
>>>>><br>
>>>>> Well,<br>
>>>>><br>
>>>>> Just for the record, I'll stick with Quatum + OpenvSwtich... Someone<br>
>>>>> on IRC told me that it is the best way to go with Quantum.<br>
>>>>><br>
>>>>> I'm still needing help to set it up (Single Flat / multi=false, still<br>
>>>>> the same simplest topology).<br>
>>>>><br>
>>>>> OpenvSwitch is already working, bridges `br-int' and `br-eth0'<br>
>>>>> created...<br>
>>>>><br>
>>>>> My main problem, I think, is that my Instances doesn't get an IP (they<br>
>>>>> supposed to be at 10.33.14.X/24).<br>
>>>>><br>
>>>>> Everything else seems to be working as expected, no apparent errors on<br>
>>>>> the logs... quantum net-create / subnet-create worked...<br>
>>>>><br>
>>>>> I appreciate any help, tips or docs!<br>
>>>>><br>
>>>>> Best!<br>
>>>>> Thiago<br>
>>>>><br>
>>>>><br>
>>>>> On 12 March 2013 23:34, Martinx - $B%8%'!<%`%:(B <<a href="mailto:thiagocmartinsc@gmail.com">thiagocmartinsc@gmail.com</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> Hi!<br>
>>>>>><br>
>>>>>> Sorry about the double posting... I need help! :-P<br>
>>>>>><br>
>>>>>> I'm trying, without any kind of success, to deploy OpenStack with<br>
>>>>>> Quantum on its simplest scenario, I think, which is `Single Flat' with<br>
>>>>>> `Linux Bridge' plugin.<br>
>>>>>><br>
>>>>>> My topology is:<br>
>>>>>><br>
>>>>>> 1 firewall with 2 ethX (eth0 public, eth1 10.32.14.1 and 10.33.14.1)<br>
>>>>>> 1 controller with 1 eth0 (<a href="http://10.32.14.232/24" target="_blank">10.32.14.232/24</a> gateway 10.32.14.1)<br>
>>>>>> 1 node with 1 eth0 (<a href="http://10.32.14.234/24" target="_blank">10.32.14.234/24</a> gateway 10.32.14.1)<br>
>>>>>><br>
>>>>>> Instances Network:<br>
>>>>>> <a href="http://10.33.14.0/24" target="_blank">10.33.14.0/24</a> (Instances gateway must be 10.33.14.1, same router of<br>
>>>>>> the physical servers above, NOT its own host hypervisor).<br>
>>>>>><br>
>>>>>> I'm trying this:<br>
>>>>>><br>
>>>>>><br>
>>>>>> <a href="http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html" target="_blank">http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html</a><br>
>>>>>> - doesn't work... Even enabling OpenvSwith (but I don't want it for now,<br>
>>>>>> only Quantum instead of nova-network, with Linux Bridge for the sake of<br>
>>>>>> simplicity).<br>
>>>>>><br>
>>>>>> The following guide help me a lot (with Nova Network everything is<br>
>>>>>> fine): <a href="http://openstack-folsom-install-guide.readthedocs.org/en/latest/" target="_blank">http://openstack-folsom-install-guide.readthedocs.org/en/latest/</a> -<br>
>>>>>> I'm trying to follow it, by replacing nota-network instructions, for Quantum<br>
>>>>>> instructions but, doesn't work...<br>
>>>>>><br>
>>>>>> Any docs or tips?<br>
>>>>>><br>
>>>>>> NOTE: I do not want any kind of NAT (like nova-network multi=true) or<br>
>>>>>> `Floating IPs' within my Cloud Computing environment.<br>
>>>>>><br>
>>>>>> Thanks!<br>
>>>>>> Thiago<br>
>>>>><br>
>>>>><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-operators mailing list<br>
>>> <a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
>><br>
>><br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<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>
</div></div></blockquote></div><br></div>