Open Stack

Hmm... I didn't know the difference. 
So does it works like this: one can use the floating_range flag/fixed_range in nova. conf for putting instances in this global network by default ? and then one could create quantum network for each project and may use fixed/floating flags with this network to define private and public networks ?

Date: Thu, 3 May 2012 23:36:36 +0200
Subject: Re: [Openstack] Instance IP assignment problem
From: emilien.openstack at gmail.com
To: salmanmk at live.com
CC: soheil at cs.toronto.edu; ahaldin at griddynamics.com; openstack at lists.launchpad.net

With Quantum !


Le jeudi 3 mai 2012, Salman Malik <salmanmk at live.com> a écrit :
> I see. So where do you use private IP's in your setup ?
>
> Thanks,

> Salman
>
>
> ________________________________
> Subject: RE: [Openstack] Instance IP assignment problem
> From: emilien.openstack at gmail.com

> To: salmanmk at live.com
> CC: soheil at cs.toronto.edu; ahaldin at griddynamics.com; openstack at lists.launchpad.net

> Date: Thu, 3 May 2012 17:02:23 +0200
>
> Hi Salman,
>
> Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit :
>
> Hi Emilien,
>
> In your configuration you have the following flags:

>
> --flat_network_bridge=br100
>
> I'm going to try to change it in both servers.
>
> --floating_range=10.68.5.0/24
>
> That's actually my "public" pool, sot it's not my fixed pool (privates IPs).

>
> After my tests, I will let you know of course.
>
>
> Thanks,
>
>
>
> Regards
>
>
> Can you please tell me why you need br100 when you are using br-int with OVS ? Secondly, you seem to use floating_range flag as the second flag. I assume that it is the pool of addresses that your instances will get IP from, right? It may be worthwhile to modify it to fixed_range because Bilal suggested here that this config worked for him.

>
> Let us know.
>
> Thanks,
> Salman
>
>
>
> ________________________________
> Date: Thu, 3 May 2012 08:29:42 -0400
> Subject: Re: [Openstack] Instance IP assignment problem

> From: soheil at cs.toronto.edu
> To: emilien.openstack at gmail.com
> CC: ahaldin at griddynamics.com; openstack at lists.launchpad.net; salmanmk at live.com

>
> Oops accidently hit send on my phone.
>
>
> I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn't delivering packets. You can check it using tcpdump -e -vvv.

>
> BTW, if you are using virtualbox to run openstack, make sure you are not using vbox intel drivers. Use pcnet fast instead.
>
> OVS splinter may also be useful.
>
> Hope that helps.

>
> Cheers
>
> Soheil
>
> On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote:
>
> I had a similar problem before. My problem was that the nic driver on the compute instance (your Essex 2) was dropping vlan tags, and then, openvswitch wasn

>
> can you find dhcp requests by using tcpdump for example ?
>
> sorry for "off-topic" but there may be many reasons of such issue with dhcp. last one for me was old dhcp client(Ubuntu) and udp checksum error. I have essex on centos and was trying ubuntu vm. 

>
> On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi <emilien.openstack at gmail.com> wrote:
>
> All seems alright but not working yet.
>
>

> http://paste.openstack.org/show/14791/
>
>
>
> I have executed on both servers :
>
> ovs-vsctl add-port br-int eth1
>

>
> Need I do something else ?
>
> How t 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120503/03afd64b/attachment.html>