Network function virtualization - Revision history

OAbot: Open access bot: url-access updated in citation with #oabot.

2025-05-26T13:05:38Z

Open access bot: url-access updated in citation with #oabot.

← Previous revision		Revision as of 13:05, 26 May 2025
Line 142:		Line 142:

	==Performance study==		==Performance study==
	Recent performance study on NFV focused on the throughput, latency and jitter of virtualized network functions (VNFs), as well as NFV scalability in terms of the number of VNFs a single physical server can support.<ref>{{cite journal\|url=https://ieeexplore.ieee.org/document/7781548\|title=Toward High-Performance and Scalable Network Functions Virtualization\|year=2016\|doi=10.1109/MIC.2016.111\|last1=Wang\|first1=Chengwei\|last2=Spatscheck\|first2=Oliver\|last3=Gopalakrishnan\|first3=Vijay\|last4=Xu\|first4=Yang\|last5=Applegate\|first5=David\|journal=IEEE Internet Computing\|volume=20\|issue=6\|pages=10–20\|s2cid=15518060}}</ref>		Recent performance study on NFV focused on the throughput, latency and jitter of virtualized network functions (VNFs), as well as NFV scalability in terms of the number of VNFs a single physical server can support.<ref>{{cite journal\|url=https://ieeexplore.ieee.org/document/7781548\|title=Toward High-Performance and Scalable Network Functions Virtualization\|year=2016\|doi=10.1109/MIC.2016.111\|last1=Wang\|first1=Chengwei\|last2=Spatscheck\|first2=Oliver\|last3=Gopalakrishnan\|first3=Vijay\|last4=Xu\|first4=Yang\|last5=Applegate\|first5=David\|journal=IEEE Internet Computing\|volume=20\|issue=6\|pages=10–20\|s2cid=15518060\|url-access=subscription}}</ref>
	Open source NFV platforms are available, one representative is openNetVM.<ref name="OpenNetVM">{{cite journal\|title=OpenNetVM: A Platform for High Performance Network Service Chains\|url=http://faculty.cs.gwu.edu/timwood/papers/16-HotMiddlebox-onvm.pdf\|doi=10.1145/2940147.2940155\|doi-access=free\|s2cid=13706879}}</ref> openNetVM is a high performance NFV platform based on DPDK and Docker containers. openNetVM provides a flexible framework for deploying network functions and interconnecting them to build service chains. openNetVM is an open source version of the NetVM platform described in NSDI 2014 and HotMiddlebox 2016 papers, released under the BSD license. The source code can be found at GitHub:openNetVM<ref>{{cite web\|url=https://github.com/sdnfv/openNetVM\|title=GitHub- OpenNetVM\|website=[[GitHub]]}}</ref>		Open source NFV platforms are available, one representative is openNetVM.<ref name="OpenNetVM">{{cite journal\|title=OpenNetVM: A Platform for High Performance Network Service Chains\|url=http://faculty.cs.gwu.edu/timwood/papers/16-HotMiddlebox-onvm.pdf\|doi=10.1145/2940147.2940155\|doi-access=free\|s2cid=13706879}}</ref> openNetVM is a high performance NFV platform based on DPDK and Docker containers. openNetVM provides a flexible framework for deploying network functions and interconnecting them to build service chains. openNetVM is an open source version of the NetVM platform described in NSDI 2014 and HotMiddlebox 2016 papers, released under the BSD license. The source code can be found at GitHub:openNetVM<ref>{{cite web\|url=https://github.com/sdnfv/openNetVM\|title=GitHub- OpenNetVM\|website=[[GitHub]]}}</ref>

GreenC bot: Reformat 1 archive link. Wayback Medic 2.5 per WP:USURPURL and JUDI batch #23aa

2025-02-15T21:52:44Z

Reformat 1 archive link. Wayback Medic 2.5 per WP:USURPURL and JUDI batch #23aa

← Previous revision		Revision as of 21:52, 15 February 2025
Line 57:		Line 57:

	==Industry impact==		==Industry impact==
	NFV has proven a popular standard even in its infancy. Its immediate applications are numerous, such as virtualization of [[mobile base station]]s, [[platform as a service]] (PaaS), [[content delivery network]]s (CDN), fixed access and home environments.<ref>{{cite web\|title=Network Functions Virtualization (NFV) Use Cases\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf}}</ref> The potential benefits of NFV is anticipated to be significant. Virtualization of network functions deployed on general purpose standardized hardware is expected to reduce capital and operational expenditures, and service and product introduction times.<ref name="benefits">{{cite web\|title=What's NFV – Network Functions Virtualization?\|url=http://www.sdncentral.com/whats-network-functions-virtualization-nfv/\|publisher=SDN Central}}</ref><ref>{{cite web\|title=Carrier Network Virtualization\|url=http://carriernetworkvirtualization.com/company/network-functions-virtualisation-isg-nfv-etsi/\|publisher=ETSI news}}</ref> Many major network equipment vendors have announced support for NFV.<ref>{{Cite news \|title= Openwave Exec Discusses the Benefits, Challenges of NFV & SDN \|work= Article \|url= http://www.sdnzone.com/topics/software-defined-network/articles/359936-openwave-exec-discusses-benefits-challenges-nfv-sdn.htm \|date= 12 November 2013 \|access-date= 22 November 2013 \|archive-url= https://web.archive.org/web/20160303214633/http://www.sdnzone.com/topics/software-defined-network/articles/359936-openwave-exec-discusses-benefits-challenges-nfv-sdn.htm \|archive-date= 3 March 2016 \|url-status= ~~dead~~ }}</ref> This has coincided with NFV announcements from major software suppliers who provide the NFV platforms used by equipment suppliers to build their NFV products.<ref>{{cite web\|url=http://www.serviceprovideritreport.com/author.asp?section_id=3098\|title=Middleware for the NFV Generation\|publisher=Service Provider IT Report\|first=Lee\|last=Doyle}}</ref><ref>{{cite web\|url=http://www.policychargingcontrol.com/1643-wind-river-s-launches-nfv-ecosystem-program-with-initial-five-industry-leaders\| title=Wind River Launches NFV Ecosystem Program with Five Industry Leaders\|publisher=PCC Mobile Broadband\|first1=Ray\|last1=Sharma}}</ref>		NFV has proven a popular standard even in its infancy. Its immediate applications are numerous, such as virtualization of [[mobile base station]]s, [[platform as a service]] (PaaS), [[content delivery network]]s (CDN), fixed access and home environments.<ref>{{cite web\|title=Network Functions Virtualization (NFV) Use Cases\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf}}</ref> The potential benefits of NFV is anticipated to be significant. Virtualization of network functions deployed on general purpose standardized hardware is expected to reduce capital and operational expenditures, and service and product introduction times.<ref name="benefits">{{cite web\|title=What's NFV – Network Functions Virtualization?\|url=http://www.sdncentral.com/whats-network-functions-virtualization-nfv/\|publisher=SDN Central}}</ref><ref>{{cite web\|title=Carrier Network Virtualization\|url=http://carriernetworkvirtualization.com/company/network-functions-virtualisation-isg-nfv-etsi/\|publisher=ETSI news}}</ref> Many major network equipment vendors have announced support for NFV.<ref>{{Cite news \|title= Openwave Exec Discusses the Benefits, Challenges of NFV & SDN \|work= Article \|url= http://www.sdnzone.com/topics/software-defined-network/articles/359936-openwave-exec-discusses-benefits-challenges-nfv-sdn.htm \|date= 12 November 2013 \|access-date= 22 November 2013 \|archive-url= https://web.archive.org/web/20160303214633/http://www.sdnzone.com/topics/software-defined-network/articles/359936-openwave-exec-discusses-benefits-challenges-nfv-sdn.htm \|archive-date= 3 March 2016 \|url-status= usurped }}</ref> This has coincided with NFV announcements from major software suppliers who provide the NFV platforms used by equipment suppliers to build their NFV products.<ref>{{cite web\|url=http://www.serviceprovideritreport.com/author.asp?section_id=3098\|title=Middleware for the NFV Generation\|publisher=Service Provider IT Report\|first=Lee\|last=Doyle}}</ref><ref>{{cite web\|url=http://www.policychargingcontrol.com/1643-wind-river-s-launches-nfv-ecosystem-program-with-initial-five-industry-leaders\| title=Wind River Launches NFV Ecosystem Program with Five Industry Leaders\|publisher=PCC Mobile Broadband\|first1=Ray\|last1=Sharma}}</ref>

	However, to realize the anticipated benefits of virtualization, network equipment vendors are improving IT virtualization technology to incorporate carrier-grade attributes required to achieve [[high availability]], scalability, performance, and effective network management capabilities.<ref>{{cite web\|title=Carrier-Grade Reliability—A "Must-Have" for NFV Success\|url=http://electronicdesign.com/communications/carrier-grade-reliability-must-have-nfv-success\|publisher=Electronic Design\|first1=Charlie\|last1=Ashton\|date=January 2015}}</ref> To minimize the total cost of ownership (TCO), carrier-grade features must be implemented as efficiently as possible. This requires that NFV solutions make efficient use of redundant resources to achieve five-nines availability (99.999%),<ref>{{cite web\|title=5 must-have attributes of an NFV platform\|url=http://www2.alcatel-lucent.com/techzine/5-must-attributes-nfv-platform/ \|archive-url=https://web.archive.org/web/20150526044023/http://www2.alcatel-lucent.com/techzine/5-must-attributes-nfv-platform/ \|archive-date=2015-05-26\|publisher=Techzine, Alcatel-Lucent\|first1=Andreas\|last1=Lemke\|date=November 2014}}</ref> and of computing resource without compromising performance predictability.		However, to realize the anticipated benefits of virtualization, network equipment vendors are improving IT virtualization technology to incorporate carrier-grade attributes required to achieve [[high availability]], scalability, performance, and effective network management capabilities.<ref>{{cite web\|title=Carrier-Grade Reliability—A "Must-Have" for NFV Success\|url=http://electronicdesign.com/communications/carrier-grade-reliability-must-have-nfv-success\|publisher=Electronic Design\|first1=Charlie\|last1=Ashton\|date=January 2015}}</ref> To minimize the total cost of ownership (TCO), carrier-grade features must be implemented as efficiently as possible. This requires that NFV solutions make efficient use of redundant resources to achieve five-nines availability (99.999%),<ref>{{cite web\|title=5 must-have attributes of an NFV platform\|url=http://www2.alcatel-lucent.com/techzine/5-must-attributes-nfv-platform/ \|archive-url=https://web.archive.org/web/20150526044023/http://www2.alcatel-lucent.com/techzine/5-must-attributes-nfv-platform/ \|archive-date=2015-05-26\|publisher=Techzine, Alcatel-Lucent\|first1=Andreas\|last1=Lemke\|date=November 2014}}</ref> and of computing resource without compromising performance predictability.

VulcanSphere: Changing short description from "Creation of functions which may be chained to deliver communication services" to "Type of computing virtualization"

2024-12-09T12:26:22Z

Changing short description from "Creation of functions which may be chained to deliver communication services" to "Type of computing virtualization"

← Previous revision		Revision as of 12:26, 9 December 2024
Line 1:		Line 1:
	{{Short description\|~~Creation~~ of ~~functions~~ ~~which may be chained to deliver communication services~~}}		{{Short description\|Type of computing virtualization}}
	'''Network functions virtualization''' ('''NFV''')<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' ('''NFV''')<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

Widefox: /* top */ bold alt article name per MOS

2024-11-24T22:07:13Z

top: bold alt article name per MOS

← Previous revision		Revision as of 22:07, 24 November 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' ('''NFV''')<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

Frap at 17:47, 6 November 2024

2024-11-06T17:47:49Z

← Previous revision		Revision as of 17:47, 6 November 2024
Line 83:		Line 83:
	The full set of published specifications is summarized in the table below.		The full set of published specifications is summarized in the table below.
	{\| class="wikitable"		{\| class="wikitable"
	\|Specification		!Specification
	\|Title		!Title
	\|-		\|-
	\|[https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/ ETSI GS NFV-SOL 001]		\|[https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/001/ ETSI GS NFV-SOL 001]
Line 145:		Line 145:
	Open source NFV platforms are available, one representative is openNetVM.<ref name="OpenNetVM">{{cite journal\|title=OpenNetVM: A Platform for High Performance Network Service Chains\|url=http://faculty.cs.gwu.edu/timwood/papers/16-HotMiddlebox-onvm.pdf\|doi=10.1145/2940147.2940155\|doi-access=free\|s2cid=13706879}}</ref> openNetVM is a high performance NFV platform based on DPDK and Docker containers. openNetVM provides a flexible framework for deploying network functions and interconnecting them to build service chains. openNetVM is an open source version of the NetVM platform described in NSDI 2014 and HotMiddlebox 2016 papers, released under the BSD license. The source code can be found at GitHub:openNetVM<ref>{{cite web\|url=https://github.com/sdnfv/openNetVM\|title=GitHub- OpenNetVM\|website=[[GitHub]]}}</ref>		Open source NFV platforms are available, one representative is openNetVM.<ref name="OpenNetVM">{{cite journal\|title=OpenNetVM: A Platform for High Performance Network Service Chains\|url=http://faculty.cs.gwu.edu/timwood/papers/16-HotMiddlebox-onvm.pdf\|doi=10.1145/2940147.2940155\|doi-access=free\|s2cid=13706879}}</ref> openNetVM is a high performance NFV platform based on DPDK and Docker containers. openNetVM provides a flexible framework for deploying network functions and interconnecting them to build service chains. openNetVM is an open source version of the NetVM platform described in NSDI 2014 and HotMiddlebox 2016 papers, released under the BSD license. The source code can be found at GitHub:openNetVM<ref>{{cite web\|url=https://github.com/sdnfv/openNetVM\|title=GitHub- OpenNetVM\|website=[[GitHub]]}}</ref>

	==Cloud-native ~~Network~~ ~~Functions~~==		==Cloud-native network functions==
	From 2018, many VNF providers began to migrate many of their VNFs to a container-based architecture. Such VNFs also known as [[Cloud-Native Network Function]]s (CNF) utilize many innovations deployed commonly on internet infrastructure. These include auto-scaling, supporting a continuous delivery / DevOps deployment model, and efficiency gains by sharing common services across platforms. Through service discovery and orchestration, a network based on CNFs will be more resilient to infrastructure resource failures. Utilizing containers, and thus dispensing with the overhead inherent in traditional virtualization through the elimination of the [[Hardware virtualization\|guest OS]] can greatly increase infrastructure resource efficiency.<ref>{{Cite web\|title=Cloud-Native Network Functions\|url=https://www.cisco.com/c/en/us/solutions/service-provider/industry/cable/cloud-native-network-functions.html\|access-date=1 April 2021\|website=Cisco}}</ref>		From 2018, many VNF providers began to migrate many of their VNFs to a container-based architecture. Such VNFs also known as [[Cloud-Native Network Function]]s (CNF) utilize many innovations deployed commonly on internet infrastructure. These include auto-scaling, supporting a continuous delivery / DevOps deployment model, and efficiency gains by sharing common services across platforms. Through service discovery and orchestration, a network based on CNFs will be more resilient to infrastructure resource failures. Utilizing containers, and thus dispensing with the overhead inherent in traditional virtualization through the elimination of the [[Hardware virtualization\|guest OS]] can greatly increase infrastructure resource efficiency.<ref>{{Cite web\|title=Cloud-Native Network Functions\|url=https://www.cisco.com/c/en/us/solutions/service-provider/industry/cable/cloud-native-network-functions.html\|access-date=1 April 2021\|website=Cisco}}</ref>

Tule-hog: Undid revision 1243645730 by 189.203.51.234 (talk) - WP:DIS

2024-09-25T03:23:38Z

Undid revision 1243645730 by 189.203.51.234 (talk) - WP:DIS

← Previous revision		Revision as of 03:23, 25 September 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>

189.203.51.234 at 17:18, 2 September 2024

2024-09-02T17:18:47Z

← Previous revision		Revision as of 17:18, 2 September 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	~~'''Network functions virtualization''' (NFV)~~<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> ~~is a~~ [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. ~~A '''virtualized network function''', or '''VNF''', is implemented within one or more~~ [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>

GreenC bot: Move 1 url. Wayback Medic 2.5 per WP:URLREQ#prweb.com

2024-08-15T06:06:25Z

Move 1 url. Wayback Medic 2.5 per WP:URLREQ#prweb.com

← Previous revision		Revision as of 06:06, 15 August 2024
Line 63:		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 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=~~http~~://www.prweb.com/releases/~~2014/04~~/prweb11768622.htm\|publisher=PRweb\|date=April 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=https://www.prweb.com/releases/6wind_announces_open_vswitch_acceleration_for_red_hat_enterprise_linux_openstack_platform/prweb11768622.htm\|publisher=PRweb\|date=April 2014}}</ref>

	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.		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.

Madacs: VNF is a commonly used term, defined here.

2024-04-30T09:41:02Z

VNF is a commonly used term, defined here.

← Previous revision		Revision as of 09:41, 30 April 2024
Line 2:		Line 2:
	'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A virtualized network function, or VNF, is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>

JJMC89 bot III: Removing :Category:Emerging technologies per Wikipedia:Categories for discussion/Log/2023 November 29#Category:Emerging technologies

2023-12-12T10:29:16Z

Removing Category:Emerging technologies per Wikipedia:Categories for discussion/Log/2023 November 29#Category:Emerging technologies

← Previous revision		Revision as of 10:29, 12 December 2023
Line 164:		Line 164:
	* [https://www.ibm.com/services/network/what-is-nfv What are the benefits of NFV?]		* [https://www.ibm.com/services/network/what-is-nfv What are the benefits of NFV?]

	[[Category:Emerging technologies]]
	[[Category:Network architecture]]		[[Category:Network architecture]]

← Previous revision		Revision as of 22:07, 24 November 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' ('''NFV''')<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

← Previous revision		Revision as of 03:23, 25 September 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>

← Previous revision		Revision as of 17:18, 2 September 2024
Line 1:		Line 1:
	{{Short description\|Creation of functions which may be chained to deliver communication services}}		{{Short description\|Creation of functions which may be chained to deliver communication services}}
	~~'''Network functions virtualization''' (NFV)~~<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> ~~is a~~ [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. ~~A '''virtualized network function''', or '''VNF''', is implemented within one or more~~ [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>

← Previous revision		Revision as of 06:06, 15 August 2024
Line 63:		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 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=~~http~~://www.prweb.com/releases/~~2014/04~~/prweb11768622.htm\|publisher=PRweb\|date=April 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=https://www.prweb.com/releases/6wind_announces_open_vswitch_acceleration_for_red_hat_enterprise_linux_openstack_platform/prweb11768622.htm\|publisher=PRweb\|date=April 2014}}</ref>

	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.		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.

← Previous revision		Revision as of 09:41, 30 April 2024
Line 2:		Line 2:
	'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.		'''Network functions virtualization''' (NFV)<ref>{{Cite web \| url=http://www.etsi.org/technologies-clusters/technologies/nfv \|title = ETSI - Standards for NFV - Network Functions Virtualisation \| NFV Solutions}}</ref> is a [[network architecture]] concept that leverages IT [[virtualization]] technologies to virtualize entire classes of [[network node]] functions into building blocks that may connect, or chain together, to create and deliver communication services.

	NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A virtualized network function, or VNF, is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.		NFV relies upon traditional server-[[virtualization]] techniques such as those used in enterprise IT. A '''virtualized network function''', or '''VNF''', is implemented within one or more [[virtual machines]] or [[OS-level virtualization\|containers]] running different software and processes, on top of commercial off the shelf (COTS) high-volume servers, switches and storage devices, or even [[cloud computing]] infrastructure, instead of having custom hardware appliances for each network function thereby avoiding vendor lock-in.

	For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>		For example, a virtual [[session border controller]] could be deployed to protect a network without the typical cost and complexity of obtaining and installing physical network protection units. Other examples of NFV include virtualized [[Network Load Balancing\|load balancers]], [[Firewall (computing)\|firewalls]], [[Intrusion detection system\|intrusion detection devices]] and [[WAN optimization\|WAN accelerators]] to name a few.<ref>{{cite web\|title=Network Functions Virtualisation (NFV); Use NFV is present and SDN is future\|url=http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf\|access-date=6 June 2014}}</ref>