[Openstack] Devstack Grizzly networking help needed

Jake G. dj_dark_junglist at yahoo.com
Fri Aug 2 07:19:18 UTC 2013

HI Salvatore, 

Thank you for your reply and sorry for being a pain in the butt. 
What I really need help with is the initial setup in the localrc file. I dont really understand how each piece works.

The internal network can be any ip range and gateway, but I do not understand the public network part.

Does the floating range have to match the subnet that my eth0 ip is on?
if I specify the floating range to devstack still gives me a gateway starting 172.x.x.x that is configured in br-ex interface

Does it not matter what the floating range ips are?

This is my localrc file. Can you tell me where I am going wrong first before we get into the serious troubleshooting? Thank you soo much!





disable_service n-net
enable_service q-svc
enable_service q-agt
enable_service q-dhcp
enable_service q-l3
enable_service q-meta
enable_service quantum
enable_service q-lbaas


 From: Salvatore Orlando <sorlando at nicira.com>
To: Jake G. <dj_dark_junglist at yahoo.com> 
Sent: Friday, August 2, 2013 3:51 PM
Subject: Re: [Openstack] Devstack Grizzly networking help needed

The fact that you do not get addresses from the dhcp server has little to do with the floating IP range, and getting a 172.x.x.x network when no range is specified is the default behaviour.
If you refer to 'public network' to the one where you're going to create floating IPs, then usually addresses are not distributed by DHCP there.

The fact that you do not get DHCP addresses on the private network, on a simple setup like the single-host one, might mean we need to look at failures in openstack services rather than devstack configuration issues.

I assume that you're using neutron (this is what I recall from your previous posts), and that the following servcies are running in devstack (check if they crashed too!).
1) quantum-server
2) quantum-agent
3) quantum-dhcp-agent
4) quantum-l3-agent
5) quantum-meta

1) Check the NICs on your instance; if you don't find any then perhaps the interface driver in nova is not working - set NOVA_VIF_DRIVER to nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver in your localrc (this should be the default value anyway) - or go to nova.conf and set libvirt_vif_driver to the above value
2) If the NICs are present, verify they're being plugged into br-int. Otherwise either check again nova's libvirt_vif_driver, or check if you have br-int at all! If you don't then probably openvswitch-switch is not running and this is likely to be your issue
3) If all the interfaces are up and running, we should focus on why DHCP traffic is being dropped. One reason might be the DHCP agent is not responding at all. Verify that you do not have errors in the DHCP agent log
4) If none of the above bullets helps you, then you can try and boot to vms and give them manually the address neutron selected for them, and then see if you have connectivity. Then we will be able to say whether we need to look at a DHCP problem or a general connectivity issue.


On 2 August 2013 07:37, Jake G. <dj_dark_junglist at yahoo.com> wrote:

HI all, Another day of failed attempts to get this right. Would appreciate any help you can give. Its been almost 3 weeks and I haven't been able to get past this point.
>I have an All-in-one Devstack grizzly deployment here, but I cannot get the networking right no matter how I configure it.
>My Physical Host NIC settings are:
>auto eth0
>iface eth0 inet static
>        address
>        netmask
>        network
>        broadcast
>        gateway
>#Secondary network not connected to anything(cable not plugged in)
>auto eth1
>        iface eth1 inet manual
>        up ifconfig $IFACE up
>        up ip link set $IFACE promisc on
>        down ip link set $IFACE promisc off
>        down ifconfig $IFACE down
>What should my localrc file correctly look like? I really dont understand this. Should the floating IPs be on the same subnet as my host IP?
>for example, HOST_IP= with the GW       FLOATING_RANGE=
>if I dont configure any ips ranges then I always get a 172. IP for my public network and my instances do not get a IP from DHCP services.
>Thank you for your help
>Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to     : openstack at lists.openstack.org
>Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130802/778d784e/attachment.html>

More information about the Openstack mailing list