Openet: NFV - Moving It To The Field

Size: px
Start display at page:

Download "Openet: NFV - Moving It To The Field"

Transcription

1 Openet: NFV - Moving It To The Field

2 Corporate Overview Delivering Real-time BSS that drives innovation Enable real-time monetization of network activity Virtualization ready technology Deliver functionality for rapidly evolving future business needs Top tier customer base 3 of 4 US Tier 1 Telco s 15 international customers with > 10m subscribers Founded employees 42 deployments in 32 countries Offices in Ireland (HQ), US, Brazil, & Malaysia Who we work with We make data make money Openet s agile-billing business solutions and our real-time decision systems: Enable the commercialization of network activity today Deliver functionality for rapidly evolving, future business models Copyright 2015 Openet w w w. o p e n e t. c o m

3 Openet Products in the Network User interactions with next-gen networks Secure 3 rd party access to network features Operator Network Interaction Gateway Policy Manager Evolved Charging Convergent Mediation Definition of network policies Monitor real-time usage & execute rules Other Network Systems Define charging & data entitlements Create up-sell and dynamic service offers Collection & processing of network usage data Business insight & actionable analytics Copyright 2014 Openet w w w. o p e n e t. c o m

4 Openet Products in the Network delivering a range of solutions SELECTION OF OPENET SOLUTIONS Sponsored Data SIP-based applications Location Server Applications Non-SIP based applications Presence Server Tethering Shared Data IN Replacement Fair Usage Network Selection Intelligence Network Bearer Channel Control Channel Application Servers / Manager Rx Openet Policy Manager (PCRF) Gx Policy Enforcement Function Gy Sp Profile Manager (SPR) Openet Evolved Charging (OCS) Interaction Gateway Gz Openet Convergent Mediation (OFCS) Copyright 2015 Openet w w w. o p e n e t. c o m

5 Openet: Virtualization Background

6 Background In 2012 Openet deployed its first virtualized PCRFs across several large tier one operators 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) The orchestration workflows automated the following operations: Deployment of vpcrf (including operating system, application and database) Configuration of vpcrf In-service upgrade of vpcrf Elastic scaling of vpcrf First telco-grade Virtualized PCRF platform: Hardware (Servers + Network) Hypervisors and their Tuning (e.g. SR-IOV) Virtual Infrastructure Manager Virtual Machines Management Layer and Orchestration

7 Background (continued) In 2014, Configuration and Deployment Manager (CDM) was released as Openet s VNF Manager CDM is similar to configuration management tools such as Puppet and Chef, however it also performs monitoring, recovery, VNF-level orchestration and lifecycle management It has since been deployed in multiple customer sites, in support of Virtualized Policy, Charging, and Mediation solutions, in both North America and Europe

8 Background (continued) Openet s CDM integrated with numerous VIMs and Orchestrators in the past VIMs include OpenStack, VMware, Red Hat Enterprise Virtualization (RHEV), IBM SmartCloud, libvirt and Amazon Elastic Cloud Computing (EC2): RedHat Enterprise Linux Guest OS supports the following hypervisors :- RHEL and KVM, RHEV, RHEL OpenStack Platform and VMWare ESXi/ESX and Microsoft Hyper-V Orchestrators include HP OO, Amartus, OpenStack Tacker, Apache Camel, and more CDM was agnostic in terms of orchestrator and virtualised infrastructure and has been developed so that it can be easily integrated in to any NFV platform Policy Manager Policy Manager VNFs Policy Manager Virtualisation Layer Hardware Resources Policy Manager VNF Manager CDM VIM virt-manager HP Operations Orchestrator Orchestrator

9 Openet: ETSI Proof of Concepts

10 Openet and NFV Real World Monetization of NFV - ETSI PoC #32 with many partners: Virtualisation of OSS and BSS functions such as DPI, Policy and Charging Control and analytics

11 Openet: Moving Forward For 2016

12 Introduction Openet VNF Lifecycle Manager (OVLM) Openet s VNF Manager (OVLM) is Openet s new NFV platform offering While CDM provided VNF-M functionality, OVLM provides a rich set of MANO and EMS features OVLM introduces the innovative new management as a service deployment model which provides a shared management layer for all VNFs This simplifies the NFV architecture for operators and the overhead for vendors to deliver VNFs

13 OVLM VNF-M Consolidation

14 OVLM goals: OVLM automates end-to-end VNF lifecycle operations such deployment, monitoring, in-service upgrades and scaling It provides a flexible architecture that allows for the integration of VNFs from multiple vendors into the OVLM ecosystem of Manager and tools Using OVLM, developers can deliver VNF services faster through the continuous delivery management flows Operators can bring new services and products online faster and in a more robust manner OVLM can manage both simple and complex VNF flows Vendors existing applications can be easily migrated to run in the OVLM ecosystem in an NFV environment Lowers the skill level required to perform deployment, upgrade

