Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
FYI, I pushed code review for the blueprint. The patch is missing unitest and tempest. It's only submitted for discussion. The patch implements two-step commit process similar to ML2, but it's not intended to solve all race conditions. Another thing I think worth discussing is how to work with agent scheduler. Thanks, Gary On Thu, Oct 24, 2013 at 11:56 AM, Gary Duan 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 > > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
I just wrote a short spec on the wiki page and link it to the blueprint. I should have done this when we registered the BP. Please let me know if you have any question. Thanks, Gary On Thu, Oct 24, 2013 at 5:35 PM, Gary Duan wrote: > Hi, Geoff, > > This is because I haven't added spec to the BP yet. > > Gary > > > On Thu, Oct 24, 2013 at 4:51 PM, Geoff Arnold wrote: > >> I’m getting a *“**Not allowed here”* error when I click through to the >> BP. (Yes, I’m subscribed.) >> >> On Oct 24, 2013, at 11:56 AM, Gary Duan 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 >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 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 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 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 > > > > > > > > > ___ > > > OpenStack-dev mailing list > > > OpenStack-dev@lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > Itsuro ODA > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 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 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 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 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 >>> >>> >>> ___ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
Hi, Geoff, This is because I haven't added spec to the BP yet. Gary On Thu, Oct 24, 2013 at 4:51 PM, Geoff Arnold wrote: > I’m getting a *“**Not allowed here”* error when I click through to the > BP. (Yes, I’m subscribed.) > > On Oct 24, 2013, at 11:56 AM, Gary Duan 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 > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
I’m getting a “Not allowed here” error when I click through to the BP. (Yes, I’m subscribed.) On Oct 24, 2013, at 11:56 AM, Gary Duan 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 > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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. * 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. I think the implementation would change depending on the service chaining discussion. 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 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 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 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 > > > > > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Itsuro ODA ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 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 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 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 >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 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 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 > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Neutron] L3 router service integration with Service Type Framework
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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
