openstack team mailing list archive

[Thierry Carrez <thierry@xxxxxxxxxxxxx>]

Dan Wendlandt wrote:
> On 24/07/12 18:33 -0700, Eugene Kirpichov wrote:
>>         We at Mirantis have had a number of clients request functionality to
>>         control various load balancer devices (software and hardware) via an
>>         OpenStack API and horizon. So, in collaboration with Cisco OpenStack
>>         team and a number of other community members, we’ve started
>>         socializing the blueprints for an elastic load balancer API service.
>>         At this point we’d like to share where we are and would very much
>>         appreciate anyone participate and provide input.
> 
> Yes, I definitely think LB is one of the key items that we'll want to tackle during Grizzly in terms of L4-L7 services.  

Yes, LB sounds like the first service to implement in the "utility
network services" direction.

>>         Another question we have is if this should be a standalone
>>         module or a
>>         Quantum plugin… 
> 
> Based on discussions during the PPB meeting about quantum becoming core,
> there was a push for having a single network service and API, which
> would tend to suggest it being a sub-component of Quantum that is
> independently loadable.  I also tend to think that its likely to be a
> common set of developers working across all such networking
> functionality, so it wouldn't seem like keeping different core-dev
> teams, repos, tarballs, docs, etc. probably doesn't make sense.  I think
> this is generally inline with the plan of allowing Quantum to load
> additional portions of the API as needed for additional services like
> LB, WAN-bridging, but this is probably a call for the PPB in general.  

The sub-component approach would have my preference. It sounds like a
natural advanced network service to provide within Quantum.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack