<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.2.2">
</HEAD>
<BODY>
Hi Salman,<BR>
<BR>
Le jeudi 03 mai 2012 à 09:47 -0500, Salman Malik a écrit :
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#366092">Hi Emilien,</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#366092">In your configuration you have the following flags:</FONT></FONT>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
--flat_network_bridge=br100<BR>
</BLOCKQUOTE>
I'm going to try to change it in both servers.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
--floating_range=10.68.5.0/24<BR>
</BLOCKQUOTE>
That's actually my "public" pool, sot it's not my fixed pool (privates IPs).<BR>
<BR>
After my tests, I will let you know of course.<BR>
<BR>
<BR>
Thanks,<BR>
<BR>
<BR>
<BR>
Regards<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT SIZE="2"><FONT COLOR="#366092">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. </FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#366092">Let us know.</FONT></FONT><BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#366092">Thanks,</FONT></FONT><BR>
<FONT SIZE="2"><FONT COLOR="#366092">Salman</FONT></FONT><BR>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<HR ALIGN="center">
<BR>
Date: Thu, 3 May 2012 08:29:42 -0400<BR>
Subject: Re: [Openstack] Instance IP assignment problem<BR>
From: soheil@cs.toronto.edu<BR>
To: emilien.openstack@gmail.com<BR>
CC: ahaldin@griddynamics.com; openstack@lists.launchpad.net; salmanmk@live.com<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Oops accidently hit send on my phone.<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
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.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
BTW, if you are using virtualbox to run openstack, make sure you are not using vbox intel drivers. Use pcnet fast instead.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
OVS splinter may also be useful.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Hope that helps.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Cheers
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Soheil
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
On Thursday, May 3, 2012, Soheil Hassas Yeganeh wrote:<BR>
<BLOCKQUOTE>
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<BR>
<BLOCKQUOTE>
can you find dhcp requests by using tcpdump for example ?
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
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.
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
On Thu, May 3, 2012 at 12:48 PM, Emilien Macchi <emilien.openstack@gmail.com> wrote:
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BLOCKQUOTE>
All seems alright but not working yet.<BR>
<BR>
<BR>
<A HREF="http://paste.openstack.org/show/14791/">http://paste.openstack.org/show/14791/</A><BR>
<BR>
<BR>
<BR>
I have executed on both servers :<BR>
<BR>
ovs-vsctl add-port br-int eth1<BR>
<BR>
<BR>
Need I do something else ?<BR>
<BR>
How the DHCP is working in this case ?<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
Le jeudi 03 mai 2012 à 09:29 +0100, Bilel Msekni a écrit :
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BLOCKQUOTE>
Then the problem isn't in the instance but in the nova-network service , please check if it is working well <BR>
as well as give us the output log when you attempt to create a new instance.<BR>
<BR>
<BR>
<HR ALIGN="center">
<BR>
<BR>
Subject: RE: [Openstack] Instance IP assignment problem<BR>
From: emilien.openstack@gmail.com<BR>
To: skible@hotmail.fr<BR>
CC: salmanmk@live.com; openstack@lists.launchpad.net<BR>
Date: Thu, 3 May 2012 10:21:37 +0200<BR>
<BR>
Fixed IP<BR>
<BR>
<BR>
<BR>
Le jeudi 03 mai 2012 à 09:15 +0100, Bilel Msekni a écrit : <BR>
<BLOCKQUOTE>
Fixed IP or Floating IP ?<BR>
<BR>
<BR>
<HR ALIGN="center">
<BR>
<BR>
<BR>
From: emilien.openstack@gmail.com<BR>
To: salmanmk@live.com<BR>
Date: Thu, 3 May 2012 09:55:31 +0200<BR>
CC: openstack@lists.launchpad.net<BR>
Subject: Re: [Openstack] Instance IP assignment problem<BR>
<BR>
Hi,<BR>
<BR>
<BR>
As I told you, I have also a problem for instance IP assignement.<BR>
<BR>
<BR>
<U>My architecture :</U><BR>
<BR>
I use <B>Quantum</B> with <B>OVS plugin</B> on 2 servers Essex-1 & Essex-2. Essex-1 runs all services and Essex-2 runs OVS, Quantum-agent & nova-compute only.<BR>
<BR>
You can see more details <A HREF="https://github.com/EmilienM/doc-openstack/blob/master/Documentation/How%20to%20setup%20OpenStack%20Essex.pdf">here</A>.<BR>
<BR>
My configurations files are <A HREF="https://github.com/EmilienM/doc-openstack/tree/master/Configuration%20Files">here</A> and in my documentation.<BR>
<BR>
<BR>
<BR>
<U>Problem Description :</U><BR>
<BR>
When an instance is created in ESSEX-1, all is working (network).<BR>
<BR>
But when the VM is started on ESSEX-2, it does not get an IP address. (<A HREF="http://paste.openstack.org/show/14775/">log file</A>)<BR>
<BR>
I'm sure the problem comes from OVS connection with ESSEX-1.<BR>
<BR>
<BR>
Do I need to configure something like a trunk or a tunnel between Essex-1 & Essex-2 ?<BR>
<BR>
I miss something in my configuration, if you have any idea...<BR>
<BR>
<BR>
Regards<BR>
<BR>
<BR>
Emilien<BR>
<BR>
<BR>
Le mardi 01 mai 2012 à 14:35 -0500, Salman Malik a écrit : <BR>
<BLOCKQUOTE>
<FONT COLOR="#366092">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. </FONT><BR>
<FONT COLOR="#366092">Netstack developers can give a definitive answer to this, but it would be interesting to learn what goes wrong with a launched instance.</FONT><BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>