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

Mailing List Archive: OpenStack: Netstack

Re: [Openstack] [Nova] Networking changes and quantum

 

 

OpenStack netstack RSS feed   Index | Next | Previous | View Threaded


dan at nicira

Jul 6, 2012, 5:57 PM

Post #1 of 4 (203 views)
Permalink
Re: [Openstack] [Nova] Networking changes and quantum

Hi Ryan,

L3 + Floating IPs are being added to Quantum in F-3 (got bumped from F-2).


I haven't looked at your patch in detail, but it seems like you're looking
to notice when a floating-ip is allocated or deallocated, and use that to
trigger a change to the configuration of an external BGP daemon.

Assuming that's the case, I'd much rather we take the approach of creating
a notification API that would let you build this functionality as an
external component process that feeds off of notifications about floating
IPs being allocated and deallocated. We're looking at something similar
for DHCP as well. This let's people implement custom functionality without
having to modify the core code and config files. We have a blueprint to
add such a notification framework to Quantum (likely based on work in
Nova), but at this point, but its not clear when this will land (likely
depends on whether it is used for DHCP improvements in F-3 or not). If
you're interested in helping out with it, let me know.

Dan


On Fri, Jul 6, 2012 at 5:09 PM, Ryan Lane <rlane [at] wikimedia> wrote:

> I'm trying to add support to nova for BGP announcements for floating
> IP addresses (as an alternative to subnetting and ARP). The change
> currently has a -1, since networking code is moving to quantum. It
> seems that quantum doesn't have floating IP support, though. Where
> should I be adding this code?
>
> https://review.openstack.org/#/c/9255/
>
> - Ryan
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~


rlane at wikimedia

Jul 7, 2012, 5:33 PM

Post #2 of 4 (188 views)
Permalink
Re: [Openstack] [Nova] Networking changes and quantum [In reply to]

> L3 + Floating IPs are being added to Quantum in F-3 (got bumped from F-2).
>

So, I should wait until L3 and try again, but in quantum?

> I haven't looked at your patch in detail, but it seems like you're looking
> to notice when a floating-ip is allocated or deallocated, and use that to
> trigger a change to the configuration of an external BGP daemon.
>

Yes, on a per network-node basis. Also, rather than binding the IP to
the public network device, it should bind the IP to lo (to avoid arp
issues). Binding the IPs to lo is likely doable without any changes,
though.

> Assuming that's the case, I'd much rather we take the approach of creating a
> notification API that would let you build this functionality as an external
> component process that feeds off of notifications about floating IPs being
> allocated and deallocated. We're looking at something similar for DHCP as
> well. This let's people implement custom functionality without having to
> modify the core code and config files. We have a blueprint to add such a
> notification framework to Quantum (likely based on work in Nova), but at
> this point, but its not clear when this will land (likely depends on whether
> it is used for DHCP improvements in F-3 or not). If you're interested in
> helping out with it, let me know.
>

Well, I can write this as a plugin, based on the plugin code in
openstack-common. I thought this was a useful enough change to go in
core, though. If everything in quantum is going to be a plugin, I'm
more than happy to have this as a plugin.

When do you expect this API to be available? I plan on backporting my
work to nova for diablo and essex, but I'd like to make sure I have
this upstream in the right place, and in the preferred way.

- Ryan

--
Mailing list: https://launchpad.net/~netstack
Post to : netstack [at] lists
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp


dan at nicira

Jul 10, 2012, 8:50 AM

Post #3 of 4 (177 views)
Permalink
Re: [Openstack] [Nova] Networking changes and quantum [In reply to]

On Sat, Jul 7, 2012 at 5:33 PM, Ryan Lane <rlane [at] wikimedia> wrote:

> > L3 + Floating IPs are being added to Quantum in F-3 (got bumped from
> F-2).
> >
>
> So, I should wait until L3 and try again, but in quantum?
>

Yes, from talking to Vish a while back, the plan is that nova-network will
be more less "feature frozen", with new features targeting Quantum. We're
at a bit of an awkward transition point right now, so probably best to
continue to use your nova-network implementation off an internal branch for
now, and then integrate with Quantum once the base L3 stuff is in.


> When do you expect this API to be available? I plan on backporting my
> work to nova for diablo and essex, but I'd like to make sure I have
> this upstream in the right place, and in the preferred way.
>

The basic L3 and notification changes should be in during Folsom-3.

Dan



>
> - Ryan
>



--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~


rlane at wikimedia

Jul 10, 2012, 10:24 AM

Post #4 of 4 (177 views)
Permalink
Re: [Openstack] [Nova] Networking changes and quantum [In reply to]

>> So, I should wait until L3 and try again, but in quantum?
>
>
> Yes, from talking to Vish a while back, the plan is that nova-network will
> be more less "feature frozen", with new features targeting Quantum. We're
> at a bit of an awkward transition point right now, so probably best to
> continue to use your nova-network implementation off an internal branch for
> now, and then integrate with Quantum once the base L3 stuff is in.
>
>>
>> When do you expect this API to be available? I plan on backporting my
>> work to nova for diablo and essex, but I'd like to make sure I have
>> this upstream in the right place, and in the preferred way.
>
>
> The basic L3 and notification changes should be in during Folsom-3.
>

Great, thanks for the info, I'll add this into quantum in L3.

- Ryan

--
Mailing list: https://launchpad.net/~netstack
Post to : netstack [at] lists
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp

OpenStack netstack 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.