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]
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<mailto: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<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--- Begin Message ---
Some of my perspective with [RP]
From: "A, Keshava" <keshav...@hp.com<mailto:keshav...@hp.com>>
Date: Wednesday, December 10, 2014 at 8:59 AM
To: Christopher Price
<christopher.pr...@ericsson.com<mailto:christopher.pr...@ericsson.com>>,
"opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>"
<opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>>,
"opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>"
<opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] Service VM v/s its basic framework
Hi Chris,
Thanks for your reply.
In my opinion it is very important to have common understanding how the
Service-VM should look .
1. There are many question coming-in like ‘OVS can be also part of the
Service-VM”?
[RP] It can, but the only advantage is if it can process NSH headers.
If multiple features(services) are running with-in one Service-VM, use ‘local
OVS to do service-chaining’.
(Of course it can be handled by internal routing table by setting Next-hop as
Next Service running with in that local-VM also, if routing is running in that
VM)
[RP] Then local OVS becomes a SFF. This is fine, I see no issues with it. Your
Service Path topology would include each (SFF, SF) tuple inside your service-VM
as a service hop.
2. OVS running in compute node:
a. Can be used to do ‘service chaining across Service-VM’ running with in
same compute Node ?
b. Service-VM running in different compute-nodes needs can be chained by
Service Layer.
[RP] As soon as a OVS (irrespective where it is) sends packets to Service
Functions it becomes a SFF. If you think like that everything becomes simpler.
With both 1 + 2 and ‘Service Layer running in NFV orchestration’ +
‘Service topology’ .
This ‘Service Layer’ will configures
a. ‘OpenStack Controller’ to configure OVS which it manages for Service
Chaining.
b. Service-VM , to chain the service within that VM itself.
[RP] I think Openstanck’s current layer 2 hop-by-hop Service Path diverges
considerably a departure from IETF’s proposal and consequently ODL
implementation. I think this is a good opportunity to align everything.
3. HA framework :
a. Service VMs will run in Active-Active mode or Active-Standby mode ?
b. How the incoming packet should be delivered ?
c. OpenStack should deliver the packet only to Active-VM ?
i. or to
both Active and Standby-VM together ?
ii. or first
to Standby-VM, from there to Standby-VM to deliver to Active-VM ?
d. Active-VM should control Standby-VM ?
[RP] Let’s think about SFF and SF. SFF controls where the packet are sent,
period. SFs has no saying in it.
e. Active-VM will control the network ?
f. Active-VM will be ahead of Standby-VM as for ‘live network
information is concerned ‘ ?
4. Can the Service-VM can run routing/Forwarding information to
OpenStack infrastructure ? Or it should be within that Service-VM itself ?
So it very important , what and how the Service-VM should look for from NFV
perspective.
Based on this NFV and OpenStack community should work together to address some
of these issues.
[cid:image003.png@01D014C8.9BA6F7D0]
Thanks & regards,
keshava
From: Christopher Price [mailto:christopher.pr...@ericsson.com]
Sent: Wednesday, December 10, 2014 3:17 PM
To: A, Keshava;
opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>;
opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] Service VM v/s its basic framework
Hi Keshava,
Good questions and you are right, some discussion is required to answer them.
As a first pass over your questions each service entity needs to be addressable
on the network for sure, if it requires to be routable is a question of the
service itself and the associated network design. I expect we will see a
number of common models surface as we build out our testing and infrastructure
pieces and methodologies for deploying and addressing the service VM’s
depending on the role and design of the services/functions themselves in the
network. I also expect to see common features emerge that will be deployed as
common frameworks as you have described in your e-mail.
At this time OPNFV has not arrived at or published any conclusions on these
although work is ongoing to establish founding principals. The tools and
components available in the platform will be introduced through the requirement
and collaborative development projects, the utilisation and proof of the tools
will be done in our test and performance projects.
/ Chris
From: "A, Keshava" <keshav...@hp.com<mailto:keshav...@hp.com>>
Date: Wednesday 10 December 2014 05:18
To:
"opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>"
<opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>>,
"opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>"
<opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] Service VM v/s its basic framework
[cid:image001.png@01D014C1.A152DBB0]
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 network ?
i.e, Each Service-VM will run its own routing protocol so that it is a
reachable entity in the network ?
2. Will there be any basic framework / basic elements that needs to run
in these VM ?
a. Each Service-VM should also its routing instance + L3 Forwarding ..
If so are they optional or mandatory
3. When these Service-VM runs (which may be part vCPE) then each service
packet will be carried till Service-VM or it will be handled in the OVS of the
compute node it self ?
Then how this will be handled for routing packet ?
4. If there are multiple ‘features running with in a Service-VM’ (example
NAT,FW,IPSEC),
a. Then depending on the prefix(tenant/user traffic) may need to chain
them differently .
i. Example
for tenant-1 packet prefix P1: Service execution may be NAT --> FW --> IPSEC
ii. Tennant-2
p2 : it may NAT->IPSEC->AAA
5. How the Service chain Execution, which may be running across multiple
Service-VM is controlled.
a. Is it controlled by configuring the OVS (Open V Switch ) running in
the compute node ?
b. When the Service-VMs are running across different Compute nodes they
need to be chained across OVS .
This needs to controlled by NFV Service Layer + OpenStack Controller ?
In my opinion there should be a some basic discussion on how these Service-VM’s
framework and how they needs to be chained ,which entity are mandatory in such
service to run over the cloud.
Please let me know if such discussion already happened ? Let me know others
opinion for the same.
Let me know my basic understanding is not correct ?
Thanks & regards,
keshava
_______________________________________________ opnfv-tech-discuss mailing list
opnfv-tech-disc...@lists.opnfv.org<mailto:opnfv-tech-disc...@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--- End Message ---
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
