Intel's Out of the Box Network Developers Ireland Meetup on March 29 2017 - Openet Presentation
- 1. 1© Copyright 2017 Openet Classification: Confidential Openet - Enabling Virtualization in SDN and NFV World Aidan Molloy : Snr. Director NFV Strategy
- 2. 2© Copyright 2017 Openet Classification: Confidential • Who are Openet? • Current Telco Challenges • What is NFV? • What is MANO? • How Vendors onboard their software into an NFV architecture? Agenda
- 3. 3© Copyright 2017 Openet Classification: Confidential ® Who are Openet?
- 4. 4© Copyright 2017 Openet Classification: Confidential Corporate Overview • Founded 1999 • 850 Employees • 80 customer deployments in 32 countries • Offices in Ireland (HQ), US, Brazil, & Malaysia ‘we make data make money’ Our real time telecom business support systems enable the commercialization of operator's network activity • Leading global provider of virtualized, highly scalable, ultrahigh performance, real-time mediation, charging and policy systems • Deployed globally in mission critical applications including 3 of 4 US Tier 1 Telcos covering 85% of all NAR subscribers • Differentiated through performance, in-service experience and support • Incumbent position in rapidly emerging NFV and VoLTE roll-outs • 58 Patents & Applications
- 5. 5© Copyright 2017 Openet Classification: Confidential ® • In 2012 Openet deployed the world’s first virtualized vPCRF across a large tier one operator • This included large scale deployments e.g. of 13 datacenters and over 600 hypervisors • This was pre-NFV but the solution consisted of a number of similar components: • Orchestration workflows • Configuration Master • Virtual infrastructure manager (RHEV-Manager) NFV and Virtualisation Background
- 6. 6© Copyright 2017 Openet Classification: Confidential Openet NFV : Areas of Focus in MANO
- 7. 7© Copyright 2017 Openet Classification: Confidential Enabling intelligent, intent-driven, business aware management of dynamic, automated and software-centric networks. Accelerate NFV business case realisation Control Deploy Secure Monetize Network Automation Insight Assure Intent
- 8. 8© Copyright 2017 Openet Classification: Confidential ® Current Telco Challenges
- 9. 9© Copyright 2017 Openet Classification: Confidential • Traditional voice, SMS and new IP services are steadily being gobbled up by OTTs • Deliver ‘apps’ that people want, at incredible speeds and at low cost. • DevOps mentality encourages rapid innovation and deployment of new services. • If services fail, they learn and quickly move to next big thing. Current Telco Challenges 1 billion monthly active users 1.2 Billion subscribers 75 million subscribers Google Fibre 200 million active users 1.5 billion monthly active users
- 10. 10© Copyright 2017 Openet Classification: Confidential They must behave like Google • To date Operator’s network flexibility has been limited to automating specific tasks. • Tasks which were never tightly coupled to overall business process or strategy. Launch & iterate, fail fast and fail often
- 11. 11© Copyright 2017 Openet Classification: Confidential Digital human Smart Everything Networked Society Internet for everyone Global Wifi Machine to Machine Telco needs to prepare for the future
- 12. 12© Copyright 2017 Openet Classification: Confidential ® What is NFV?
- 13. 13© Copyright 2017 Openet Classification: Confidential What is NFV?
- 14. 14© Copyright 2017 Openet Classification: Confidential NFV Reference Architecture • VNF: Virtual Network Function – S/W implementation of network function like P-GW, DPI or PCRF • VNFM: VNF Manager manages life cycle of VNF ( creates, maintains and terminates VNF instances). • EMS: Element Manager Fault, Configuration, Accounting, Performance and Security Management (FCAPS ) • NFVI: H/W and S/W environment in which VNFs deploy • VIM: Virtualised Infrastructure Manager controls NFV resource (e.g. Openstack, VMWare) • Orchestrator: Service level lifecycle management. Orchestration of physical and/or software resources that support the infrastructure virtualization, and the lifecycle management of VNFs.
- 15. 15© Copyright 2017 Openet Classification: Confidential ® What is MANO?
- 16. 16© Copyright 2017 Openet Classification: Confidential MANO and Openet • MANO stands for Management and Orchestration. • Virtualized Infrastructure Manager (VIM). • Manages NFV resources that includes physical (server, storage etc.), virtual resources (Virtual Machines) and software resources (hypervisor) in an NFV environment. • VNF Manager (VNFM). • This is the VNF Manager, which manages life cycle of VNFs. That is it creates, maintains and terminates VNF instances. • NFV Orchestrator (VNFO). • Automated arrangement, coordination, and management of complex computer systems
- 17. 17© Copyright 2017 Openet Classification: Confidential ETSI Plugtest
- 18. 18© Copyright 2017 Openet Classification: Confidential ® Vendor Onboarding into MANO
- 19. 19© Copyright 2017 Openet Classification: Confidential • Topology and Orchestration Specification for Cloud Applications (TOSCA), is an OASIS standard language to describe a topology of cloud applications • Capture everything needed to run the application • Benefits include: • Interoperability • Portability • Multi VIM • Topology, workflows, policies What is TOSCA?
- 20. 20© Copyright 2017 Openet Classification: Confidential • Topology • Defines nodes, relationships, capabilities • Workflows • Lifecycle Operations – install, scale etc • Policies • can express such diverse things like monitoring behavior, payment conditions, scalability, or continuous availability, for example. Topology, workflows, policies
- 21. 21© Copyright 2017 Openet Classification: Confidential • They have a similar structure • Description • Input Parameters • Output Parameters • They have some differences • Support for Workflows • The WF is hardcoded into heat engine • TOSCA has no hard coded processes TOSCA vs HOT
- 22. 22© Copyright 2017 Openet Classification: Confidential Descriptors
- 23. 23© Copyright 2017 Openet Classification: Confidential NS Template Network Service Template NSD Network Function Template VNFM Flows VNF Template VNF Component Template Weaver Template VDU VDU NS Orchestration Flows VNFD NFV Templates VNF software packages and configuration
- 24. 24© Copyright 2017 Openet Classification: Confidential Instantiation NS Flow Service Catalog OSS NFVO VIM Openstack Weaver VNFM Weaver EMS Instantiate NS Instantiate VNF Ack resource allocation Instantiation Response Create service network connectivity Create network connectivity response Connect VNFs to connectivity network For each VNF Allocate resources Resource (compute, storage network) allocation and interconnection setup Allocate internal connectivity network Allocate VMs & attach network Ack completion of resource allocation Connect response VNF software instantiated Instantiate VNF software VMFM–EMS Flow
- 25. 25© Copyright 2017 Openet Classification: Confidential SR-IOV • Single Root I/O Virtualisation provides :- • Direct I/O throughput • Reduced CPU utilization • Increased scalability • Improved device performance for virtual guests
- 26. 26© Copyright 2017 Openet Classification: Confidential SR-IOV • In traditional I/O architectures, a single core has to • handle all the Ethernet interrupts for all the incoming packets • and deliver them to the different virtual machines running on the server. • Two core interrupts are required • one to service the interrupt on the NIC (incoming packet) and determine which VM the packet belongs to • the second on the core assigned to the VM, to copy the packet to the VM where the packet is destined. • SR-IOV introduces the idea of a Virtual Function (VF). • Virtual Functions are ‘lightweight’ PCI function entities that contain the resources necessary for data movement. • The hypervisor is not involved in the packet processing to move the packet (between the hardware interface and the actual VM) thus removing any bottlenecks in the path.
- 27. 27© Copyright 2017 Openet Classification: Confidential DPDK • Intel® Data Plane Development Kit (Intel® DPDK), a set of software libraries that can improve packet processing performance by up to ten times. • It moves control of Ethernet hardware directly into userspace processes to avoid the overhead of communicating with the operating system kernel. • This gives userspace all of the raw performance traditionally enjoyed by the kernel – and all of the responsibility too. • This is important for specialized low latency applications such as virtual network functions.
- 28. 28© Copyright 2017 Openet Classification: Confidential ® Thank You – visit accelerate.openet.com
Editor's Notes
- #18: MANO Cisco - NFVO MANO Ericsson - Cloud Manager MANO OSM - OSM Rel ONE MANO Rift.io - Rift.ware MANO Openet - Weaver MANO HP Enterprise - NFV Director OPNFV - Ericsson - NFVI+VIM Windriver - Titanium OPNFV - Intel - NFVI+VIM OPNFV - Ericsson - NFVI+VIM ADVA - NFVI+VIM Canonical - Lenovo - NFVI+VIM RedHat - Lenovo - NFVI+VIM
- #23: A VLD shall enable specifying requirements on performance characteristics on the link A Network Service Deployment Flavour description shall describe how many instances of each constituent VNF are required. Lifecycle event is the API exposed to the OSS
- #28: The page size in x86 systems is typically 4 KB which is considered an optimal page size for general purpose computing. While 4 KB is the typical page size other, larger page sizes are also available. Larger page sizes mean that there are fewer pages overall, and therefore increases the amount of system memory that can have its virtual to physical address translation stored in the TLB and as a result lowers the potential for TLB misses, which increases performance. Conversely with larger page sizes there is also an increased potential for memory to be wasted as processes must allocate memory in pages but not all of the memory on the page may actually be required. As a result choosing a page size is a trade off between providing faster access times by using larger pages and ensuring maximum memory utilization by using smaller pages. There are other potential issues to consider as well. At a basic level processes that use large amounts of memory and-/or are otherwise memory intensive may benefit from larger page sizes, often referred to as large pages or huge pages.