<div dir="ltr">So it's to add a wider approach to the whole "services" framework that got added in Grizzly?</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/6 P Balaji-B37839 <span dir="ltr"><<a href="mailto:B37839@freescale.com" target="_blank">B37839@freescale.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Stackers,<br>
<br>
Please give us your comments on BP for refining it further.<br>
<br>
Regards,<br>
Balaji.P<br>
<div class="im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: P Balaji-B37839<br>
Sent: Friday, May 03, 2013 4:25 PM<br>
To: 'Kyle Mestery (kmestery)'; OpenStack Development Mailing List<br>
Cc: Ravi Chunduru; Vetcha Sarat Babu-B37147; Addepalli Srini-B22160<br>
Subject: RE: [openstack-dev] [Quantum]Network Function Virtualization using OpenStack and Network Service Chain Implementation Blue-Print<br>
<br>
Yes, I agree that this blue-print is to focus on VM form-factor and NFV deployment using Quantum.<br>
<br>
We tried to bring in more modular and flexible approach so that tenants can have more options for choosing the vendor and their NFV appliances. And as well multiple vendors can use the same network service infrastructure create their own plug-ins for deploying their NFV appliances.<br>
<br>
Any comments on improving this further are most welcome.<br>
<br>
Regards,<br>
Balaji.P<br>
<br>
-----Original Message-----<br>
From: Kyle Mestery (kmestery) [mailto:<a href="mailto:kmestery@cisco.com">kmestery@cisco.com</a>]<br>
Sent: Friday, May 03, 2013 12:26 AM<br>
</div><div class="im HOEnZb">To: OpenStack Development Mailing List<br>
</div><div class="HOEnZb"><div class="h5">Cc: Ravi Chunduru; Vetcha Sarat Babu-B37147; P Balaji-B37839<br>
Subject: Re: [openstack-dev] [Quantum]Network Function Virtualization using OpenStack and Network Service Chain Implementation Blue-Print<br>
<br>
I agree with Sumit, but I would say that NFV focuses specifically on virtualizing network services, so I would expect this blueprint to focus on the virtual form factor. Seeing how this fits into the broader service insertion story will be a good first step.<br>
<br>
Thanks,<br>
Kyle<br>
<br>
On May 2, 2013, at 12:53 PM, Sumit Naiksatam <<a href="mailto:sumitnaiksatam@gmail.com">sumitnaiksatam@gmail.com</a>><br>
wrote:<br>
<br>
> We had a discussion on the topic of service chaining and insertion during the summit. You can find the details here:<br>
> Etherpad: <a href="https://etherpad.openstack.org/Quantum_Services'_Chaining_and_Insertion" target="_blank">https://etherpad.openstack.org/Quantum_Services'_Chaining_and_Insertion</a><br>
> Blueprint: <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-services-insertion-chaining-steering" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-services-insertion-chaining-steering</a><br>
><br>
> My first impression on quickly browsing through your attached document is that it focuses on the service provider abstractions and might be complementary to what we discussed in the above proposal during the summit. That said, it seems to me that your document makes an assumption that a service chain always manifest as a single multiservice appliance in a VM form-factor and in a single insertion mode. This is one valid use case, however the model should not be limited to this. One can have a combination of services in different insertion modes and realized on dedicated hardware or in software. Please the aforementioned blueprint/spec for such examples and a flexible model which captures this.<br>
><br>
> Thanks,<br>
> ~Sumit.<br>
><br>
> On Thu, May 2, 2013 at 9:37 AM, Ravi Chunduru <<a href="mailto:ravivsn@gmail.com">ravivsn@gmail.com</a>> wrote:<br>
> This is in continuation with the APIs I have shared couple of weeks ago in this link.<br>
><br>
> README.md<br>
><br>
> Balaji,<br>
> Glad to see the document coming along.<br>
> I suggest we create a google doc so that it is easy to collaborate with the openstack community.<br>
><br>
> Thanks,<br>
> -Ravi.<br>
><br>
><br>
> On Thu, May 2, 2013 at 6:11 AM, balaji patnala <<a href="mailto:patnala003@gmail.com">patnala003@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> It is glad to inform that we are publishing the Blue-Print for Network Function Virtualization using OpenStack and Network Service Chain Implementation.<br>
><br>
> We had couple of queries when we show cased it in ONS 2013 like guys from Midokura,Redhat etc are enquired about this blue print.<br>
><br>
> We would like to contribute this for Havana Release.<br>
><br>
> Regards,<br>
> Balaji.P<br>
><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>
><br>
><br>
><br>
> --<br>
> Ravi<br>
><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>
<br>
<br>
<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>
</div></div></blockquote></div><br></div>