| commit | 1660a8c5518c45b8a424b15b8c63b71ae0b39c69 | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Tue May 03 16:24:13 2022 +0100 |
| committer | efiacor <fiachra.corcoran@est.tech> | Tue May 03 16:24:19 2022 +0100 |
| tree | 7d48706094ef60898b8b7553a06b45914e92c750 | |
| parent | 9a62578638e21ecc0c12be240af6365b3e84a416 [diff] |
[DOCS] Clean up docs etc Clean up docs dir Add some stuff for J release Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: Ie34bfe9c70129e3ffc34800481e4052faaebe067 Issue-ID: OOM-2953
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.
