Content deleted Content added
m VNF is a commonly used term, defined here. |
GreenC bot (talk | contribs) Move 1 url. Wayback Medic 2.5 per WP:URLREQ#prweb.com |
||
Line 63:
The NFV platform is the foundation for achieving efficient carrier-grade NFV solutions.<ref>{{cite web|title=Why Service Providers Need an NFV Platform | url=https://networkbuilders.intel.com/docs/NP2013113597EN_NFV_Platform_StraWhitePaper.pdf | archive-url=https://web.archive.org/web/20150526045311/https://networkbuilders.intel.com/docs/NP2013113597EN_NFV_Platform_StraWhitePaper.pdf | archive-date=2015-05-26|publisher=Intel Strategic paper}}</ref> It is a software platform running on standard multi-core hardware and built using open source software that incorporates carrier-grade features. The NFV platform software is responsible for dynamically reassigning VNFs due to failures and changes in traffic load, and therefore plays an important role in achieving high availability. There are numerous initiatives underway to specify, align and promote NFV carrier-grade capabilities such as ETSI NFV Proof of Concept,<ref>{{cite web|url=http://www.etsi.org/technologies-clusters/technologies/nfv/nfv-poc|title=NFV Proof of Concept|publisher=ETSI}}</ref> ATIS<ref>{{cite web|title=New NFV Forum Focused on Interoperability|url=http://www.lightreading.com/nfv/nfv-strategies/new-nfv-forum-focused-on-interoperability/d/d-id/710874|publisher=Light Reading|first1=Carol|last1=Wilson|date=16 September 2015}}</ref> Open Platform for NFV Project,<ref>{{cite web|url=https://www.opnfv.org/|title=OPNFV|publisher=Linux Foundation Collaborative Projects Foundation}}</ref> Carrier Network Virtualization Awards<ref>{{cite web|url=http://carriernetworkvirtualization.com/carrier-network-virtualization-awards/|title=Carrier Network Virtualization Awards|archive-url=https://web.archive.org/web/20150607213250/http://carriernetworkvirtualization.com/carrier-network-virtualization-awards/|archive-date=2015-06-07|date=December 2015}}</ref> and various supplier ecosystems.<ref>{{cite web|title=Wind River's Ecosystemic Solution to NFV and Orchestration|url=https://blog.cimicorp.com/?p=1788|publisher=CIMI Corporation Public Blog|first1=Tom|last1=Nolle|date=June 2014}}</ref>
The vSwitch, a key component of NFV platforms, is responsible for providing connectivity both VM-to-VM (between VMs) and between VMs and the outside network. Its performance determines both the bandwidth of the VNFs and the cost-efficiency of NFV solutions. The standard [[Open vSwitch]]'s (OVS) performance has shortcomings that must be resolved to meet the needs of NFVI solutions.<ref>{{cite web|url=http://networkheresy.com/2014/11/13/accelerating-open-vswitch-to-ludicrous-speed/|title=Accelerating Open vSwitch to "Ludicruos Speed"|work=Network Heresy: Tales of the network reformation|first1=Justin|last1=Pettit|date=11 November 2014}}</ref> Significant performance improvements are being reported by NFV suppliers for both OVS and Accelerated Open vSwitch (AVS) versions.<ref>{{cite web|title=Wind River Delivers Breakthrough Performance for Accelerated vSwitch Optimized for NFV|url=http://www.windriver.com/news/press/pr.html?ID=12801|publisher=Wind River News Room|date=May 2014}}</ref><ref>{{cite web|title=6WIND Announces Open vSwitch Acceleration for Red Hat Enterprise Linux OpenStack Platform|url=
Virtualization is also changing the way [[availability]] is specified, measured and achieved in NFV solutions. As VNFs replace traditional function-dedicated equipment, there is a shift from equipment-based availability to a service-based, end-to-end, layered approach.<ref>{{cite web|title=Network Functions Virtualization Challenges and Solutions|url=http://www.tmcnet.com/tmc/whitepapers/documents/whitepapers/2013/9377-network-functions-virtualization-challenges-solutions.pdf|publisher=Alcatel-Lucent|year=2013}}</ref><ref>{{cite web|title=NFV: The Myth of Application-Level High Availability|url=http://www.windriver.com/whitepapers/nfv-myth-app/|archive-url=https://web.archive.org/web/20151005122643/http://www.windriver.com/whitepapers/nfv-myth-app/|archive-date=2015-10-05|publisher=Wind River|date=May 2015}}</ref> Virtualizing network functions breaks the explicit coupling with specific equipment, therefore availability is defined by the availability of VNF services. Because NFV technology can virtualize a wide range of network function types, each with their own service availability expectations, NFV platforms should support a wide range of fault tolerance options. This flexibility enables CSPs to optimize their NFV solutions to meet any VNF availability requirement.
| |||