Hi
A Good question in the current scenario of NFV/SDN, let me add cloud to the topic as well.
Few inputs to digest, as on date:
1. NFV maturity - All Telco Network functional applications are currently adaptable on virtualisation, means it can run on any HW including COTS or Virtual machine.
2. SDN maturity - SDN has matured independently, and implementation of SDN is in full swing in almost all enterprise segment, Still Telco adaptation is in initial stages
3. Cloud - Cloud is a combination of Virtualized environment , which is orchestratable, means Elasticity applicability.
4. Platform - VMware is the leader of the pack in non-open standard software, there are open stack, cloudily, etc, with OpenStack being adapted by many Telco Vendors.
Answering to the question:
How a telco needs to plan , i have shared this feedback in TMforum before also.
1. Choose the model of deployment - Virtualised, Cloud or Baremetal
2. Deploy NFVs or network functions - VNF creation will be based on NFV needs and sub functions, Telco applications does have multiple sub functions, unlike a IT applications.
3. Create SDN transformation journey, if not planned
4. Select a Orchestration platform - means cloud, IT clouds are all not open sourced such as IBM, Amazon, Microsoft, etc, we can very well deploy on such cloud platforms also.
5. Ensure COTS selected are carrier grade only.
6. Plan SDN and NFV functions working together under Cloud platform orchestration , there will be no meaning, if SDN and NFV function works together, as the network expands we need to expand the IP Core and HW together.
7. Plan entire above steps with 20 to 30% more dimensioning and prepare a roadmap for transition
8. Prepare a HLD, and followup with appropriate LLD for deployment.
Digital Journey has attained the highest level in IT segment, Telcos are still catching up, top telcos such as AT&T, Verizon, Orange, Vodafone have already in the journey to transformation, there is a need for all telcos to adapt as it will showcase a significant OPEX and CAPEX savings.
i have not gone into the detailing of any deep steps as every network will be different , it has to be designed according to the operator priorities and focus , strategies.
Let me know if you need any support , will be happy to help.
Regards//Karthik.
------------------------------
karthik s
Tata Communications Ltd
------------------------------
Original Message:
Sent: 02-07-2018 02:26
From: Angelo Baccarani
Subject: NFV adoption: avilability of solutions for COTS servers
Hi Yunus,
I think that yes, there are already various solutions available as "software running on COTS servers": as example, Empirix provides Service Assurance solutions in such architecture. In other words, it is already possible to deploy a single network node on COTS: but I would not call it "NFV"...
Mixing software on the same Compute Node through Virtual Machines orchestrated by a single entity (the "real" NFV...) is also feasible but much more complex because requires a careful evaluation of the interworking between the various components.
Best regards
------------------------------
Angelo Baccarani
Product Manager - NFV Service Assurance
Empirix - Italy
Original Message:
Sent: 02-06-2018 00:51
From: Saad Ullah Sheikh
Subject: NFV adoption: avilability of solutions for COTS servers
Hi Yunus,
I think your observations are quite relevant and infact many CSP's are thinking on it , i think the main problem here is that big vendors have started to control SDO's more than others and although it was against the very principle of Open source but recently in last six months in many ISG meetings we can see it happening . Decision on NFV License management , SLA working all proof still it is not easy to get an agreement on using S/W style for Network .But with ONAP , Sample VNF things are going to change very fast .
But as a CSP i suggest you should start your journey by thinking and building the platform first because at this time we can clearly see vendors making VNF to match the Infra and not on principle of decoupling with VNF package not standardized and infact VNF testing taking long time than expected .
So to sum up summary is simple build a platform around standard of Cloud and let vary work load match it . this is right direction and for decoupling i think till Sample VNF do not output some baseline its hard as VNF onboarding of Juniper Router will not be same exp as Brocade so target is far away .
SampleVNF - Home - SampleVNF - OPNFV Wiki
Opnfv |
remove preview |
|
SampleVNF - Home - SampleVNF - OPNFV Wiki |
This project provides a placeholder for various sample VNF (Virtual Network Function) development which includes example reference architecture and optimization methods related to VNF/Network service for high performance VNFs. This project provides benefits to other OPNFV projects like Functest, Models, yardstick etc to perform real life use-case based testing and NFVi characterization for the same. |
View this on Opnfv > |
|
|
------------------------------
Saad Ullah Sheikh
Chief Architect - Consultant NFV , SDN and Telco Cloud
Saudi Telecom Company
Original Message:
Sent: 10-11-2017 09:36
From: Yunus Celebiler
Subject: NFV adoption: avilability of solutions for COTS servers
Let me start with a qualifier: please forgive me if my question is naive.
There was a question as to why NFV adoption is not occuring faster, based on the premise that great progress has been made and therefore faster adoption would have been expected. In response there was some discussion about orchestration issues, and business cases for deploying virtual network functions into the cloud.
I have a naive question: in assessing the progress in NFV, what is truly the availability of network systems as software that can run on COTS servers? Because it seems to me the first basic step is just that, before getting to orchastrated, automated distributed, virtual network functions. In the IT world, before we had virtual machines, we had OS / hardware separation, with migration away from specialized hardware like Sun and Silicon Graphics in favor of COTS hardware. Has this happened yet for network equipment?
Great progress has been made in NFV perhaps, but are the basics in place? Can my company's next purchase of routers, which would typically be Juniper or Cisco proprietary dedicated hardware with porprietary OS/software, at this point be a purchase of COTS hardware + proprietary OS/software?
Are we there yet? (If so, I'll go let my network planning team know!) Forgive the naivety of my question. I honestly don't know.
Best regards,
Yunus
Yunus Çelebiler
CIO
Yunus.Celebiler@turknet.net.tr
TurkNet İletişim Hizmetleri A.Ş.
Tel: +90 212 355 17 00
Faks: +90 212 216 55 66
Bu elektronik posta ve onunla iletilen bütün dosyalar sadece göndericisi tarafından alması amaçlanan yetkili gerçek ya da tüzel kişinin kullanımı içindir. Eğer söz konusu yetkili alıcı değilseniz bu elektronik postanın içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız kesinlikle yasaktır ve bu elektronik postayı derhal silmeniz gerekmektedir. TurkNet bu mesajın içerdiği bilgilerin doğruluğu veya eksiksiz olduğu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne şekilde olursa olsun içeriğinden, iletilmesinden, alınmasından ve saklanmasından sorumlu değildir. Bu mesajdaki görüşler yalnızca gönderen kişiye aittir ve TurkNet'in görüşlerini yansıtmayabilir. Bu e-posta bilinen bütün bilgisayar virüslerine karşı taranmıştır.
________________________________________
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted. TurkNet makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TurkNet. This e-mail has been scanned for all known computer viruses.