<font size=2 face="sans-serif">Hi Virkram,</font>
<br>
<br><font size=2 face="sans-serif">Glad to hear that. Have you implemented
that?</font>
<br>
<br><font size=2 face="sans-serif">BR</font>
<br><font size=2 face="sans-serif">Alan</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">发件人:
</font><font size=1 face="sans-serif">Vikram Choudhary
<vikram.choudhary@huawei.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">收件人:
</font><font size=1 face="sans-serif">"lv.erchun@zte.com.cn"
<lv.erchun@zte.com.cn>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">抄送:
</font><font size=1 face="sans-serif">"OpenStack
Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org>,
"sumitnaiksatam@gmail.com" <sumitnaiksatam@gmail.com>,
Dhruv Dhody <dhruv.dhody@huawei.com>, "Dongfeng (C)" <albert.dongfeng@huawei.com>,
Kalyankumar Asangi <kalyana@huawei.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">日期:
</font><font size=1 face="sans-serif">2015/01/12
13:05</font>
<br><font size=1 color=#5f5f5f face="sans-serif">主题:
</font><font size=1 face="sans-serif">RE: [openstack-dev]
答复: Re: [neutron][AdvancedServices] Confusion about the solution
of the service chaining!</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hi Alan,<br>
<br>
We have also proposed an idea about SFC. <br>
For more details you can refer to </font></tt><a href=https://review.openstack.org/#/c/146315/><tt><font size=2>https://review.openstack.org/#/c/146315/</font></tt></a><tt><font size=2><br>
<br>
<br>
Thanks<br>
Vikram<br>
<br>
-----Original Message-----<br>
From: Sumit Naiksatam [</font></tt><a href=mailto:sumitnaiksatam@gmail.com><tt><font size=2>mailto:sumitnaiksatam@gmail.com</font></tt></a><tt><font size=2>]
<br>
Sent: 09 January 2015 01:39<br>
To: lv.erchun@zte.com.cn<br>
Cc: OpenStack Development Mailing List<br>
Subject: Re: [openstack-dev] 答复: Re: [neutron][AdvancedServices] Confusion
about the solution of the service chaining!<br>
<br>
Hi Alan,<br>
<br>
On Wed, Jan 7, 2015 at 9:54 PM, <lv.erchun@zte.com.cn> wrote:<br>
> Hi Sumit,<br>
><br>
> thanks for your reply, one more question,<br>
><br>
> If I just using the 'group-based-policy-service-chaining' to <br>
> developing the service chaining feuture, how to map the network <br>
> service in the neutron to the GBP model, because all the network <br>
> service we implemented are based on neutron model, but the <br>
> 'group-based-policy-service-chaining' setup the service chaining based
<br>
> on GBP model, so how can we setup the service chaining for network
<br>
> services based the neutron model using the 'group-based-policy-service-chaining'
?<br>
<br>
The current model and implementation leverage the Neutron services as is
(the model is actually agnostic of the service definition/implementation).
Will be happy to further discuss this, feel free to ping on #openstack-gbp.<br>
<br>
Thanks,<br>
~Sumit.<br>
<br>
><br>
> BR<br>
> Alan<br>
><br>
><br>
><br>
><br>
> 发件人: Sumit Naiksatam <sumitnaiksatam@gmail.com><br>
> 收件人: "OpenStack Development
Mailing List (not for usage questions)"<br>
> <openstack-dev@lists.openstack.org>,<br>
> 日期: 2015/01/08 10:46<br>
> 主题: Re: [openstack-dev] [neutron][AdvancedServices]
Confusion about<br>
> the solution of the service chaining!<br>
> ________________________________<br>
><br>
><br>
><br>
> Hi Alan,<br>
><br>
> Responses inline...<br>
><br>
> On Wed, Jan 7, 2015 at 4:25 AM, <lv.erchun@zte.com.cn>
wrote:<br>
>> Hi,<br>
>><br>
>> I want to confirm that how is the project about "Neutron
Services <br>
>> Insertion, Chaining, and Steering" going, I found that all
the code <br>
>> implementation about service insertion、service chaining and
traffic <br>
>> steering list in JunoPlan were Abandoned .<br>
>><br>
>> </font></tt><a href=https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan><tt><font size=2>https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan</font></tt></a><tt><font size=2><br>
>><br>
>> and I also found that we have a new project about GBP and <br>
>> group-based-policy-service-chaining be located at:<br>
>><br>
>><br>
>> </font></tt><a href="https://blueprints.launchpad.net/group-based-policy/+spec/group-based"><tt><font size=2>https://blueprints.launchpad.net/group-based-policy/+spec/group-based</font></tt></a><tt><font size=2><br>
>> -policy-abstraction<br>
>><br>
>><br>
>> </font></tt><a href="https://blueprints.launchpad.net/group-based-policy/+spec/group-based"><tt><font size=2>https://blueprints.launchpad.net/group-based-policy/+spec/group-based</font></tt></a><tt><font size=2><br>
>> -policy-service-chaining<br>
>><br>
>> so I'm confused with solution of the service chaining.<br>
>><br>
><br>
> Yes, the above two blueprints have been implemented and are available
<br>
> for consumption today as a part of the Group-based Policy codebase
and <br>
> release. The GBP model uses a policy trigger to drive the service
<br>
> composition and can accommodate different rendering policies like
<br>
> realization using NFV SFC.<br>
><br>
>> We are developing the service chaining feature, so we need to
know <br>
>> which one is the neutron's choice.<br>
><br>
> It would be great if you can provide feedback on the current <br>
> implementation, and perhaps participate and contribute as well.<br>
><br>
>> Are the blueprints about the service insertion, service chaining
and <br>
>> traffic steering list in JunoPlan all Abandoned ?<br>
>><br>
><br>
> Some aspects of this are perhaps a good fit in Neutron and others
are <br>
> not. We are looking forward to continuing the discussion on this topic
<br>
> on the areas which are potentially a good fit for Neutron (we have
had <br>
> this discussion before as well).<br>
><br>
>> BR<br>
>> Alan<br>
>><br>
>><br>
>><br>
>> --------------------------------------------------------<br>
>> ZTE Information Security Notice: The information contained in
this <br>
>> mail (and any attachment transmitted herewith) is privileged and
<br>
>> confidential and is intended for the exclusive use of the <br>
>> addressee(s). If you are not an intended recipient, any
disclosure, <br>
>> reproduction, distribution or other dissemination or use of the
<br>
>> information contained is strictly prohibited.<br>
>> If you have received this mail in error, please delete it and
notify <br>
>> us immediately.<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> OpenStack-dev@lists.openstack.org<br>
>> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
>><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> </font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
><br>
><br>
><br>
> --------------------------------------------------------<br>
> ZTE Information Security Notice: The information contained in this
<br>
> mail (and any attachment transmitted herewith) is privileged and <br>
> confidential and is intended for the exclusive use of the <br>
> addressee(s). If you are not an intended recipient, any disclosure,
<br>
> reproduction, distribution or other dissemination or use of the information
contained is strictly prohibited.<br>
> If you have received this mail in error, please delete it and notify
<br>
> us immediately.<br>
><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><pre><font color="blue">
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
</font></pre><br>