15 OVLM VNF-M The VNF-M (Virtual Network Function Manager) is responsible for the VNF lifecycle management - e.g. it takes action on instantiation, termination, failover, scaling in and out, and more The OVLM-VNFM facilitates the management of the full lifecycle of Openet VNFs through a set of REST based APIs Termination Deployment POST Upgrade Configure MANO Orchestrator PUT GET OVLM VNFM with a Workflow Engine Call VNF Flow Patch Health DELETE Scale

16 NFV-0010 NFV Architectural Framework

17 OVLM as an NFV VNF-Manager OVLM is aligned with the functionality of an NFV VNF-Manager: Provides configuration management, monitoring, recovery, VNF orchestration and lifecycle management of diverse multi-vendor VNFs Highly flexible and converged generic VNFM and EMS layer simplify the variation of lifecycle management requirements for diverse VNFs Uses metadata descriptors to manipulate the specific VNFM lifecycle operations and EMS functions OVLM Workflow Studio provides a tool for designing workflows for VNF Lifecycle events

18 Workflow Automation A workflow is a logically linked sequence of steps - each step is a either an EMS API call or a VIM API call which represents an action which has both an input and an output (success/failure) After each step, the flow will proceed to next step if that step is successful or an action can be made to pause, rollback or retry on failure VNF lifecycle workflows are reliable with OVLM since every step in the upgrade is an API call within a fully automated, repeatable and well tested workflow Health Check Auto Stage Auto Update Auto Health Check Auto

19 Workflow Example Each step in a VNF Lifecycle flow either calls a EMS APIs to manage the VNF components or a VIM API to manage the infrastructure components Manage VNF components Terminate Workfow Upgrade Workflow Deploy Workflow Workflow Repo MANO Orchestrator OVLM OVLM Workflow Engine Call VNF lifecycle flow Manage Infrastructure Components Fault Manager Config Manager Security Manager Resource Manager Perf Manager Nova Cinder Neutron Glance EMS VIM

20 VNF-M Workflows The OVLM VNFM exposes APIs to the MANO Orchestrator for performing VNF lifecycle operations Each API triggers an internal workflow to perform a distributed VNF operation The OVLM platform provides workflows for each VNF lifecycle operation: VNF Development Validation VNF Promotion VNF Selection VNF Deployment VNF Management Upgrade, Configure, Start/Stop, Scale, Monitor VNF Termination

21 VNF-M Workflows (continued) These workflows can be triggered through the Workflow Dashboard (below left) or via the VNFM REST API The workflows can be viewed or modified for a specific vendor s VNF using the Workflow Editor (below right) OVLM-VNFM allows lifecycle operations to be in four modes (Visually guided mode, Fully automated mode, Scheduled mode and CLI / API)

22 User Friendly VNF Operations OVLM s Workflow Engine reduces the level of expertise and effort to deploy, configure, upgrade and scale VNFs The point and click Workflow Studio makes it easy to run, modify and debug distributed VNF lifecycle operation flows The progress of your flow can be easily followed on the dashboard and the results of each step are clearly marked green or red depending on API return codes Uses can drill down into each step of their flow from a central GUI to see the input/output of that step History and audit log of all executed workflows are also maintained

23 Health Check Workflow The health check is the most important step in any workflow It validates that any action you have made during a workflow has not impacted the systems health Without this step, the VNFM and orchestrator are managing the system blind Process Running Service Running VNF Health Service Performance Service Healthy

24 Reliable and Resilient Upgrades The health check is performed on many different levels: Service Running Process(es) running: Are the VNF processes up and running? Service running: Are the VNF services up and available? Service performance: Process Running VNF Health Service Performance Are the VNF services performing as expected? Service Healthy: Have any alarms or traps been raised? Service Healthy

25 MANO Orchestrator and OVLM The MANO Orchestrator calls OVLM REST APIs An equivalent Web UI is also available

26 Key architectural advantages of OVLM OVLM lifecycle management is VNF software lifecycle driven - NOT solely VM driven: E.g. rather than just spawning a new VM instance for in-service upgrade, OVLM s integrated VNFM and EMS can upgrade software/configurations in the VM This fine grain control and visibility over the VNFs reduces operational time and complexity Upgrade, Patch, Configure, Test, Rollback etc. Custom procedures enable any number of additional operations to be added Each change is tracked and version controlled

27 OVLM in Summary Flexible VNF-M that can manage third party VNFs Supports management of complex VNFs Supports complex VNF lifecycle operations Easy to use UI to track VNF workflow progress Allows incremental updates to VNFs VNF Access Level Controls VNF Validation and Health Checks

28 New NFV Partnerships - Brocade and Openet Combining the expertise of Brocade in delivering Virtual Network Functions and Openet s expertise in policy management and lifecycle management for virtualized network functions

29 @alanmcnamee THANK YOU