NFV Director overview June 2014 Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
NFV the new business of the network Why now? Change is not optional Improves OPEX Move from Telco opex model, to lower cost IT opex model Lowers CAPEX Move from dedicated appliances to virtualization model based on IT technology Accelerates time to market Deploy new software and new services quickly and easily (from months to minutes) Accelerates innovation via an open platform Broaden access to partners who can innovate not just NEPs but also start ups, ISV s Delivers business agility Rapidly scale up or scale down applications modify QoS, deliver new services faster 2
What is Network Functions Virtualization (NFV)? Ability to provide network functions on industry standard platforms Evolution of IT virtualization techniques for core network functions Use standard servers and storage Reduced equipment costs Faster time to market Resource sharing Targeted service introduction Classic network appliance approach Message router WAN acceleration CDN DPI Session border controller Firewall Network virtualization approach Software vendors Virtual appliances Orchestrated, automatic, and remote install Implement network functions in SW It can be moved to, or instantiated in, various locations in the network as required, without the need to install new equipment! 3 Carriergrade NAT PE router Tester/QoE monitor BRAS SGSN/ GGSN Radio access network nodes Fragmented non-commodity hardware Physical install per appliance per site Hardware development large barrier to entry for new vendors, constraining innovation and competition Standard high-volume servers Standard high-volume storage Standard high-volume Ethernet switches
NFV Challenges for the CSP NFV adoption is not an option, yet it is deeply transformational and introduces risks Infrastructural Cost of transformation Need Telco-grade availability, performance and SLAs Future proof architecture to cope with NFV uncertainty Operational Integration within existing OSS/BSS environment How to maintain customer and services view correlated to underlying infrastructure Need automation to enable NFV agility How to ensure reduced operations costs while deploying NFV Organizational CIO vs. CTO scope of responsibility Automation will create redundancies and have social impact Purchase chain and interfacing will drastically change 4
NFV Operational Challenges for the CSP CSPs demand vendors to focus also on operational challenges Seamless integration with existing OSS/BSS systems, processes and practices Correlation across Network Service, VNF, infrastructure and network to provide end to end view of services to guarantee customer experience Management automation to enable NFV agility Affordable and flexible solution with multi-vendor capabilities that removes vendor dependency while maintaining telco-grade availability NFV transformation requires orchestration capability 5
Addressing the challenges through orchestration Key component of NFV management is Orchestration NFV Orchestration role Maintain end to end view of Infrastructure, VNFs and Network services to provide proper visibility of customer experience Automate deployment and monitoring across multiple VNF and VIMs Ensure integration with OSS to guarantee NFV manageability Business case 1 Operating cost Physical Virtual NFV with orchestration Business case 2 Installation costs NFV Orchestration benefit Avoid creating new technical or organizational silos of management for NFV Easily integrate virtualized network functions into OSS and IT environment Reduce risk by implementing a standard based approach Avoid vendor lock-in at infrastructure or VNF level Enabling Successful Business Cases Y-1 Y-2 Y-3 Y-4 Net margin Y-1 Y-2 Y-3 Y-4 Y-5 Net margin Y-1 Y-2 Y-3 Y-4 Y-1 Y-2 Y-3 Y-4 Y-5 6
NFV Director overview
NFV Director is part of the HP OpenNFV Program Mapping to the ETSI functional architecture HP NFV Director Operationalizing NFV through an NFV orchestrator with embedded VNF manager capabilities HP Helion OpenStack Fully supported and tuned OpenStack distribution HP NFVI management Domain management handling all aspects of the NFVI HP OSS solutions Combining HP s OSS and IT management capabilities to deliver an OSS adapted to NFV HP converged infrastructure The leading provider of COTS based NFV Infrastructure HP VNF ecosystem HP VNF coupled with a foundation to support the vast 3rd party NEP and ISV applications HP OSS Solutions HP VNF ecosystem Fulfillment EMS EMS EMS VNF Compute & storage OSS Assurance EMS EMS EMS VNF Logical environment Lifecycle & Change Management Network EMS EMS EMS VNF HP converged infrastructure HP NFV Director NFV Orchestrator VNF Manager Virtual Infrastructure Manager NFV Management and Orchestration Physical Infrastructure Management HP NFVI management HP Helion OpenStack 8
HP NFV Director a complete NFV orchestrator Fulfillment Model-based for agility and extensibility Maintains catalog and inventory Manages configuration of infrastructure and assurance components Assurance Monitors infrastructure and VNF KPIs Provides end-to-end visibility Integrated together Automated reactions to KPI changes Fulfillment NFV Director Assurance A common point to ensure consistent management and behavior of VNFs and NSs Designed to meet the evolving ETSI specifications Supporting the journey to NFV Open and multivendor Modular and extensible 9
NFV Director more than an NFVO Fills the gaps Agile and extensible Fills gaps that may be present in full NFV deployment Adapters can augment functionality lacking in some Virtual Infrastructure Managers and VNF Managers Support deploying VNF without complete VIM in singleserver POPs deployed in CPE and edge Provide WAN infrastructure and device management when no controller present Dynamically extensible definitions All models, processes, and visual representation can be dynamically changed Allows support for broader concepts than just those specified by ETSI (e.g., composite VNF) Fill Mind the gap 10
HP NFV Director layered view OSS MANO NFV Director NS Orchestrator (fulfillment & assurance) VNF VNF Manager (external) VNF adapter VNF Manager (embedded) Global Resource Orchestrator WAN NFVI (N-POP, DC, ) WIM VIM VIM adapter WIM adapter WIM 11
HP NFV Director network-focused features Supporting the network needs of NFV Supports the end-to-end network Manage multi-domain, multi-technology and multi-vendor network infrastructure Manage SDN, traditional (non-sdn), and hybrid networks Supports Physical Network Functions (PNF) and network devices as well as VNF Model-driven approach Models can be extended to address ne domains or technologies Full tear-down on VNF scale-in or decommissioning Desired State Engine dynamically determines steps to go from current state to desired state Uses proven Telco-grade activation engine Transactional capabilities Automated error handling Fault tolerant configuration Customer site vcpe WAN domain Data center domain App Radio/Access Network Data center domain App Servers and Storage AppApp Servers and Storage 12
Embedding NFV as a new OSS leg 13 OSS Engineer Internal order for Network Service from LCM (e.g. EPC, CDN etc.) Planning Legacy network management Telecommunications infrastructure BSS E2E service management Legacy request (VPN, CDN, CPE) Customer order for Network Service from BSS (e.g. Fixed Access, CPE, VPN etc.) Legacy Request (as part of a NS, which requires a PNF configuration) Customer NVF Request (VPN, CDN, CPE) Customer order for User Service NFV network management Production network VNF DC from BSS (e.g. VoIP, IPTV etc.) VNF DC User Service actiation (VoIP. IPTV) Operator E2E service management Responsible for the end-to-end operations and presentation of all Services. Assembles RFS supplied by Legacy or NFV-based Networks and Functions. Activates user services directly (full automation) Legacy network management Produces Networks using legacy network functions (PNF) in telecoms specific infrastructure. It may need engineering and workforce. NFV network management Produces Networks using NFV Technology, but may connect to legacy endpoints. Full automation
NFV Director v1: what is included NFV configuration Support deployment of VNF, NS and VNFFG including PNF interaction VNF and NS Descriptor using internal Open-XML based format Support versioning of NS and VNF NFV monitoring Automatic monitoring of NS, VNFs and NFV compute infrastructure with correlation across end to end NFV topology Automation rules for actions such as scale-in/out/up/down VIM related features Support of OpenStack Havana, others on demand No limitation in term of number and size of datacenters Affinity rules through the use of resource pools Ability to orchestrate WAN and servers not under VIM control (e.g., vcpe) VNF Manager VNF Descriptor using open XML-based format allowing automatic deployment and monitoring of VNF Provide VNF Manager functionality or work with external VNFM Embedded VNFM can be configured to automate actions Support of direct (VNFM-VIM) and indirect (NFVO as VIM proxy) interaction model with external VNF managers General Simple Pay As You Grow model with very low entry price for PoC Carrier-grade Scalability HA and geo-redundant configurations possible Northbound APIs allow Integration with existing OSS 14
Example use cases
EPC use case PoC with equipment provider enodeb Serving Gateway Monitor performance HP NFV Director Load Balancing MME VM MME VM MME VM Create/delete Net Threshold HP Virtualized Infrastructure Manager (MOE or CloudSystem 8) Create/delete VM HP Blades and Network (with SR-IOV and Intel DPDK) 16
Enterprise vcpe PoC @ Customer Virtual CPE Applications vcpe VNFDs Firewall WAN acceleration Router DHCP IPv4/IPv6 VPN Deploy, Configure, & Monitor HP NFV Director VCenter RiverbedCMC Checkpoint SmartCenter Cold Boot Control Deploy, Configure, & Manage Access Network (options) Customer s internal Network vapp images COTS Server Customer Site WAN Access Access Network Configure and Manage Backend Office/DC Customer Site 17
HP IMS MSE The Multimedia Services Environment consisting of four VNF components: Element Manager SIP Load Balancer (MRB) MSE SEE Application server includes WEB LB SEE AS instances SEE Reporting instances The IMS MRF VNF that groups MRF-C MRF-P MRF storage functions NFV Director orchestrates Instantiate the IMS VNF (all components) Scales out and in of the IMS VNF MSE SEE SIP AS AS WEB Load Balancer WEB AS AS Reporting & Monitoring MSE SIP Load Balancer (MRB) MRF MRF-C NFV Director MRF Storage MRF-P Element Manager Fulfillment Assurance 18
HP vcdn NFV Director CDN is composed of several components Control Plane Fulfillment Assurance TLDDNS, CDN Logger, CDN Manager, Control Service Nodes Topology, Origin, Tracker, Publisher Delivery Regions Endpoints HP NFV Director provides ISP DNS TLDDNS CDN Logger Control plane CDN Manager Topology Origin Control service nodes Publisher Tracker NFV orchestrator and VNF manager Fulfillment and assurance planes Internet Delivery region Endpoint Endpoints can scale out and in to accommodate increases and decreases in load. 19
Virtualization of mobile core network / vhss HP Virtual HSS (vhss) Instantiation within minutes Scale up/down as needed License by actual usage Leverage commodity infrastructure NFV /VNF compliant VNF Descriptors NFV Director Subscriber DB Home Subscriber Server (HSS) Hypervisor Perfect fit for MVNO and M2M providers Separate subscriber data per service group Scale up/down to adjust with traffic volatility Active / Active Real-time Synchronization S6a Cx Serving CSCF MME Interrogating CSCF IMS Networks Proxy CSCF S-GW P-GW E-UTRAN EPC Networks 20
Summary
HP NFV Director An NFV Orchestrator that can automate the deployment and monitoring of your VNF ecosystem NFV Director Fulfillment Assurance Business/technical differentiators Aligned with ETSI NFV to avoid NFV vendor lock-in and new silos Multivendor, Open Carrier grade & scalable HP achievements to date Most complete NFV Orchestration solution. Nominated for TMF Solution Excellence award Product development and experience used to submit >40 ETSI NFV ISG MANO contributions Multi VIM support (Openstack, VMware, KVM) Multi VNF vendor integration available Open interfaces, implementing standards where they defined Based on technology supporting >400 CSPs WW 22
Key benefits Safely transition your network from physical to virtualized mode Fully realize the benefit of the NFV promise by properly operationalizing the deployment Easily integrate virtualized network function into your OSS and IT environment Seamlessly row from simple virtualization use cases to very complex use cases Avoid creating new technical or organizational silos of management for NFV Fully benefit from a standards based and multi-vendor approach Faster innovation and increased revenue through easier and quicker deployment of network functions 23
Why HP for NFV management and orchestration? HP is the partner of choice to help operationalize NFV OSS transformation NFV Orchestration Manageable NFV deployment IT & cloud management HP is a leader in both OSS and IT management Leading OSS solutions covering both fulfillment and assurance using TMF Frameworx Leading IT management solutions covering full ITIL processes Experience integrating OSS and ITSM, bringing together etom and ITIL HP is committed to open, multi-vendor solutions HP OSS and ITSM have proven multi-vendor approaches HP solution is modular, allowing you to start small and grow as you need HP can provide a complete NFV management solution NFV management and orchestration IT and cloud management tools and processes integrated into OSS Analysis of existing OSS and recommendations on transformation to NFV-capable OSS 24
Thank you
Glossary For formal definitions, see ETSI documents Definition Comments NFV Network function virtualization; the approach to building telecom services using virtualization approaches This is the general term VNF Virtual network function; the application that provides the functionality currently provided by devices This is used when referring to specific NF (applications) VNFC VNF component; each VNF is composed of one or more components, often mapping to a VM The number and types of VNFC is implementationdependent (defined by the VNF vendor) MANO Management and orchestration; addressing the functionality required to deal with the new abstractions Consists of NFVO, VNFM, and VIM NFVO NFV orchestrator; in charge of the orchestration and management of NFV infrastructure and software resources, and realizing network services on NFVI Deals with things that span VNF or VIM (NS, global policies, global resource management) VNFM VNF manager; responsible for VNF lifecycle management (e.g. instantiation, update, query, scaling, termination) Can be implemented as part of the NFVO or supplied by the VNF provider VIM Virtualized infrastructure manager Think OpenStack or Cloud OS NFVI NFV Infrastructure; the totality of all hardware and software components which build up the environment in which VNFs are deployed, managed and executed Both the physical hardware and the virtualization layer (e.g., hypervisor) EMS Element management system; performs the typical management functionality for one or several VNFs. Handles the type of management functionality required by devices NS Network service; A composition of network functions (VNF or PNF) and defined by its functional and behavioral specification At least one network function needs to be a VNF PNF Physical network function Today s devices 26