| commit | 4be5581537d8acd33636f3f621831efae96ee4ac | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Wed Dec 14 13:49:28 2022 +0000 |
| committer | efiacor <fiachra.corcoran@est.tech> | Wed Dec 14 13:49:34 2022 +0000 |
| tree | 79c176eea95a870e056e7f73be482aab759c2f15 | |
| parent | f6bda71b5f76434b09004c5adfc8dab8cf17c1c2 [diff] |
[APPC] Remove appc chart and refs Removing appc chart Removing most appc refs Some SO data may need to be followed up with SO team Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I183e3dfb7e33a3ada1ac9925ee96b9f32d89bd5a Issue-ID: OOM-3069
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.