Open Stack

Hi Sumit,

I probably missed to answer your email on this thread. My apologies for
this.

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.
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.

Salvatore

On 24 October 2012 06:40, Sumit Naiksatam <sumitnaiksatam at gmail.com> wrote:

> Hi Salvatore,
>
> 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"?
>
> Thanks,
> ~Sumit.
>
>
>> From: Salvatore Orlando <sorlando at nicira.com>
>>> Date: Tue, Oct 23, 2012 at 5:15 PM
>>> Subject: [openstack-dev] [Quantum] Advanced service insertion
>>> To: OpenStack Development Mailing List <
>>> openstack-dev at lists.openstack.org>
>>>
>>>
>>> Hi all,
>>>
>>> The blueprint for advanced services insertion has been registered and
>>> can be found here:
>>> https://blueprints.launchpad.net/quantum/+spec/quantum-service-insertion
>>> The design specification is about 75% complete - your feedback is more
>>> than welcome.
>>>
>>> Please use this email thread for discussing design details, unless you
>>> feel there's a more suitable medium.
>>>
>>> Regards,
>>> Salvatore
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>>
>>> --
>>> Mike Cohen
>>> Big Switch Networks
>>>
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121105/b5ef0d53/attachment.html>