s Extending DCAE Orchestration into OOM Combined Orchestration

s Extending DCAE Orchestration into OOM (Combined Orchestration support of Tosca & Helm) Vijay Venkatesh Kumar, Kailash Deshmukh AT&T

Controller Alignment Proposal for ONAP DCAE Architecture in ONAP comprise of platform and service components collectively fulfilling the role of data collection from network elements, performing intelligent analytics and triggering root cause CL Events for ONAP. The DCAE platform supports functions to deploy, host and perform LCM of DCAE service components in a distributed environment. Migration of DCAE Platform components into OOM will ensure orchestration alignment across all management application in ONAP. This enables support for both Tosca and Helm work flows under OOM. The solution proposed is completely backward compatible with existing ONAP OOM and ONAP DCAE deployments. 2

DCAE Platform (Controller) Overview Ø Stateful entities supporting LCM of management of DCAE applications. Primary orchestrator is Cloudify, combined with other platform modules enables flexible, pluggable, micro-service oriented, model based component deployment and LCM support. Ø Support dynamic (standalone or composite) applications deployment to support open and closed loops flows in ONAP. Ø Platform design standardizes several Service Component functions § Control Loop Driven deployment and configuration Interfaces (CLAMP/SDC/Policy) § Dynamic topics/feed provisioning and role assignment for MS* § Configuration model standardization and common API for sourcing configuration § AAF Integrations § Support docker or K 8 S deployment (transparent to application) by providing a configuration management layer Ø Support infrastructure setup/deployment for management application if required 3

OOM – Key Functional Gaps (Dublin) ØNo design flow integration (SDC) and standardized configuration modelling enforced (under Helm templates) ØControl Loop flow deployment and support through CLAMP/Policy Integration ØDynamic configuration management through central ONAP Policy ØNo support on Tosca based ONAP management application and workflow ØLack of consolidated view of deployed MS and their relationship Note: Refer backup slide for complete list 4

OOM Extension through DCAE-Platform – Realization Proposal 1. Use Cloudify instead of Rancher for K 8 S setup 2. Move DCAE Platform components under OOM umbrella Policy Handler, Service. Change-Handler, Inventory. API, Deployment-handler, Config. Binding. Service, Dashboards Phased Enhancements based on ONAP priority Ø Event driven reconfiguration capabilities to added among ONAP Controller (OTI) Ø Onboarding Helm based application through SDC Ø Policy based configuration for application deployed through Helm Ø Orchestrator sync-up (Kubernetes and Cloudify) Ø Add new pluggable modules to support cloud native integration 5

OOM Extension - Implementation (proposal) Central Cloud Workflow 1 Dev. Ops/User installs ONAP CENTRAL OOM-orch (Cloudify) OOM-active in the OOM Tenant space, on a VM OOM-active installs K 8 S 2 cluster (using K 8 S cluster API) & Helm OOM-active deploys base 3 ONAP Controller components using either Helm/TOSCA in K 8 S cluster Cons ul ONAP controller components using Helm/Tosca in K 8 S 5 OOM-active deploys ONAP Central mgmt. app using Helm/Tosca in K 8 S cluster Deploy dynamic mgmt. app 6 using Helm/Tosca in K 8 S cluster Edge/Regional (ER) Cloud Workflow K 8 S ETCD Plugin K 8 S CRD plugin Istio. Plugin CBS OOM-active sends central mgmt. app config changes to ER K 8 S cluster using ER K 8 S API CRD Inven tory DH DM DM AAP AAF SO SO ONAP at Edge Servi ce. Ch ange OTIHand ler Dynamic Mgmt. application (DCAE service components) Eve nt. Pr oc Coll ecto r CLA MP MP Polic y Hand er K 8 S CLUSTER Poli cy cy SDC AAI K 8 S CLUSTER Base OOM Orch. Components ONAP Central Mgmt. Application 1 4 Stora ge (PG) Optional OOM Orch. Components 4 OOM-active deploys other OOM-active installs K 8 S clusters in relevant Edge Clouds based on config OOM-active places mgmt. 2 app on ER K 8 S cluster using ONAP Central OOF and ER K 8 S API OOM-active monitors mgmt. 3 app metrics on ER K 8 S cluster using ER K 8 S API Dash boar d Ana lytic ss Coll ecto r r External Cloud CL support VNF AP CO P L VNF-APP package Configuration Binding Service (CBS): Provides API to obtains configuration parameters from Consul during a deployment or reconfiguration process. Consul: Provides service discovery and key-value storage capabilities Dashboard API: The Dashboard provides AC and GUI access for orchestrator Deployment Handler (DH): Provides an interface to deploy/access information (e. g. , blueprints) in Inventory OTI/Handler: Interface between A&AI and prepares events concerning VNF/topology changes in A&AI and forwards them to controller. Inventory: Stores blueprints in its Post. Gres (PG) database Policy Handler (PH): Interface to external Policy Engine for receiving and processing policy related information including updates Service Change Handler Provides an interface to SDC for receiving blueprints and storing them into Inventory (PG) Cloud Native Integration Modules K 8 S ETCD: Provides key-value storage capabilities. K 8 S usage model – config map/secretes Istio Service Mesh: Provides service discovery, security, traffic management Helm: App versioning/upgrade/rollback K 8 S Operator/CRD: Framework for building custom controllers (CC) e. g. to dispatch app config changes from Central to ER Cloud

