| commit | 4c9b6ad723ce8d069bcbc852ceff55b966d49dba | [log] [tgz] |
|---|---|---|
| author | Vijay Venkatesh Kumar <vv770d@att.com> | Mon Aug 15 11:15:03 2022 -0400 |
| committer | Vijay Venkatesh Kumar <vv770d@att.com> | Fri Aug 19 10:59:23 2022 -0400 |
| tree | 77c668b79315a47a9ce9f178e21c79e33e369f68 | |
| parent | 9a3395bd906fcdbcd619f82535d0ce7e913ee3c4 [diff] |
[DCAE] Remove platform charts and overrides All platform components has been disabled/deprecated since Jakarta release Change-Id: I8837ad4e6b9ef20cd7c94fefd6ec4b9cb7b20b08 Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com> Issue-ID: DCAEGEN2-3002 Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
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.