Table of Contents

Project Name:

Proposed name for the project: ONAP Operations Manager
Proposed name for the repository: oom

...

How does this align with external standards/specifications?
- At target, TOSCA should be used to model platform deployments and operations.
Are there dependencies with other open source projects?
- Open source technologies could be Cloudify, Kubernetes, Docker, and others.
- The OOM will have dependency on the current proposed "Common Controller Framework" (CommServ 2) project and will leverage its software framework.
- The OOM will require to work with the MSB project for to perform a comprehensive Service Registry function. At this point, the 2 projects seems to have needs to manage service registry at 2 different levels, i.e. MSB at the micro/macro service endpoint level vs OOM at the micro-service/component level.
- The OOM will have inter-dependencies with DCAE (specifically the DCAE Controller). OOM will be built on the CCF software framework for ONAP platform management. DCAE Controller will be updated to use the same CCF software framework. In addition, OOM ("Root Node") and DCAE Controller ("DCAE Node") form the initial hierarchy of managers for ONAP platform management (as depicted in Slides 7-8 of this deck: https://wiki.onap.org/pages/worddav/preview.action?fileName=ONAP_Operations_Manager_Proposalv2.pdf&pageId=3246809). OOM Root Node is the Tier 1 manager responsible for the entire platform and delegates to the Tier 2 DCAE Controller/DCAE Node to be responsible for managing DCAE and its analytics and collector microservices.
- The current proposed "System Integration and Testing" (Integration) Project might have a dependency on this project - use OOM to deploy/undeploy/change the test environments, including creation of the container layer.
- This project has also a dependency on the LF infrastructure (seed code from ci-management project)

...

Initial Implementation Proposal: ONAP on Containers

Description:

This milestone describes a deployment and orchestration option for the ONAP platform components (MSO, SDNC, DCAE, etc.) based on Docker containers and the open-source Kubernetes container management system. This solution removes the need for VMs to be deployed on the servers hosting ONAP components and allows Docker containers to directly run on the host operating system. As ONAP uses Docker containers presently, minimal changes to existing ONAP artifacts will be required.

...

- How does this project fit into the rest of the ONAP Architecture?
  - Please Include architecture diagram if possible
  - What other ONAP projects does this project depend on?
  - ONAP Operations Manager (OOM) [Formerly called ONAP Controller]: The ONAP on Containers project is a sub-project of OOM focusing on docker/kubernetes management of the ONAP platform components
  - The current proposed "System Integration and Testing" (Integration) Project might have a dependency on this project - use OOM to deploy/undeploy/change the test environments, including creation of the container layer.
  - This project has also a dependency on the LF infrastructure (seed code from ci-management project)
- How does this align with external standards/specifications?
  - N/A
- Are there dependencies with other open source projects?
  - Docker
  - Kubernetes

Resources:

Primary Contact Person: David Sauvageau (Bell Canada)
Munish Agarwak (Ericsson)
John Ng (AT&T)
Arthur Berezin (Gigaspaces)
John Murray (AT&T)
Christopher Rath (AT&T)
Roger Maitland (Amdocs)
Jérôme Doucerain (Bell Canada)
Marc-Alexandre Choquette (Bell Canada)
Alexis De Talhouët (Bell Canada)
- Mike Elliott (Amdocs)
Mandeep Khinda (Amdocs)
Catherine Lefevre (AT&T)

Éric Debeau (Orange)

David Blaisonneau (Orange)
Elhay Efrat (Amdocs)
Eliyahu Noach (Amdocs)
Xin Miao (Huawei)
Joe Zhang (ZTE)
Jason Hunt (IBM)
Jochen Kappel (IBM)
Josef Reisinger (IBM)
Helen Chen (Huawei)
Earle West (AT&T)
Yang Xu (Huawei)
Hong Guan(AT&T)
Committers and Contributors:
- OOM Team

Other Information:

link to seed code (if applicable)
Docker/kubernetes seed code available at Bell Canada - waiting for a repo to be available.
aai/aai-data AAI Chef environment files
aai/logging-service AAI common logging library
aai/model-loader Loads SDC Models into A&AI
appc/deployment APPC docker deployment
ci-management - Management repo for Jenkins Job Builder, builder scripts and management related to the CI configuration.
dcae/apod/buildtools - Tools for building and packaging DCAE Analytics applications for deployment
dcae/apod/cdap - DCAE Analytics' CDAP cluster installation
dcae/operation - DCAE Operational Tools
dcae/operation/utils - DCAE Logging Library
dcae/utils - DCAE utilities
dcae/utils/buildtools - DCAE utility: package building tool
mso/chef-repo - Berkshelf environment repo for mso/mso-config
mso/docker-config -MSO Docker composition and lab config template
mso/mso-config - mso-config Chef cookbook
ncomp/docker - SOMF Docker Adaptor
policy/docker - Contains the Policy Dockerfile's and docker compose script for building Policy Component docker images.
sdnc/oam - SDNC OAM
:
- oom: https://gerrit.onap.org/r/gitweb?p=oom.git
Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
Meets Board policy (including IPR)

...

Repo name: oom
Lifecycle State: IncubationApproved
Primary Contact: David Sauvageau (Bell CanadaMike Elliott (Amdocs)
Project Lead: Mike Elliott (Amdocs)
mailing list tag oom
Committers (Name - Email - IRC):