| commit | a32709acf3d267cbc56394443c8d37463d64658f | [log] [tgz] |
|---|---|---|
| author | Cédric Ollivier <cedric.ollivier@orange.com> | Thu Apr 14 10:12:45 2022 +0200 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Thu Apr 21 14:35:32 2022 +0000 |
| tree | d4330f5d7dce6dcd06d5bddb131281add8782f68 | |
| parent | c8964e507dfc9b32a0f29f2a67ce74b1f8a260b9 [diff] |
[DOC] Add bounds to sphinx requirement As ONAP was created before Oct 20 2020 in RTD, we must set bounds to enforce a compatible Sphinx version (see manual). Issue-ID: DOC-782 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com> Change-Id: Icc0f783e36473df0571056fc23461e48aaeb5ce6
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.