1. Open Network Automation Program(ONAP) Merging OPEN-O and ECOMP efforts
(OPNFV MANO WG)
Prakash Ramchandran

2. Open Network Alliance/Automation Program (ONAP)
Govern
Board
Oversight
Business
Steer
TSC.
Technical
Platinum Service Provider
Members (limited
to service providers);
    
 Platinum Members; and
     Silver Members.

3. ONAP Emerging from LF https://www.onap.org/
Governing Board(GB)
business oversight
create a model and meta- data driven reference open platform for service providers
to support full lifecycle management of cloud- centric, software-controlled networks (SDN / NFV).
ONAP Project Charter
Technical Steering Committee (TSC)
technical oversight
Project platform to include:
to support design-time capabilities
define infrastructures and services
define analytics and policies for run time

4. View of ONAP (Harmonize Framework) to rapidly create new services
PROJECT
PROJECT
Framework
Real Time, Policy Driven, Software Automation of VNFs to enable Developers

5. ECOMP

6. Comparing ECOMP & OPEN-O
Topic or Module
ECOMP
OEPN-O
Automation Targets
70% by 2017 (35% now in AT&T )+ Orange+ Bell Canada
No figures available from China Mobile for this.
Design Framework
Metadata for Service
Blue Prints, TOSCA, YANG
Constraints
Recipes
Policy Framework: Congress
Metadata in Info/Data models TOSCA/YANG
TOSCA , SDK. ARIA parser
Common TOOSCA Services
TOSCA based
Models : Virtual/Physical
Models: Virtual/Physical
Use Cases
vIMS, vEPC
vIMS, vCPE
MANO Execution Framework
ECOMP Execution Framework (MSO+VNFM)
OpenStack IaaS + Domain 2.o SDN Hierarchy(ODL+ONOS)
Service Layer (GSO)
Control Layer (SDNO/NFVO Controllers)
Infrastructure layer (OpenStack + VMware)
Telemetry/Analytics
Control loop
Data Center Alerts & Events
(DCAE)
Analytics
Common TOSCA services to include the resources change notification / Analytics in sub module

7. Governance Model
Governance documents applicable to the project include:
The Linux Foundation’s Anti-Trust Policy
The Bylaws of The Linux Foundation
The Linux Foundation’s Privacy Policy
The Linux Foundation Trademark Policy (until such time as the ONAP community develops its own policy)
ONAP Project Corporate Contribution License Agreement

8. Use case: Virtual IMS Core
Amdocs partnered with Metaswitch to provide a virtual IMS core network, ready to provide any IMS service within minutes
The rapid implementation was enabled by virtualized cloud based components which are scalable, self-maintained, self -operated and constantly monitored
The sizing of the IMS core network is automatically calculated according to the specific order parameters
The service has auto-healing capabilities which allows minimal recovery time and smooth operation
IMS core service can be instantiated either by a network administrator or can be triggered by a new enterprise service order which requires IMS core as a prerequisite
Service providers can deploy limited scale systems, as needed, and grow it as IP multimedia services become more prevalent. Introducing a variety of IMS core services according to customers’ needs now is quicker and easier.

9. Virtual Evolved Packet Core (EPC)
Amdocs partnered with Connectem to establish a virtualized evolved packet core (vEPC).
The joint use case demonstrates full evolved packet core network functionality. The Connectem vEPC is instantiated, managed and operated by Amdocs service orchestrator including on-going monitoring, dynamic scaling and auto-healing.
Virtual Evolved Packet Core
DPE – Data Plane EPC element /CPE – Control Plane EPC element / SDB – Subscriber DB
RIF – Routing Info Forwarder
VEM – Virtual Element Manager
AMDOC Network Cloud Orchestrator
CMS – Cloud Management System OpenStack
Connectem (vEPC) Virtual Core for Mobile (VCM)– bought by Brocade and in-turn Bought by Broadcom
Service providers can use this solution to offload traffic (M2M, connected car) from their legacy vEPC system, as well as to expand the vEPC capacity to meet increasing demand from new services such as VoLTE.

10. OPEN-O
OPEN-O is an open source project backed by the Linux Foundation that enables telecommunications and cable operators to effectively deliver end-to- end services across Network Functions Virtualization (NFV) Infrastructure, as well as Software Defined Network (SDN) and legacy network services.

11. OPEN-O Architecture

12. Comparisons of MANO Stacks
link on MNAO page for tech comparisons.

13. Questions & Answers?
10/8/2017
OPNFV Documentation

14. Appendix : CTOs push for Cloud Automation
AT&T John Donovan CTO (2017)
Automation from 5% to 35% in two years
Plan to get Cloud Automation to 90% in 2017
Endorsements for implementations of ECOMP with Bell Canada & and Orange
Teams are working with Linux Foundation to get ECOMP work with OPEN-O(AMDOCS a key player)
By deploying ECOMP, service providers can move from today's appliance-based, proprietary networks to easily configurable and scalable software-based networks and associated services. These software-driven networks will allow carriers to be much quicker with new service introduction and provide an improved connectivity and service experience to their customers," said Gary Miles, chief marketing officer at Amdocs. "Having co-developed important modules to be contributed to OpenECOMP, we are in a position to help customers achieve an early advantage in leveraging OpenECOMP for service innovation. (planning to possibly launch OpenECOMP with LF to be announced at LF event or Barcelona – Feb 27, March 2)