Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Dev

Instance IP assignment problem

 

 

First page Previous page 1 2 Next page Last page  View All OpenStack dev RSS feed   Index | Next | Previous | View Threaded


emilien.openstack at gmail

May 3, 2012, 3:09 AM

Post #26 of 39 (236 views)
Permalink
Re: Instance IP assignment problem [In reply to]

I share my OVS configuration with you :


root [at] essex-:~# ovs-vsctl show
03583d51-03b8-4061-a147-1d892447bee2
Bridge br-int
Port "tap21d51768-3c"
tag: 12
Interface "tap21d51768-3c"
Port br-int
Interface br-int
type: internal
Port "gw-2850687f-68"
tag: 12
Interface "gw-2850687f-68"
type: internal
Port "eth1"
Interface "eth1"
ovs_version: "1.4.0+build0"


root [at] essex-:~# ovs-vsctl show
3defede8-df1c-4a99-9928-850d9f665194
Bridge br-int
Port br-int
Interface br-int
type: internal
Port "tapa8899517-37"
tag: 12
Interface "tapa8899517-37"
Port "eth1"
Interface "eth1"
ovs_version: "1.4.0+build0"





Le jeudi 03 mai 2012 à 13:31 +0400, Anton Haldin a écrit :

> 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> 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
> > To: skible [at] hotmail
> > CC: salmanmk [at] live; openstack [at] lists
> > 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
> > To: salmanmk [at] live
> > Date: Thu, 3 May 2012 09:55:31 +0200
> > CC: openstack [at] lists
> > 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.
> >
> > Salman
> >
> >
> >
> >
> > ____________________________________________
> >
> >
> >
> > Subject: RE: [Openstack] Instance IP
> > assignment problem
> > From: emilien.openstack [at] gmail
> > To: salmanmk [at] live
> > CC: jorge.delacruz [at] stackops;
> > openstack [at] lists
> > 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
> > To: salmanmk [at] live
> > CC: jorge.delacruz [at] stackops;
> > openstack [at] lists
> > 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
> > To:
> > emilien.openstack [at] gmail
> > CC:
> > openstack [at] lists; salmanmk [at] live
> >
> > 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> 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
> > To:
> > salmanmk [at] live
> > CC:
> > openstack [at] lists
> >
> > 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> 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
> > Post
> > to
> >
> > :
> > openstack [at] lists
> > Unsubscribe : https://launchpad.net/~openstack
> > More
> > help : https://help.launchpad.net/ListHelp
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to : openstack [at] lists
> > Unsubscribe : https://launchpad.net/~openstack
> > More help : https://help.launchpad.net/ListHelp
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack Post
> > to : openstack [at] lists Unsubscribe :
> > https://launchpad.net/~openstack More help :
> > https://help.launchpad.net/ListHelp
> >
> >
> >
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
>


emilien.openstack at gmail

May 3, 2012, 4:01 AM

Post #27 of 39 (244 views)
Permalink
Re: Instance IP assignment problem [In reply to]

Can you send my your nova.conf of nova-compute servers ?



I'm thinking about flat interface...




