Hi, Salvatore, I guess 'router_service_type' extension is used together with 'router_service_insertion'.
The purpose of this blueprint is to allow multiple vendor's routing services coexist in a network. One router can be implemented by L3 agent, another one might be from vArmour, NVP or Cisco, for example. Thanks, Gary On Thu, Oct 24, 2013 at 4:13 PM, Salvatore Orlando <[email protected]>wrote: > Gary, > > In the context of the nvp plugin we use a mechanism for enabling > 'advanced' capabilities of a router leveraging a 'router_service_type' > extension. > this allow us to configure two types of routers, one which does just L3 > forwarding, NAT and a few other things, and another one which also has the > capability of hosting adv services such as firewall and load balancing. > > Is this similar to what you want to achieve with this blueprint? > > Regards, > Salvatore > > > On 25 October 2013 01:03, Gary Duan <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >>> >>> >>> _______________________________________________ >>> OpenStack-dev mailing list >>> [email protected] >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
