...
This proposal introduces the ONAP Platform OOM (ONAP Operations Manager) – which initially includes a controller for cross-technology orchestration and container orchestration. It is a framework on which a complete set of OAM capabilities can be enabled on ONAPfor the ONAP platform components. The OOM will unify the deployment, management and control capabilities for ONAP, including all components, the data messaging fabric as well as the micro-services (including collectors, analytics, UI apps, etc.) to be on-boarded onto the platform. The ONAP Platform OAM addresses the current lack of consistent platform-wide method in managing software components, their health, resiliency and other lifecycle management functions. With the OOM, service providers will have a single dashboard/UI to deploy & un-deploy the entire (or partial) ONAP platform, view the different instances being managed and the state of each component, monitor actions that have been taken as part of a control loop (e.g., scale in-out, self-heal), and trigger other control actions like capacity augments.
Current Gaps and Initial Use Cases:
- Flexible Platform Deployment - While current ONAP deployment automation enables the entire ONAP to be created, more flexibility is needed to support the dynamic nature of getting ONAP instantiated, tested and operational. Specifically, we need the capability to repeatedly deploy, un-deploy, and make changes onto different environments (dev, system test, DevOps, production), for both platform as a whole or on an individual component basis. To this end, we are introducing the ONAP Platform Controller with orchestration capabilities into the deployment, un-deployment and change management process associated with the platform.
- State Management of ONAP platform components – Our initial health checking of Components and software modules are done manually and lack consistency. We are proposing key modules/services in each ONAP Component to be able to self-register/discovered into the ONAP Platform Controller, which in turn performs regular health checks and determines the state of the Components/software.
- Control Loop Actions – Currently there is a lack of event-triggered corrective actions defined for platform OAM. The ONAP Platform Controller will enable DevOps to view events and to manually trigger corrective actions. The actions might be simple initially – stop, start or restart the container. Over time, more advanced control loop automation, triggered by policy, will be built into the ONAP Platform Controller.
...
Proposed ONAP Platform Controller Functional Architecture:
- UI/Dashboard – this provides DevOps users a view of the inventory, events and state of what is being managed by the ONAP Platform Controller, and the ability to manually trigger corrective actions on a component. The users can also deploy ONAP instances, a component, or a change to a software module within a component.
- API handler – this supports NB API calls from external clients and from the UI/Dashboard
- Inventory & data store – tracks the inventory, events, health, and state of the ONAP instances and individual components
- ONAP Lifecycle Manager – this is the TOSCA-based orchestration engine for deploying/un-deploying instances and components. It will trigger downstream plugin actions such as instantiate VMs, create containers, stop/restart actions, etc.
- SB Interface Layer – these are a collection of plugins to support actions and interactions needed by the ONAP Platform Controller to ONAP instances and other external cloud related resources – plugins may include Openstack, Docker, Kubernetes, Chef, Ansible, etc.
- Service & Configuration Registry – this function performs the registry and discovery of components/software to be managed as well as the subsequent health check on each registered component/software
Scope:
- In scope: ONAP Platform lifecycle management & automation through containers, i.e.
- Platform Deployment: Automated deployment/un-deployment of ONAP instance(s) / Automated deployment/un-deployment of individual platform components
- Platform Monitoring & healing: Monitor platform state, Platform health checks, fault tolerance and self-healing
- Platform Scaling: Platform horizontal scalability
- Platform Upgrades: Platform upgrades
- Platform Configurations: Manage overall platform components configurations
- Platform migrations: Manage migration of platform components
- Out of scope: support of container networking for VNFs. The project is about containerization of the ONAP platform itself.
Initial proposal - ONAP Containerization with Docker/Kubernetes
...
- Duplicate containers – The VM structure of ONAP hides internal container structure from each of the components including the existence of duplicate containers such as Maria DB.
- DCAE - The DCAE component not only is not containerized but also includes its own VM orchestration system. A possible solution is to not use the DCAE Controller but port this controller’s policies to Kubenetes directly, such as scaling CDAP nodes to match offered capacity.
- Ports - Flattening the containers also expose port conflicts between the containers which need to be resolved.
- Permanent Volumes - One or more permanent volumes need to be established to hold non-ephemeral configuration and state data.
- Configuration Parameters - Currently ONAP configuration parameters are stored in multiple files; a solution to coordinate these configuration parameters is required. Kubernetes Config Maps may provide a solution or at least partial solution to this problem.
- Container Dependencies – ONAP has built-in temporal dependences between containers on startup. Supporting these dependencies will likely result in multiple Kubernetes deployment specifications.
Scope:
- In scope: ONAP Platform lifecycle management & automation through containers, i.e.
- Platform Deployment: Automated deployment/un-deployment of ONAP instance(s) using containers / Automated deployment/un-deployment of individual platform components using containers,
- Platform Monitoring & healing: Monitor platform state, Platform health checks, fault tolerance and self-healing using containers
- Platform Scaling: Platform horizontal scalability through containers
- Platform Upgrades: Platform upgrades using containers
- Platform Configurations: Manage overall platform components configurations
- Platform migrations: Manage migration of platform components
- Out of scope: support of container networking for VNFs. The project is about containerization of the ONAP platform itself.
...