| commit | 8d72830d90449b34a6dd062b4f9bea88a005f60f | [log] [tgz] |
|---|---|---|
| author | aravind.est <aravindhan.a@est.tech> | Wed Dec 07 12:26:28 2022 +0000 |
| committer | aravind.est <aravindhan.a@est.tech> | Fri Dec 23 16:04:26 2022 +0000 |
| tree | 8b8e9b37d2048f61bff765853ff86bbc304b48dc | |
| parent | 17de6f76f85e39b6e5484a335ebcb1c41e0ef862 [diff] |
[POLICY] Add A1pms participant charts Add A1pms participant helm charts Issue-ID: CCSDK-3816 Signed-off-by: aravind.est <aravindhan.a@est.tech> Change-Id: I4153f070e6f3394667b8ce4a714d0f8e91be4738
The ONAP Operations Manager (OOM) is responsible for life-cycle management of the ONAP platform itself; components such as SO, SDNC, etc.
It is not responsible for the management of services, VNFs or infrastructure instantiated by ONAP or used by ONAP to host such services or VNFs.
OOM uses the open-source Kubernetes container management system as a means to manage the containers that compose ONAP where the containers are hosted either directly on bare-metal servers or on VMs hosted by a 3rd party management system.
OOM ensures that ONAP is easily deployable and maintainable throughout its life cycle while using hardware resources efficiently.
Full documentation is available in ONAP documentation in operations and administration guides.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.