Le jeudi 03 mai 2012 à 10:26 +0100, Bilel Msekni a écrit :
> Basing on your architecture picture , I think you mean ping VM that
> resides on Essex 2 from server containing Essex 1
>
> I had a similar networking problem and i honestly don't know i fixed
> it ( didn't enable tunneling) , this is what i did
> 1- ifconfig eth0 0.0.0.0
> 2- dhclient br-int ( normally the bridge will take the address of
> eth0)
>
>
> and pinging went back to working fine but i am still testing if there
> are any side effects
> Try it out and txt me !
>
>
> btw , i used your ubuntu 12.04 LTS cloud img and i can't seem to ping
> it but when i choose another image ( the default tty for example) it
> ping as a charm , probably you should pick another image !
>
>
>
>
>
>
> ______________________________________________________________________
> Subject: RE: [Openstack] Instance IP assignment problem
> From: emilien.openstack [at] gmail
> To: skible [at] hotmail
> CC: openstack [at] lists
> Date: Thu, 3 May 2012 11:11:04 +0200
>
> Ok :
>
> http://paste.openstack.org/show/14797/
>
>
> I know where is the problem but I dont know yet how to fix it :
>
>
> - Quantum creates TAP interface on ESSEX-2
>
> - From ESSEX-2, I can't ping VMs on ESSEX-1
>
>
> Here my ovs_quantum_plugin.ini :
>
> [DATABASE]
> sql_connection =
> mysql://ovs_quantum:password [at] 10:3306/ovs_quantum
>
>
> [OVS]
> integration-bridge = br-int
>
>
> [AGENT]
> root_helper = sudo
>
>
>
> Do we need enable bridge ?
>
>
>
>
> Le jeudi 03 mai 2012 à 10:00 +0100, Bilel Msekni a écrit :
>
> èmm , can you do this on your instance : nova show %
> instance_Id so that i may see the problem in the resume of
> spawning ?
> and are you sure you have enough fixed ip addresses left for
> use ?
>
> The configuration of nova and quantum is almost the same as me
> and the instances are getting Fixed Ips without any problem !
>
>
> ______________________________________________________________
>
> Subject: RE: [Openstack] Instance IP assignment problem
> From: emilien.openstack [at] gmail
> To: skible [at] hotmail
> CC: salmanmk [at] live; openstack [at] lists
> Date: Thu, 3 May 2012 10:48:43 +0200
>
> 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
> To: skible [at] hotmail
> CC: salmanmk [at] live; openstack [at] lists
> 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
> To: salmanmk [at] live
> Date: Thu, 3 May 2012 09:55:31 +0200
> CC: openstack [at] lists
> 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.
>
> Salman
>
>
>
>
> ______________________________________
>
>
>
>
> Subject: RE: [Openstack] Instance IP
> assignment problem
> From: emilien.openstack [at] gmail
> To: salmanmk [at] live
> CC: jorge.delacruz [at] stackops;
> openstack [at] lists
> 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
> To: salmanmk [at] live
> CC:
> jorge.delacruz [at] stackops;
> openstack [at] lists
> 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
> To:
> emilien.openstack [at] gmail
> CC:
> openstack [at] lists; salmanmk [at] live
>
> 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> 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
> To:
> salmanmk [at] live
> CC:
> openstack [at] lists
>
> 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> 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
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack [at] lists Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
>
>
>
>
>
>
>
>
>


soheil at cs

May 3, 2012, 5:18 AM

Post #28 of 39 (243 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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> 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
>> To: skible [at] hotmail
>> CC: salmanmk [at] live; openstack [at] lists
>> 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
>> To: salmanmk [at] live
>> Date: Thu, 3 May 2012 09:55:31 +0200
>> CC: openstack [at] lists
>> 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
>> To: salmanmk [at] live
>> CC: jorge.delacruz [at] stackops; openstack [at] lists
>> 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
>> To: salmanmk [at] live
>> CC: jorge.delacruz [at] stackops; openstack [at] lists
>> 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
>> To: emilien.openstack [at] gmail
>> CC: openstack [at] lists; salmanmk [at] live
>>
>> 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>
>> 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
>> To: salmanmk [at] live
>> CC: openstack [at] lists
>>
>> 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> 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
>> Post to : openstack [at] lists
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack [at] lists
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________ Mailing list:
>> https://launchpad.net/~openstack Post to : openstack [at] lists :
>> https://launchpad.net/~openstack More help :
>> https://help.launchpad.net/ListHelp
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack [at] lists
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>


soheil at cs

May 3, 2012, 5:29 AM

Post #29 of 39 (240 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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> 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
> To: skible [at] hotmail
> CC: salmanmk [at] live; openstack [at] lists
> 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
> To: salmanmk [at] live
> Date: Thu, 3 May 2012 09:55:31 +0200
> CC: openstack [at] lists
> 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.
>
>


salmanmk at live

May 3, 2012, 7:47 AM

Post #30 of 39 (232 views)
Permalink
Re: Instance IP assignment problem [In reply to]

Hi Emilien,

In your configuration you have the following flags:
--flat_network_bridge=br100--floating_range=10.68.5.0/24Can 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
To: emilien.openstack [at] gmail
CC: ahaldin [at] griddynamics; openstack [at] lists; salmanmk [at] live

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.

CheersSoheil
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> 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

To: skible [at] hotmail

CC: salmanmk [at] live; openstack [at] lists

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

To: salmanmk [at] live

Date: Thu, 3 May 2012 09:55:31 +0200

CC: openstack [at] lists

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.


emilien.openstack at gmail

May 3, 2012, 8:02 AM

Post #31 of 39 (234 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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
> To: emilien.openstack [at] gmail
> CC: ahaldin [at] griddynamics; openstack [at] lists;
> salmanmk [at] live
>
>
> 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> 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
> To: skible [at] hotmail
> CC: salmanmk [at] live;
> openstack [at] lists
> 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
> To: salmanmk [at] live
> Date: Thu, 3 May 2012 09:55:31
> +0200
> CC:
> openstack [at] lists
> 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.
>
>
>


salmanmk at live

May 3, 2012, 12:53 PM

Post #32 of 39 (230 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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
To: salmanmk [at] live
CC: soheil [at] cs; ahaldin [at] griddynamics; openstack [at] lists
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

To: emilien.openstack [at] gmail

CC: ahaldin [at] griddynamics; openstack [at] lists; salmanmk [at] live





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> 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

To: skible [at] hotmail

CC: salmanmk [at] live; openstack [at] lists

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

To: salmanmk [at] live

Date: Thu, 3 May 2012 09:55:31 +0200

CC: openstack [at] lists

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.


emilien.openstack at gmail

May 3, 2012, 2:36 PM

Post #33 of 39 (230 views)
Permalink
Re: Instance IP assignment problem [In reply to]

With Quantum !


Le jeudi 3 mai 2012, Salman Malik <salmanmk [at] live> 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
> To: salmanmk [at] live
> CC: soheil [at] cs; ahaldin [at] griddynamics;
openstack [at] lists
> 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
> To: emilien.openstack [at] gmail
> CC: ahaldin [at] griddynamics; openstack [at] lists;
salmanmk [at] live
>
> 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> 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


salmanmk at live

May 3, 2012, 3:06 PM

Post #34 of 39 (233 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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
To: salmanmk [at] live
CC: soheil [at] cs; ahaldin [at] griddynamics; openstack [at] lists

With Quantum !


Le jeudi 3 mai 2012, Salman Malik <salmanmk [at] live> 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

> To: salmanmk [at] live
> CC: soheil [at] cs; ahaldin [at] griddynamics; openstack [at] lists

> 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
> To: emilien.openstack [at] gmail
> CC: ahaldin [at] griddynamics; openstack [at] lists; salmanmk [at] live

>
> 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> 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


emilien.openstack at gmail

May 4, 2012, 12:39 AM

Post #35 of 39 (232 views)
Permalink
Re: Instance IP assignment problem [In reply to]

I think this documentation explains better like me :


http://docs.openstack.org/trunk/openstack-network/admin/content/Using-dle455.html

Quantum is in incubation with Essex, so it's use Nova as a client of
Quantum. In the future, Quantum could be able to manage floating / fixed
ips by itself.



Regards



Le jeudi 03 mai 2012 à 17:06 -0500, Salman Malik a écrit :

> 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
> To: salmanmk [at] live
> CC: soheil [at] cs; ahaldin [at] griddynamics;
> openstack [at] lists
>
> With Quantum !
>
>
> Le jeudi 3 mai 2012, Salman Malik <salmanmk [at] live> 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
> > To: salmanmk [at] live
> > CC: soheil [at] cs; ahaldin [at] griddynamics;
> openstack [at] lists
> > 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
> > To: emilien.openstack [at] gmail
> > CC: ahaldin [at] griddynamics; openstack [at] lists;
> salmanmk [at] live
> >
> > 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> 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


Mandar.Vaze at nttdata

May 4, 2012, 6:10 AM

Post #36 of 39 (233 views)
Permalink
Re: Instance IP assignment problem [In reply to]

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 [mailto:openstack-bounces+mandar.vaze=nttdata.com [at] lists] On Behalf Of Emilien Macchi
Sent: Thursday, May 03, 2012 1:26 PM
To: Salman Malik
Cc: openstack [at] lists
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<mailto:emilien.openstack [at] gmail>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: jorge.delacruz [at] stackops<mailto:jorge.delacruz [at] stackops>; openstack [at] lists<mailto:openstack [at] lists>
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<mailto:emilien.openstack [at] gmail>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: jorge.delacruz [at] stackops<mailto:jorge.delacruz [at] stackops>; openstack [at] lists<mailto:openstack [at] lists>
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<mailto:jorge.delacruz [at] stackops>
To: emilien.openstack [at] gmail<mailto:emilien.openstack [at] gmail>
CC: openstack [at] lists<mailto:openstack [at] lists>; salmanmk [at] live<mailto:salmanmk [at] live>

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<mailto:emilien.openstack [at] gmail>> 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<mailto:jorge.delacruz [at] stackops>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: openstack [at] lists<mailto:openstack [at] lists>

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<mailto:salmanmk [at] live>> 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<mailto:openstack [at] lists>
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<mailto:openstack [at] lists>

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


Mandar.Vaze at nttdata

May 4, 2012, 6:14 AM

Post #37 of 39 (226 views)
Permalink
Re: Instance IP assignment problem [In reply to]

Please also see this : https://review.openstack.org/#/c/6829/

When nova-network is on remote host, dhcp requests need to go to remote server. I’ve proposed a fix above.

-Mandar

From: openstack-bounces+mandar.vaze=nttdata.com [at] lists [mailto:openstack-bounces+mandar.vaze=nttdata.com [at] lists] On Behalf Of Emilien Macchi
Sent: Thursday, May 03, 2012 2:19 PM
To: Bilel Msekni
Cc: salmanmk [at] live; openstack [at] lists
Subject: Re: [Openstack] Instance IP assignment problem

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<mailto:emilien.openstack [at] gmail>
To: skible [at] hotmail<mailto:skible [at] hotmail>
CC: salmanmk [at] live<mailto:salmanmk [at] live>; openstack [at] lists<mailto:openstack [at] lists>
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<mailto:emilien.openstack [at] gmail>
To: salmanmk [at] live<mailto:salmanmk [at] live>
Date: Thu, 3 May 2012 09:55:31 +0200
CC: openstack [at] lists<mailto:openstack [at] lists>
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<mailto:emilien.openstack [at] gmail>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: jorge.delacruz [at] stackops<mailto:jorge.delacruz [at] stackops>; openstack [at] lists<mailto:openstack [at] lists>
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<mailto:emilien.openstack [at] gmail>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: jorge.delacruz [at] stackops<mailto:jorge.delacruz [at] stackops>; openstack [at] lists<mailto:openstack [at] lists>
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<mailto:jorge.delacruz [at] stackops>
To: emilien.openstack [at] gmail<mailto:emilien.openstack [at] gmail>
CC: openstack [at] lists<mailto:openstack [at] lists>; salmanmk [at] live<mailto:salmanmk [at] live>

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<mailto:emilien.openstack [at] gmail>> 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<mailto:jorge.delacruz [at] stackops>
To: salmanmk [at] live<mailto:salmanmk [at] live>
CC: openstack [at] lists<mailto:openstack [at] lists>

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<mailto:salmanmk [at] live>> 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
Post to : openstack [at] lists<mailto:openstack [at] lists>
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp



_______________________________________________

Mailing list: https://launchpad.net/~openstack

Post to : openstack [at] lists<mailto:openstack [at] lists>

Unsubscribe : https://launchpad.net/~openstack

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





_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack [at] lists<mailto:openstack [at] lists> Unsubscribe : https://launchpad.net/~openstack 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


emilien.openstack at gmail

May 4, 2012, 6:29 AM

Post #38 of 39 (226 views)
Permalink
Re: Instance IP assignment problem [In reply to]

Thank's for your link, but I'm not sure to have to use it now.


I have one server with all nova services and another with nova-compute
only.


Anyway, I'm going to post a new e-mail about my problem.


Regards


Le vendredi 04 mai 2012 à 13:14 +0000, Vaze, Mandar a écrit :
> Please also see this : https://review.openstack.org/#/c/6829/
>
>
>
> When nova-network is on remote host, dhcp requests need to go to
> remote server. I’ve proposed a fix above.
>
>
>
> -Mandar
>
>
>
>
> From: openstack-bounces+mandar.vaze=nttdata.com [at] lists
> [mailto:openstack-bounces+mandar.vaze=nttdata.com [at] lists]
> On Behalf Of Emilien Macchi
> Sent: Thursday, May 03, 2012 2:19 PM
> To: Bilel Msekni
> Cc: salmanmk [at] live; openstack [at] lists
> Subject: Re: [Openstack] Instance IP assignment problem
>
>
>
>
>
> 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
> To: skible [at] hotmail
> CC: salmanmk [at] live; openstack [at] lists
> 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
> To: salmanmk [at] live
> Date: Thu, 3 May 2012 09:55:31 +0200
> CC: openstack [at] lists
> 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.
>
> Salman
>
>
>
>
>
>
> ______________________________________________________________
>
>
>
>
> Subject: RE: [Openstack] Instance IP assignment problem
> From: emilien.openstack [at] gmail
> To: salmanmk [at] live
> CC: jorge.delacruz [at] stackops; openstack [at] lists
> 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
> To: salmanmk [at] live
> CC: jorge.delacruz [at] stackops; openstack [at] lists
> 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
> To: emilien.openstack [at] gmail
> CC: openstack [at] lists; salmanmk [at] live
>
> 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> 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
> To: salmanmk [at] live
> CC: openstack [at] lists
>
> 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>
> 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
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
>
>
>
>
>
>
>
> _______________________________________________ Mailing list:
> https://launchpad.net/~openstack Post to :
> openstack [at] lists Unsubscribe :
> https://launchpad.net/~openstack 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


emilien.openstack at gmail

May 4, 2012, 6:32 AM

Post #39 of 39 (228 views)
Permalink
Re: Instance IP assignment problem [In reply to]

With this article, I understand I'm not alone to have this problem.


I'm going to try the solution, and If it's working, I will update my
documentation on Essex.



Regards



Le vendredi 04 mai 2012 à 13:10 +0000, Vaze, Mandar a écrit :
> 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
> [mailto:openstack-bounces+mandar.vaze=nttdata.com [at] lists]
> On Behalf Of Emilien Macchi
> Sent: Thursday, May 03, 2012 1:26 PM
> To: Salman Malik
> Cc: openstack [at] lists
> 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.
>
> Salman
>
>
>
>
>
>
>
>
> ______________________________________________________________
>
>
> Subject: RE: [Openstack] Instance IP assignment problem
> From: emilien.openstack [at] gmail
> To: salmanmk [at] live
> CC: jorge.delacruz [at] stackops; openstack [at] lists
> 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
> To: salmanmk [at] live
> CC: jorge.delacruz [at] stackops; openstack [at] lists
> 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
> To: emilien.openstack [at] gmail
> CC: openstack [at] lists; salmanmk [at] live
>
> 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> 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
> To: salmanmk [at] live
> CC: openstack [at] lists
>
> 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>
> 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
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> 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

First page Previous page 1 2 Next page Last page  View All OpenStack dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.