Hi Sumit,<div><br></div><div>I probably missed to answer your email on this thread. My apologies for this.</div><div><br></div><div>The short answer is yes. If you associate a service_type to a router, advanced services attached to that router would be able to reach instances connected to each interface of the router. </div>
<div>So from the perspective of the "scope" of the advanced service, that would be the L3 domain defined by the router and all subnets attached to it.</div><div><br></div><div>Salvatore</div><div><br><div class="gmail_quote">
On 24 October 2012 06:40, Sumit Naiksatam <span dir="ltr"><<a href="mailto:sumitnaiksatam@gmail.com" target="_blank">sumitnaiksatam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><span style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">Hi Salvatore,</span><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">
<br></div><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">Thanks for posting your proposed design specification. It seems to me that service "insertion" in your model is achieved by associating a "service_type"  with a "router" entity; is my understanding correct? If so, would that service apply to every interface on that "router"?</div>

<div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif"><br></div><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">
Thanks,</div><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">~Sumit.</div><div style="color:rgb(34,34,34);font-size:13px;font-family:arial,sans-serif">
<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


From: Salvatore Orlando <<a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>><br>
Date: Tue, Oct 23, 2012 at 5:15 PM<br>
Subject: [openstack-dev] [Quantum] Advanced service insertion<br>
To: OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>><br>
<br>
<br>
Hi all,<br>
<br>
The blueprint for advanced services insertion has been registered and<br>
can be found here:<br>
<a href="https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion</a><br>
The design specification is about 75% complete - your feedback is more<br>
than welcome.<br>
<br>
Please use this email thread for discussing design details, unless you<br>
feel there's a more suitable medium.<br>
<br>
Regards,<br>
Salvatore<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>
<br>
<br>
<br>
<br>
--<br>
Mike Cohen<br>
Big Switch Networks<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br>
</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>