[Openstack] Instance IP assignment problem

Vaze, Mandar Mandar.Vaze at nttdata.com
Fri May 4 13:10:42 UTC 2012


Emilien,

Please see https://answers.launchpad.net/quantum/+question/194111

Nova-compute and nova-network on two different machines seems to be the key here.
Solution is proposed in the above thread.

Hope that helps.

-Mandar

From: openstack-bounces+mandar.vaze=nttdata.com at lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata.com at lists.launchpad.net] On Behalf Of Emilien Macchi
Sent: Thursday, May 03, 2012 1:26 PM
To: Salman Malik
Cc: openstack at lists.launchpad.net
Subject: Re: [Openstack] Instance IP assignment problem

Hi,


As I told you, I have also a problem for instance IP assignement.


My architecture :

I use Quantum with OVS plugin on 2 servers Essex-1 & Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent & nova-compute only.

You can see more details here<https://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf>.

My configurations files are here<https://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files> and in my documentation.



Problem Description :

When an instance is created in ESSEX-1, all is working (network).

But when the VM is started on ESSEX-2, it does not get an IP address. (log file<http://paste.openstack.org/show/14775/>)

I'm sure the problem comes from OVS connection with ESSEX-1.


Do I need to configure something like a trunk or a tunnel between Essex-1 & Essex-2 ?

I miss something in my configuration, if you have any idea...


Regards


Emilien


Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit :
It may help if you can share the log of your launched instance as well. There is a possibility that we both are having the same issue.
Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance.

Salman


________________________________

Subject: RE: [Openstack] Instance IP assignment problem
From: emilien.openstack at gmail.com<mailto:emilien.openstack at gmail.com>
To: salmanmk at live.com<mailto:salmanmk at live.com>
CC: jorge.delacruz at stackops.com<mailto:jorge.delacruz at stackops.com>; openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Date: Tue, 1 May 2012 21:26:26 +0200

Le mardi 01 mai 2012 à 14:22 -0500, Salman Malik a écrit :
Regarding L3 gateway, I believe its not necessary to have one (as the VM hasn't obtained an IP right now, so it can't talk to anything outside its net), but I am not sure.
Regarding your problem, do you see any DHCP responses from the DHCP server ? I am asking this because I was having a similar problem earlier where I was getting assigned an IP address no in my desired fixed_network and I believe that was cause by another interfering DHCP server that was replying to discover messages before the nova-network could.
Here my nova.conf and I don't have any interfering DHCP server :

https://github.com/EmilienM/doc-openstack/blob/master/Configuration%20Files/Essex-1/nova.conf


Thanks
Salman


________________________________


Subject: RE: [Openstack] Instance IP assignment problem
From: emilien.openstack at gmail.com<mailto:emilien.openstack at gmail.com>
To: salmanmk at live.com<mailto:salmanmk at live.com>
CC: jorge.delacruz at stackops.com<mailto:jorge.delacruz at stackops.com>; openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Date: Tue, 1 May 2012 21:06:01 +0200

Hi Salman,


I'm thinking about a networking issue. Where is your L3 gateway in this architecture ? Maybe do you need an ip helper tool to redirect DHCP broadcast ?


What do you think about my problem (follow up to my last e-mail) ?


Thanks


Emilien

Le mardi 01 mai 2012 à 14:00 -0500, Salman Malik a écrit :
Hi,

Here is the error log: http://pastebin.com/KrNZDrvD
and nova.conf: http://pastebin.com/Fvd6dSZs

Emilien, I am trying to get an understanding of how different Quantum plugins work with OpenStack. Ryu plugin is particularly interesting as it uses an OpenFlow controller to configure Vswitches.

The problem I am faced with is  (I think ) that I already have a private network and Quantum should assign IP addresses to instances using DHCP. But instances send out discover message on laucnh but never find a DHCP server (although there are 2 dnsmasqs running).

Any ideas?

Thanks,
Salman


________________________________



Date: Tue, 1 May 2012 20:43:44 +0200
Subject: Re: [Openstack] Instance IP assignment problem
From: jorge.delacruz at stackops.com<mailto:jorge.delacruz at stackops.com>
To: emilien.openstack at gmail.com<mailto:emilien.openstack at gmail.com>
CC: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>; salmanmk at live.com<mailto:salmanmk at live.com>

Hi Emilien and Salman,
Please, could you upload all the files, errors and conf in pastebin or something like that?
I have troubles to open in phone :)
Thank you
El 01/05/2012 20:39, "Emilien Macchi" <emilien.openstack at gmail.com<mailto:emilien.openstack at gmail.com>> escribió:
Hi,


I have a similar problem when I create a network per project_id with Quantum.


My VMs don't get IP and I can't understand why today.

But when I create a private network for all projects, VMs get an IP and all is working well.
Do you have the same problem ?


Salman, I'm interesting about your nova.conf. I can see you are using Ryu ?
Can you tell me more about your "use case" or architecture ?


Thanks


Le mardi 01 mai 2012 à 12:28 -0500, Salman Malik a écrit :
Hi Jorge,

Thanks for looking into the post.
I have made changes to the nova.conf file so that I only use 10.0.0.x network (but the problem is still the same). For this configuration, I assume that it will give out IPs to instances starting from 10.0.0.11. And just to inform you, my eth1 is configured to be 10.0.0.10 (which is a VM itself, and eth1 is configured as a host-only network with no DHCP) and this interface is plugged in the integration bridge used by quantum plugins.

Thanks,
Salman

PS: Error log of a launched instance is also attached.


________________________________




Date: Tue, 1 May 2012 19:03:49 +0200
Subject: Re: [Openstack] Instance IP assignment problem
From: jorge.delacruz at stackops.com<mailto:jorge.delacruz at stackops.com>
To: salmanmk at live.com<mailto:salmanmk at live.com>
CC: openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>

Im not really sure but you are using range for your environment 10.0.3.x and 10.0.0.x for fixed.
Can you attach a nova network conf?
Regards
El 01/05/2012 18:56, "Salman Malik" <salmanmk at live.com<mailto:salmanmk at live.com>> escribió:
Hi Guys,

Can anyone provide any insight to the following question:
https://answers.launchpad.net/nova/+question/195439

Thanks,
Salman


_______________________________________________
Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
Post to     : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>
Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>
More help   : https://help.launchpad.net/ListHelp



_______________________________________________

Mailing list: https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>

Post to     : openstack at lists.launchpad.net<mailto:openstack at lists.launchpad.net>

Unsubscribe : https://launchpad.net/~openstack<https://launchpad.net/%7Eopenstack>

More help   : https://help.launchpad.net/ListHelp





______________________________________________________________________
Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data.  If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120504/c494a8a5/attachment.html>


More information about the Openstack mailing list