Thank you Vikram, Could you or somebody please provide the access the full specification document
Thanks -Murali On Mon, Dec 22, 2014 at 11:48 AM, Vikram Choudhary < vikram.choudh...@huawei.com> wrote: > > Hi Murali, > > > > We have proposed service function chaining idea using open flow. > > > https://blueprints.launchpad.net/neutron/+spec/service-function-chaining-using-openflow > > > > Will submit the same for review soon. > > > > Thanks > > Vikram > > > > *From:* yuriy.babe...@telekom.de [mailto:yuriy.babe...@telekom.de] > *Sent:* 18 December 2014 19:35 > *To:* openstack-dev@lists.openstack.org; stephen.kf.w...@gmail.com > *Subject:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic > framework > > > > Hi, > > in the IRC meeting yesterday we agreed to work on the use-case for service > function chaining as it seems to be important for a lot of participants > [1]. > > We will prepare the first draft and share it in the TelcoWG Wiki for > discussion. > > There is one blueprint in openstack on that in [2] > > > > [1] > http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-12-17-14.01.txt > > [2] > https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-service-chaining > > > > Kind regards/Mit freundlichen Grüßen > > Yuriy Babenko > > > > *Von:* A, Keshava [mailto:keshav...@hp.com <keshav...@hp.com>] > *Gesendet:* Mittwoch, 10. Dezember 2014 19:06 > *An:* stephen.kf.w...@gmail.com; OpenStack Development Mailing List (not > for usage questions) > *Betreff:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic > framework > > > > Hi Murali, > > > > There are many unknows w.r.t ‘Service-VM’ and how it should from NFV > perspective. > In my opinion it was not decided how the Service-VM framework should be. > > Depending on this we at OpenStack also will have impact for ‘Service > Chaining’. > > *Please find the mail attached w.r.t that discussion with NFV for > ‘Service-VM + Openstack OVS related discussion”.* > > > > > > Regards, > > keshava > > > > *From:* Stephen Wong [mailto:stephen.kf.w...@gmail.com > <stephen.kf.w...@gmail.com>] > *Sent:* Wednesday, December 10, 2014 10:03 PM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic > framework > > > > Hi Murali, > > > > There is already a ServiceVM project (Tacker), currently under > development on stackforge: > > > > https://wiki.openstack.org/wiki/ServiceVM > > > > If you are interested in this topic, please take a look at the wiki > page above and see if the project's goals align with yours. If so, you are > certainly welcome to join the IRC meeting and start to contribute to the > project's direction and design. > > > > Thanks, > > - Stephen > > > > > > On Wed, Dec 10, 2014 at 7:01 AM, Murali B <mbi...@gmail.com> wrote: > > Hi keshava, > > > > We would like contribute towards service chain and NFV > > > > Could you please share the document if you have any related to service VM > > > > The service chain can be achieved if we able to redirect the traffic to > service VM using ovs-flows > > > > in this case we no need to have routing enable on the service VM(traffic > is redirected at L2). > > > > All the tenant VM's in cloud could use this service VM services by adding > the ovs-rules in OVS > > > > > > Thanks > > -Murali > > > > > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
