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