. 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
, December 18, 2014 7:35 PM
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
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
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
that discussion with NFV for ‘Service-VM +
Openstack OVS related discussion”.
Regards,
keshava
From: Stephen Wong [mailto: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
[cid:image003.png@01D0145E.75813DF0]
I have some of the basic question w.r.t Service-VM running the NFV. (These
Service-VMs can be vNAT, vFW, vDPI, vRouting , vCPE etc ),
1. When these service-VM runs over the cloud (over OpenStack CN) each
will be treated as Routable entity in the
