Open Stack

Let me try to clarify things a bit.

At Fri, 25 Oct 2013 08:44:05 +0900,
Itsuro ODA wrote:
> 
> Hi Gray,
> 
> Thanks for your response.
> 
> Our plan is as follows:
> * LVS driver is one of lbaas provider driver.
>   It communicates with l3_agent instead of lbaas_agent.

LVS agent part will reside in the L3 agent, just like FWaaS.
At this point, I plan to use the same LBaaS RPC topic, so the server
(Neutron) side of the LVS implementation isn't much different from
the current HAproxy one.

> * For l3_agent side, I think the implementation is same as
>   fwaas. L3NATAgent inherits like LVSL3AgentRpcCallback
>   class added which communicates with LVS provider driver.
>   So l3_agent functions already existed are not changed,
>   just added LB function.

L3NATAgent inherits FWaaSL3AgentRpcCallback.
My plan is to create LVSL3AgentRpcCallback and make L3NATAgent inherit
this. LVSL3AgentRpcCallback will make use of the L3 router ports for
LVS operations.

>   I think the implementation would change depending on
>   the service chaining discussion.

Exactly.
There is a private LVS LBaaS implementation.
I think the above plan is a good way to provide a working example
based on the code.
Implementations can change as the service chaining discussion
develops.


> Thanks,
> Itsuto Oda
> 
> # note that Toshihiro Iwamoto, a main developer of our BPs
> # may replay instead of me. He will attend the HK summit.
> 
> On Thu, 24 Oct 2013 16:03:25 -0700
> Gary Duan <gduan at varmour.com> wrote:
> 
> > Hi, Oda-san,
> > 
> > Thanks for your response.
> > 
> > L3 agent function should remain the same, as one driver implementation of
> > L3 router plugin.
> > 
> > My understanding is your lbaas driver can be running on top of L3 agent and
> > LVS' own routing services. Is my understanding correct?
> > 
> > Thanks,
> > Gary
> > 
> > 
> > On Thu, Oct 24, 2013 at 3:16 PM, Itsuro ODA <oda at valinux.co.jp> wrote:
> > 
> > > Hi,
> > >
> > > We are going to implement 2-arm type lbaas using LVS, and have submitted
> > > the following BPs.
> > >
> > >
> > > https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion
> > > https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver
> > > https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-extra-features
> > >
> > > Maybe the first one is same as yours.
> > > We are happy if we just concentrate making a provider driver.
> > >
> > > Thanks.
> > > Itsuro Oda
> > >
> > > On Thu, 24 Oct 2013 11:56:53 -0700
> > > Gary Duan <gduan at varmour.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > I've registered a BP for L3 router service integration with service
> > > > framework.
> > > >
> > > > https://blueprints.launchpad.net/neutron/+spec/l3-router-service-type
> > > >
> > > > In general, the implementation will align with how LBaaS is integrated
> > > with
> > > > the framework. One consideration we heard from several team members is to
> > > > be able to support vendor specific features and extensions in the service
> > > > plugin.
> > > >
> > > > Any comment is welcome.
> > > >
> > > > Thanks,
> > > > Gary
> > >
> > > --
> > > Itsuro ODA <oda at valinux.co.jp>
> > >
> > >
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> 
> -- 
> Itsuro ODA <oda at valinux.co.jp>
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev