<div dir="ltr">Hi, Salvatore,<div><br></div><div>I guess 'router_service_type' extension is used together with 'router_service_insertion'.</div><div><br></div><div>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.</div>
<div><br></div><div>Thanks,</div><div>Gary</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 24, 2013 at 4:13 PM, Salvatore Orlando <span dir="ltr"><<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Gary,<div><br></div><div>In the context of the nvp plugin we use a mechanism for enabling 'advanced' capabilities of a router leveraging a 'router_service_type' extension.</div>
<div>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.</div>

<div><br></div><div>Is this similar to what you want to achieve with this blueprint?</div><div><br></div><div>Regards,</div><div>Salvatore</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On 25 October 2013 01:03, Gary Duan <span dir="ltr"><<a href="mailto:gduan@varmour.com" target="_blank">gduan@varmour.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, Oda-san,<div><br></div><div>Thanks for your response.</div><div><br></div><div>L3 agent function should remain the same, as one driver implementation of L3 router plugin.</div>

<div><br></div><div>My understanding is your lbaas driver can be running on top of L3 agent and LVS' own routing services. Is my understanding correct?</div>
<div><br></div><div>Thanks,</div><div>Gary</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 24, 2013 at 3:16 PM, Itsuro ODA <span dir="ltr"><<a href="mailto:oda@valinux.co.jp" target="_blank">oda@valinux.co.jp</a>></span> wrote:<br>


<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
We are going to implement 2-arm type lbaas using LVS, and have submitted<br>
the following BPs.<br>
<br>
<a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion" target="_blank">https://blueprints.launchpad.net/neutron/+spec/lbaas-support-routed-service-insertion</a><br>
<a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver" target="_blank">https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-driver</a><br>
<a href="https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-extra-features" target="_blank">https://blueprints.launchpad.net/neutron/+spec/lbaas-lvs-extra-features</a><br>
<br>
Maybe the first one is same as yours.<br>
We are happy if we just concentrate making a provider driver.<br>
<br>
Thanks.<br>
Itsuro Oda<br>
<div><div><br>
On Thu, 24 Oct 2013 11:56:53 -0700<br>
Gary Duan <<a href="mailto:gduan@varmour.com" target="_blank">gduan@varmour.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> I've registered a BP for L3 router service integration with service<br>
> framework.<br>
><br>
> <a href="https://blueprints.launchpad.net/neutron/+spec/l3-router-service-type" target="_blank">https://blueprints.launchpad.net/neutron/+spec/l3-router-service-type</a><br>
><br>
> In general, the implementation will align with how LBaaS is integrated with<br>
> the framework. One consideration we heard from several team members is to<br>
> be able to support vendor specific features and extensions in the service<br>
> plugin.<br>
><br>
> Any comment is welcome.<br>
><br>
> Thanks,<br>
> Gary<br>
<br>
</div></div><span><font color="#888888">--<br>
Itsuro ODA <<a href="mailto:oda@valinux.co.jp" target="_blank">oda@valinux.co.jp</a>><br>
</font></span><div><div><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>