network function virtualization
TRANSCRIPT
Network Function Virtualization Satish Chavan
Network Functions Virtualization – Definition
The concept originated from service providers who were looking to accelerate the deployment of new network services to support their revenue and growth objectives. The constraints of hardware-based appliances led them to applying standard IT virtualization technologies to their networks. To accelerate progress towards this common goal, several providers came together and created the European Telecommunications Standards Institute (ETSI). The ETSI Industry Specification Group for Network Functions Virtualization (ETSI ISG NFV), a group charged with developing requirements and architecture for virtualization for various functions within telecoms networks, such as standards like NFV MANO. ETSI is also instrumental in collaborative projects like the newly announced OPNFV. Network functions virtualization (NFV) is a network architecture concept that uses the technologies of IT virtualization to virtualized entire classes of network node functions into building blocks that may connect, or chain together, to create communication services.
Benefits The Benefits of Network Functions Virtualization NFV virtualizes network services via software to enable operators to: 1. Reduce CapEx: reducing the need to purchase purpose-built hardware and supporting
pay-as-you-grow models to eliminate wasteful over-provisioning.
2. Reduce OpEX: reducing space, power and cooling requirements of equipment and simplifying the roll out and management of network services.
3. Accelerate Time-to-Market: reducing the time to deploy new networking services to support changing business requirements, seize new market opportunities and improve return on investment of new services. Also lowers the risks associated with rolling out new services, allowing providers to easily trial and evolve services to determine what best meets the needs of customers.
4. Deliver Agility and Flexibility: quickly scale up or down services to address changing demands; support innovation by enabling services to be delivered via software on any industry-standard server hardware.
NFV framework NFV framework consists of three main components:
1. Virtualized network functions (VNFs) -are software implementations of network functions that can be deployed on a network functions virtualization infrastructure (NFVI).
2. Network functions virtualization infrastructure (NFVI) is the totality of all hardware and software components that build the environment where VNFs are deployed. The NFV infrastructure can span several locations. The network providing connectivity between these locations is considered as part of the NFV infrastructure.
3. Network functions virtualization management and orchestration architectural framework (NFV-MANO Architectural Framework) is the collection of all functional blocks, data repositories used by these blocks, and reference points and interfaces through which these functional blocks exchange information for the purpose of managing and orchestrating NFVI and VNFs.
The building block for both the NFVI and the NFV-MANO is the NFV platform. In the NFVI role, it consists of both virtual and physical processing and storage resources, and virtualization software. In its NFV-MANO role it consists of VNF and NFVI managers and virtualization software operating on a hardware controller. The NFV platform implements carrier-grade features used to manage and monitor the platform components, recover from failures and provide effective security - all required for the public carrier network.
Architecture
Life Cycle and Evolution
NFVIaaS
Cases
Legacy vs NFV Deployment Legacy -Serial & Iterative Process •Procure New Hardware (Dedicated /proprietary for specific network function, usually take long time on delivery, Hardware reuse is impossible, especially for different vendor) •Finding Space and Power required •Install Hardware • Commissioning, Integrate, Operate •Redo the whole process for the other or new network function
NFV Deployment Parallel Process •One hardware (x86 COTS) can be used by several network function •Hardware procurement and delivery is faster, since the hardware is a common commodity • Procure Hardware, Finding Space & Power, Installation, Commissioning, only needed to be done at the initial deployment •All Network Function is only software based and can be Install remotely and parallel •Fail fast support to achieve faster time-to-market
Ref: http://www.slideshare.net/sdnrgitb/network-function-virtualization-telkomsel-perspective-sdn-nfv-day-itb-2016
SDN VS NFV
SDN • Separate control plane from data plane in forwarding elements
• API-driven forwarding rules in data plane
• Initiated by Enterprise Sector
• Focused on L2-L4 forwarding
•Commoditize routers and switches control
• Make control plane programmable
• Industry Standards SDN Open Networking Foundation (ONF) www.opennetworking.org
NFV • Porting control & forwarding plane network functions to COTS HW
• Dynamic provisioning and orchestration of network functions
• Initiated by Telco / SP Sector
• Focused on entire OSI stack: L2-L7
• Commoditize the Telco specific hardware • Make data plane programmable • Industry Standards European Telecommunications Standards Institute (ETSI) http://www.etsi.org/technologies-clusters/technologies/nfv
Reference https://en.wikipedia.org/wiki/Network_function_virtualization
www.sdncentral.com
http://www.etsi.org/technologies-clusters/technologies/nfv
www.openstack.org
www.opendaylight.org
www.opennetworking.org
https://portal.etsi.org/NFV/NFV_White_Paper.pdf
Slide share
http://www.slideshare.net/rjain51/m-17nfv
http://www.slideshare.net/pontschek/sdn-and-nfvfriendsorenemies
http://www.slideshare.net/zahidtg/sdn-nfv-openflow-and-forces
Satish Chavan
http://in.linkedin.com/in/satchavan