| commit | eb4598bd97e43cfd88b3edc871a52d7cf0202884 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Nov 10 15:08:21 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Nov 10 15:17:33 2022 +0100 |
| tree | f6b7d75f35cb0e988c375fff46eb82317a9a78b5 | |
| parent | a8f00b5f159ed51231e7707c7e99ede11d635424 [diff] |
[COMMON] Bump ONAP version Update chart versions 12.0.0 for London Issue-ID: OOM-3046 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ic196235ff4f6ae14a7ecad799bd75a9666b2594a
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.