Open Stack

Folks,

As far as I see, it's similar of what we planned to implement for LBaaS and
other services.
Currently we're planning to implement in the scope of
https://blueprints.launchpad.net/quantum/+spec/device-inventory-management

Thanks,
Eugene.


On Mon, May 6, 2013 at 6:16 PM, Endre Karlson <endre.karlson at gmail.com>wrote:

> So it's to add a wider approach to the whole "services" framework that got
> added in Grizzly?
>
>
> 2013/5/6 P Balaji-B37839 <B37839 at freescale.com>
>
>> Hi Stackers,
>>
>> Please give us your comments on BP for refining it further.
>>
>> Regards,
>> Balaji.P
>>
>>
>> -----Original Message-----
>> From: P Balaji-B37839
>> Sent: Friday, May 03, 2013 4:25 PM
>> To: 'Kyle Mestery (kmestery)'; OpenStack Development Mailing List
>> Cc: Ravi Chunduru; Vetcha Sarat Babu-B37147; Addepalli Srini-B22160
>> Subject: RE: [openstack-dev] [Quantum]Network Function Virtualization
>> using OpenStack and Network Service Chain Implementation Blue-Print
>>
>> Yes, I agree that this blue-print is to focus on VM form-factor and NFV
>> deployment using Quantum.
>>
>> 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.
>>
>> Any comments on improving this further are most welcome.
>>
>> Regards,
>> Balaji.P
>>
>> -----Original Message-----
>> From: Kyle Mestery (kmestery) [mailto:kmestery at cisco.com]
>> Sent: Friday, May 03, 2013 12:26 AM
>> To: OpenStack Development Mailing List
>> Cc: Ravi Chunduru; Vetcha Sarat Babu-B37147; P Balaji-B37839
>> Subject: Re: [openstack-dev] [Quantum]Network Function Virtualization
>> using OpenStack and Network Service Chain Implementation Blue-Print
>>
>> 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.
>>
>> Thanks,
>> Kyle
>>
>> On May 2, 2013, at 12:53 PM, Sumit Naiksatam <sumitnaiksatam at gmail.com>
>>  wrote:
>>
>> > We had a discussion on the topic of service chaining and insertion
>> during the summit. You can find the details here:
>> > Etherpad:
>> https://etherpad.openstack.org/Quantum_Services'_Chaining_and_Insertion
>> > Blueprint:
>> https://blueprints.launchpad.net/quantum/+spec/quantum-services-insertion-chaining-steering
>> >
>> > 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.
>> >
>> > Thanks,
>> > ~Sumit.
>> >
>> > On Thu, May 2, 2013 at 9:37 AM, Ravi Chunduru <ravivsn at gmail.com>
>> wrote:
>> > This is in continuation with the APIs I have shared couple of weeks ago
>> in this link.
>> >
>> > README.md
>> >
>> > Balaji,
>> >   Glad to see the document coming along.
>> > I suggest we create a google doc so that it is easy to collaborate with
>> the openstack community.
>> >
>> > Thanks,
>> > -Ravi.
>> >
>> >
>> > On Thu, May 2, 2013 at 6:11 AM, balaji patnala <patnala003 at gmail.com>
>> wrote:
>> > Hi,
>> >
>> > It is glad to inform that we are publishing the Blue-Print for Network
>> Function Virtualization using OpenStack and Network Service Chain
>> Implementation.
>> >
>> > 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.
>> >
>> > We would like to contribute this for Havana Release.
>> >
>> > Regards,
>> > Balaji.P
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> >
>> >
>> > --
>> > Ravi
>> >
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> _______________________________________________
> 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/20130506/27b65a39/attachment.html>