openet: nfv - moving it to the...
TRANSCRIPT
Openet: NFV - Moving It To The Field
‘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
• Founded 1999
• 850+ employees
• 42 deployments in 32 countries
• Offices in Ireland (HQ), US, Brazil, & Malaysia
• 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
Corporate Overview
w w w . o p e n e t . c o m© Copyright 2015 Openet
Who we work with
Openet Products in the Network
w w w . o p e n e t . c o m© Copyright 2014 Openet
PolicyManager
EvolvedCharging
ConvergentMediation
OtherNetworkSystems
• Define charging & data entitlements
• Create up-sell and dynamic service offers
• Definition of network policies
• Monitor real-time usage & execute rules
• Collection & processing of network usage data
• Business insight & actionable analytics
Operator Network
Interaction Gateway
• User interactions with next-gen networks
• Secure 3rd party access to network features
SELECTION OF OPENET SOLUTIONS
• Sponsored Data
• Tethering
• Shared Data
• IN Replacement
• Fair Usage
• Network Selection Intelligence
Openet Products in the Network delivering a range of solutions
w w w . o p e n e t . c o m© Copyright 2015 Openet
Gz
Gy
Applications
Presence ServerLocation Server
Control Channel
Sp
Gx
Rx
ApplicationServers / Manager
Profile Manager(SPR)
InteractionGateway
Bearer Channel
Openet Policy Manager
(PCRF)
OpenetConvergent Mediation
(OFCS)
Policy Enforcement Function
Network
SIP-based applications
Non-SIP based applications
OpenetEvolvedCharging
(OCS)
Openet: Virtualization Background
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 automatedthe 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
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
• 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
Background (continued)
Virtualisation Layer
Hardware Resources
VNFs
Orchestrator
VIM
VNF Manager
CDM
virt-manager
HP Operations Orchestrator
Policy Manager
Policy Manager
Policy Manager
Policy Manager
Openet: ETSI Proof of Concepts
• 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
Openet and NFV
Openet: Moving Forward For 2016
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
OVLM VNF-M Consolidation
• 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 or scale outs
OVLM goals:
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
Deployment
Configure
Health
Scale
Patch
Upgrade
Termination
MANO
Orchestrator
OVLM VNFM
with a
Workflow Engine
POST
PUT
GET
DELETE
Call VNF Flow
NFV-0010 NFV Architectural Framework
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
OVLM as an NFV VNF-Manager
• 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
Stage Auto Update AutoHealth CheckAuto Auto
Workflow Automation
OVLM
OVLM
Workflow Engine
Terminate
WorkfowUpgrade
WorkflowDeploy
Workflow
Workflow Repo
EMS VIM
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
Config
Manager
Security
Manager
Resource
ManagerFault
Manager
Manage VNF components
Call VNF lifecycle flow
Manage Infrastructure Components
Cinder Neutron GlanceNova
Workflow Example
Perf
Manager
MANO Orchestrator
• 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
VNF-M Workflows
• 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)
VNF-M Workflows (continued)
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
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
VNF Health
Service Running
Service Performance
Service Healthy
Process Running
Reliable and Resilient Upgrades
• The health check is performed on many different levels:
• Process(es) running:
• Are the VNF processes up and running?
• Service running:
• Are the VNF services up and available?
• Service performance:
• Are the VNF services performing as expected?
• Service Healthy:
• Have any alarms or traps been raised?
VNF Health
Service Running
Service Performance
Service Healthy
Process Running
MANO Orchestrator and OVLM
• The MANO Orchestrator calls OVLM REST APIs
• An equivalent Web UI is also available
• 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
Key architectural advantages of OVLM
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
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
