Figured this out. In stack.sh, when creating the quantum subnets, the VM image below was creating them with dhcp disabled. I added that to the quantum network using the subnet-update command, rebooted the VM, and it got an IP address.
Kaneko, FYI in case you want to respin the VM images. Thanks, Kyle On Oct 26, 2012, at 11:35 AM, Kyle Mestery (kmestery) <[email protected]> wrote: > Thanks Jason, it seems similar to this. Since I'm running from devstack, I > don't > have a /etc/init/quantum-dhcp-agent.conf file. I checked though, and there are > 2 instances of quantum-dhcp-agent running on the host (see below), but none > are running for the right network. Still trying to debug why this is. > > On Oct 26, 2012, at 11:03 AM, Jason Long <[email protected]> wrote: > >> Hi Kyle maybe this is related? Its just a shot in the dark. >> >> https://lists.launchpad.net/openstack/msg16842.html >> >> >> On 10/26/12 8:53 AM, Kyle Mestery (kmestery) wrote: >>> I may have found the problem. I have 2 Quantum networks, and I don't see a >>> DHCP >>> server running on one of them. See below: >>> >>> ubuntu@ryu1:~/devstack$ quantum subnet-list >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> | id | name | cidr | >>> allocation_pools | >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> | 51a4e945-6566-4559-9cc3-4c6466dbd4cb | | 10.0.0.0/24 | >>> {"start": "10.0.0.2", "end": "10.0.0.254"} | >>> | 62123ffa-f094-4054-abee-c7f2f766521d | | 192.168.100.0/24 | >>> {"start": "192.168.100.2", "end": "192.168.100.254"} | >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> ubuntu@ryu1:~/devstack$ quantum subnet-show >>> 62123ffa-f094-4054-abee-c7f2f766521d >>> +------------------+------------------------------------------------------+ >>> | Field | Value | >>> +------------------+------------------------------------------------------+ >>> | allocation_pools | {"start": "192.168.100.2", "end": "192.168.100.254"} | >>> | cidr | 192.168.100.0/24 | >>> | dns_nameservers | | >>> | enable_dhcp | False | >>> | gateway_ip | 192.168.100.1 | >>> | host_routes | | >>> | id | 62123ffa-f094-4054-abee-c7f2f766521d | >>> | ip_version | 4 | >>> | name | | >>> | network_id | eedd4b41-b232-4370-8a1c-786a128638f6 | >>> | tenant_id | e95a7aa5d1e74ebd8914c7d4900447ab | >>> +------------------+------------------------------------------------------+ >>> ubuntu@ryu1:~/devstack$ >>> >>> When I do a "ps auxw|grep dhcp", I only see one running for the first >>> network with addresses >>> in the 10.0.0.0/24 channel. >>> >>> ubuntu@ryu1:~/devstack$ quantum subnet-list >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> | id | name | cidr | >>> allocation_pools | >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> | 51a4e945-6566-4559-9cc3-4c6466dbd4cb | | 10.0.0.0/24 | >>> {"start": "10.0.0.2", "end": "10.0.0.254"} | >>> | 62123ffa-f094-4054-abee-c7f2f766521d | | 192.168.100.0/24 | >>> {"start": "192.168.100.2", "end": "192.168.100.254"} | >>> +--------------------------------------+------+------------------+------------------------------------------------------+ >>> ubuntu@ryu1:~/devstack$ quantum subnet-show >>> 62123ffa-f094-4054-abee-c7f2f766521d >>> +------------------+------------------------------------------------------+ >>> | Field | Value | >>> +------------------+------------------------------------------------------+ >>> | allocation_pools | {"start": "192.168.100.2", "end": "192.168.100.254"} | >>> | cidr | 192.168.100.0/24 | >>> | dns_nameservers | | >>> | enable_dhcp | False | >>> | gateway_ip | 192.168.100.1 | >>> | host_routes | | >>> | id | 62123ffa-f094-4054-abee-c7f2f766521d | >>> | ip_version | 4 | >>> | name | | >>> | network_id | eedd4b41-b232-4370-8a1c-786a128638f6 | >>> | tenant_id | e95a7aa5d1e74ebd8914c7d4900447ab | >>> +------------------+------------------------------------------------------+ >>> ubuntu@ryu1:~/devstack$ >>> >>> Any ideas? >>> >>> Thanks, >>> Kyle >>> >>> On Oct 26, 2012, at 9:41 AM, Kyle Mestery (kmestery) <[email protected]> >>> wrote: >>> >>>> Hi Kaneko: >>>> >>>> I was able to confirm no IP address by logging into the console and doing a >>>> "ifconfig eth0" on the VM. Further, I followed your steps below, and in >>>> step #1, >>>> there is no IP assignment given to the VM. Running the ping with the >>>> specified >>>> netns failed as well. Also, my VMs were assigned addresses in the >>>> 192.168.100.x/24 >>>> address space, which was different from yours. Not sure if that matters. >>>> >>>> Like I said, I suspect that perhaps there is something odd about my setup >>>> since I've >>>> ported your images to VirtualBox, but I can't quite figure out what that >>>> is. Anything else >>>> for me to look at? >>>> >>>> Thank you for the help! >>>> >>>> Kyle >>>> >>>> On Oct 26, 2012, at 2:35 AM, Yoshihiro Kaneko <[email protected]> >>>> wrote: >>>> >>>>> Hi Kyle, >>>>> >>>>> How did you confirm that IP address was not given to VM? >>>>> Please confirm with the following command. >>>>> >>>>> 1. see console output of VM >>>>> >>>>> $ nova console-log vm1 | tail -30 >>>>> Initializing random number generator... done. >>>>> Starting network... >>>>> udhcpc (v1.18.5) started >>>>> Sending discover... >>>>> Sending select for 10.0.0.3... >>>>> Lease of 10.0.0.3 obtained, lease time 120 >>>>> deleting routers >>>>> route: SIOCDELRT: No such process >>>>> adding dns 10.0.0.2 >>>>> cloud-setup: checking >>>>> http://169.254.169.254/2009-04-04/meta-data/instance-id >>>>> cloud-setup: successful after 1/30 tries: up 14.29. iid=i-00000001 >>>>> wget: server returned error: HTTP/1.1 404 Not Found >>>>> failed to get http://169.254.169.254/latest/meta-data/public-keys >>>>> Starting dropbear sshd: generating rsa key... generating dsa key... OK >>>>> ===== cloud-final: system completely up in 15.15 seconds ==== >>>>> instance-id: i-00000001 >>>>> public-ipv4: >>>>> local-ipv4 : 10.0.0.3 >>>>> wget: server returned error: HTTP/1.1 404 Not Found >>>>> cloud-userdata: failed to read user data url: >>>>> http://169.254.169.254/2009-04-04/user-data >>>>> WARN: /etc/rc3.d/S99-cloud-userdata failed >>>>> ____ ____ ____ >>>>> / __/ __ ____ ____ / __ \/ __/ >>>>> / /__ / // __// __// /_/ /\ \ >>>>> \___//_//_/ /_/ \____/___/ >>>>> http://launchpad.net/cirros >>>>> >>>>> >>>>> login as 'cirros' user. default password: 'cubswin:)'. use 'sudo' for >>>>> root. >>>>> cirros login: >>>>> >>>>> >>>>> 2. ping to VM on network namespace >>>>> >>>>> $ ip netns >>>>> qrouter-223854b4-ef25-4f65-b32f-254418dbb439 >>>>> qdhcp-729be6af-188f-4174-b889-0789bfa87d4a >>>>> $ >>>>> $ sudo ip netns exec qrouter-223854b4-ef25-4f65-b32f-254418dbb439 ping >>>>> 10.0.0.3 >>>>> PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data. >>>>> 64 bytes from 10.0.0.3: icmp_req=1 ttl=64 time=2.05 ms >>>>> 64 bytes from 10.0.0.3: icmp_req=2 ttl=64 time=0.926 ms >>>>> 64 bytes from 10.0.0.3: icmp_req=3 ttl=64 time=0.875 ms >>>>> 64 bytes from 10.0.0.3: icmp_req=4 ttl=64 time=0.885 ms >>>>> ^C >>>>> --- 10.0.0.3 ping statistics --- >>>>> 4 packets transmitted, 4 received, 0% packet loss, time 3001ms >>>>> rtt min/avg/max/mdev = 0.875/1.186/2.059/0.504 ms >>>>> ubuntu@ryu1:~/devstack$ ping 10.0..0.3 >>>>> ping: unknown host 10.0..0.3 >>>>> >>>>> >>>>> Thanks, >>>>> Kaneko >>>>> >>>>> 2012/10/26 Isaku Yamahata <[email protected]>: >>>>>> On Fri, Oct 26, 2012 at 02:03:42AM +0000, Kyle Mestery (kmestery) wrote: >>>>>>> On Oct 24, 2012, at 5:33 AM, Yoshihiro Kaneko <[email protected]> >>>>>>> wrote: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I made devstack VM image for Ryu and OpenStack Folsom. Using this VM >>>>>>>> image, anyone can easily try Ryu and OpenStack. >>>>>>>> Instructions for this pre-configured VM image: >>>>>>>> https://github.com/osrg/ryu/wiki/RYU-OpenStack-Folsom-environment-VM-image-file-HOWTO >>>>>>>> Japanese: >>>>>>>> https://github.com/osrg/ryu/wiki/RYU-OpenStack-Folsom-environment-VM-image-file-Japanese-HOWTO >>>>>>>> URL for downloading VM image file is described in this document. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Kaneko >>>>>>> >>>>>>> Kaneko: >>>>>>> >>>>>>> I have ported this image to VirtualBox by using qemu-img to convert it >>>>>>> to vmdk, and then >>>>>>> importing it into VirtualBox. I then created 2 host only networks to >>>>>>> mimic the public/private >>>>>>> libvirt networks you specify. I was able to add 3 NICs to each of the 2 >>>>>>> VMs I created from >>>>>>> the image, adding the public net as network 1, the private net as >>>>>>> network 2, and a NAT >>>>>>> network (to get to the outside world) as network 3. I can bring >>>>>>> devstack up on each one, >>>>>>> and that works ok. The problem is, when I spin a VM up, it never gets >>>>>>> an IP address. I suspect >>>>>>> this may be because in your setup, libvirt has a DHCP server on one of >>>>>>> the networks >>>>>>> used by the VMs. I was thinking of running dnsmasq on the controller >>>>>>> node to alleviate this >>>>>>> problem when utilizing the images on VirtualBox, but I can't figure out >>>>>>> which interface to run >>>>>>> this on. With the latest OpenStack code, there's far too many layers of >>>>>>> indirection going on. >>>>>>> Any idea which interface I should run the dnsmasq instance with on the >>>>>>> controller node? >>>>>> Kaneko-san will give more detailed information, though. >>>>>> quantum-dhcp-agent takes care of starting/stopping dnsmasq. So we don't >>>>>> have >>>>>> to start/stop dnsmasq manually. >>>>>> -- >>>>>> yamahata >>>> >>>> ------------------------------------------------------------------------------ >>>> Everyone hates slow websites. So do we. >>>> Make your web apps faster with AppDynamics >>>> Download AppDynamics Lite for free today: >>>> http://p.sf.net/sfu/appdyn_sfd2d_oct >>>> _______________________________________________ >>>> Ryu-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/ryu-devel >>> >>> ------------------------------------------------------------------------------ >>> The Windows 8 Center >>> In partnership with Sourceforge >>> Your idea - your app - 30 days. Get started! >>> http://windows8center.sourceforge.net/ >>> what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ >>> _______________________________________________ >>> Ryu-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/ryu-devel >> >> >> ------------------------------------------------------------------------------ >> The Windows 8 Center >> In partnership with Sourceforge >> Your idea - your app - 30 days. Get started! >> http://windows8center.sourceforge.net/ >> what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ >> _______________________________________________ >> Ryu-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/ryu-devel > > > ------------------------------------------------------------------------------ > The Windows 8 Center > In partnership with Sourceforge > Your idea - your app - 30 days. Get started! > http://windows8center.sourceforge.net/ > what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel ------------------------------------------------------------------------------ The Windows 8 Center In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
