[Openstack] Instance IP assignment problem
Emilien Macchi
emilien.openstack at gmail.com
Thu May 3 15:02:23 UTC 2012
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 the DHCP is working in this case ?
>
>
>
>
>
>
> Le jeudi 03 mai 2012 à 09:29 +0100, Bilel
> Msekni a écrit :
>
> Then the problem isn't in the instance
> but in the nova-network service ,
> please check if it is working well
> as well as give us the output log when
> you attempt to create a new instance.
>
>
>
> ______________________________________
>
> Subject: RE: [Openstack] Instance IP
> assignment problem
> From: emilien.openstack at gmail.com
> To: skible at hotmail.fr
> CC: salmanmk at live.com;
> openstack at lists.launchpad.net
> Date: Thu, 3 May 2012 10:21:37 +0200
>
> Fixed IP
>
>
>
> Le jeudi 03 mai 2012 à 09:15 +0100,
> Bilel Msekni a écrit :
>
> Fixed IP or Floating IP ?
>
>
>
> ______________________________
>
>
> From:
> emilien.openstack at gmail.com
> To: salmanmk at live.com
> Date: Thu, 3 May 2012 09:55:31
> +0200
> 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.
>
> My configurations files are
> here 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)
>
> 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.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120503/1a3fe220/attachment.html>
More information about the Openstack
mailing list