[openstack-dev] [NFV][Telco] Service VM v/s its basic framework

A, Keshava keshava.a at hp.com
Thu Dec 18 15:38:46 UTC 2014

Hi Yuriy Babenko,

I am  little worried about the direction we need to think about Service Chaining .

OpenStack will focus on Service Chaining of its own internal features (like FWaaS, LBaaS, VPNasS , L2 Gateway Aas .. ? )
will it consider Service Chaining of ‘Service-VM’ also ?

A. If we are considering ‘Service-VM’ service Chaining I have below points to mention ..

1.       Does the OpenStack needs to worry about Service-VM capability ?

2.       Does OpenStack worry if Service-VM also have OVS or not ?

3.       Does OpenStack worry if Service-VM has its own routing instance running in that ? Which can reconfigures the OVS flow .

4.       Can Service-VM configure OpenStack infrastructure OVS ?

5.       Can Service-VM have multiple features in it ? (Example DPI + FW + NAT ) …

Is Service-VM is = vNFVC  ?

B. If we are thinking of Service-chaining of ‘OpenStack only Services’ :
Then have below points

For a Tennant:

1.       Can Services be  binded to a particular Compute node(CN) ?

2.       A Tennant may not want to run/enable  all the Services on all CN’s.

Tennant may want to run  FWaaS, VPNaaS  on different CNs  so that Tenant get better  infrastructure performance.

Then are we considering chaining of Services per Tennant ?

3.       If so how to control this ? (Please consider that tenants VM can get migrated to different CNs)

Let me know others opinion.


From: Yuriy.Babenko at telekom.de [mailto:Yuriy.Babenko at telekom.de]
Sent: Thursday, December 18, 2014 7:35 PM
To: openstack-dev at lists.openstack.org; stephen.kf.wong at gmail.com
Subject: Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic framework

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:keshava.a at hp.com]
Gesendet: Mittwoch, 10. Dezember 2014 19:06
An: stephen.kf.wong at gmail.com<mailto:stephen.kf.wong at 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”.


From: Stephen Wong [mailto:stephen.kf.wong at 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:


    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.

- Stephen

On Wed, Dec 10, 2014 at 7:01 AM, Murali B <mbirru at gmail.com<mailto:mbirru at 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


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141218/2fcd3e8f/attachment.html>

More information about the OpenStack-dev mailing list