Benefits via DCAE Platform integration into OOM ØSupport for Dynamic Control Loop support for management application deployment/LCM ØPolicy based configuration support across Central and Edge consistently ØComplete backward compatibility for both HELM and TOSCA 7

Additional Features available with this proposal ØDesign flow integration for automation of deployment artifact creation ØSupport containerized and VM based workload deployment on heterogenous cloud environment ØProvide deployment states, relationship and dependencies via Cloudify ØSupports single and/or multiple management application (allowing service composition design) ØSupport dynamic DMAAP topic provisioning capabilities part of orchestration. ØSupport Hierarchical and distributed deployment (with central and regional/Edge site) ØConsolidated view of deployed MS and their relationship ØHA and Georedundancy support ØInfrastructure management (if required) ØStandardization of AAF integration through plugin 8

Management Application Onboarding Stand-alone (non-SDC) DCAE Main Steps 1. Developer inputs JSON Component Spec (and Policy JSON if applicable) into blueprint generator of the Onboarding Toolbox 2. Output is the Cloudify blueprint 3. Cloudify blueprint is added to EOM Inventory via the Dashboard Using SDC DCAE Main Steps 1. Developer inputs JSON Component Spec (and Policy JSON if applicable) into blueprint generator of the Onboarding Toolbox 2. Output is TOSCA Model files 3. Service Designer adds Model files to SDC Catalog 9

Deployment Workflow Stand-alone (No design CL using SDC/CLAMP dependency) DCAE

Summary Ø Solution proposed will enable many features and options for ONAP operators through OOM Ø Production grade; implemented in AT&T production since 2017 to manage application across multisite/cluster/tenant and infrastructure. Ø Backward compatible with current ONAP OOM and DCAE deployments.

Demo on AT&T Operation manager

Heterogeneous Platform Setup 33. Cloudify installs Kubernetes on a cluster of nodes 44. Different namespaces are created 55 Install AT&T Operation Manager Components on Kubernetes VMs K 8 s AT&T Operation Manager Tenant Space 1 Dev. Ops manually 1. installs Cloudify in the AT&T Operation Manager Tenant space, on a VM cluster 22. Cloudify installs Ha. Proxy, PG and Consul on VMs Cloudify DTI Namespace AT&T Operation Manager Namespace API Dashboard Handler PG Consul AT&T Operation Manager Tenant Space DCAE Namespace Service Change Handler DTI Handler DBCL GUI DTI ha. Proxy Plug-Ins Ops Tools Inventory Policy Handler Deploymt Handler Maria. DB Cassandra My. SQL Music Cassandra Zookeeper Config Bind Service DB per DB Cinder Persistent Storage 66. Plug-ins are installed via Cloudify 77. Install Ops Tools on every VM 8 8. Install DBs for ECOMP Applications 99. Persistent Storage and Cinder is created using persistent volume 10 Using orchestrator, AT&T Operation 10. Manager installs ECOMP Applications on multiple sites DCAE Central Site DCAE Regional/Edge ha. Proxy Docker cluster DMaa. P K 8 s cluster hosting DCAE microservices 13 © 2017 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. pgda cluster Docker cluster DMaa. P cluster ha. Proxy cluster CC Docker Classic Controller K 8 s cluster hosting DCAE microservices 11 Dev. Ops 11. installs DCAE Platform Components in DCAE Central and Regional/Edge sites

AT&T Tenants Information § Over 3000 VMs § 50 - 60 k 8 s clusters in various environments supporting multiple releases for Dev, Testing and Production. § Each VM has a capacity of minimum 8 CPU and 32 GB RAM All environments are installed and orchestrated by AT&T Operation Manager 14 © 2017 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

AT&T Operation Manager - Summary § AT&T Operation Manager is an integral part of the ECOMP architecture for orchestration of management applications using ONAP-DCAE Platform components. § AT&T Operation Manager provides following support: • • • 15 Helm Chart and TOSCA blueprint based onboarding and deployment. Event driven reconfiguration of microservices (topology events and Policy flows) Deployment of Control Loop flows and support through CLAMP/SDC Geo-resilience across multiple sites User access control and namespace separation for SSO and RBAC TLS Security management (certificate delivery & auto-renewal) Management of persistent volumes (Gluster FS) Management of Dev. Ops tools and fulfillment of security requirements (AT&T internal) Dynamic DMAAP topics provisioning/configuration for management application Consolidated view of deployed MSs and their relationships Well defined API support with swagger documentation. © 2017 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.

Backup 16

OOM – Functional Gaps (Dublin) Design ØNo design flow integration and standardized configuration modelling enforced (under Helm templates) ØOn-demand Service design creation and deployment of single/composed management application Instantiation ØControl Loop flow deployment and support through CLAMP/Policy/SDC Øx. NF Event based application management (deployment and configuration) Run-time ØDynamic configuration management through central ONAP Policy ØNo backward support on Tosca based ONAP application and workflow ØDynamic DMAAP topics provisioning/configuration for management application ØConsolidated view of deployed MS and their relationship Platform/Infrastructure ØDeployment of dynamic service components across multiple K 8 S cluster ØSupport for Heterogeneous environment/payload (eg. K 8 S, VM and Openstack) ØInfrastructure management associated with new service components ØMaintenance (manual) of chart/values. yaml is not scalable approach for operation ØGeo-redundancy management support for ONAP components ØStandardized Security integration 17