| commit | 4982ac31186b65b457250fffa2fc3f459fea658e | [log] [tgz] |
|---|---|---|
| author | Tomasz Wrobel <tomasz.wrobel@nokia.com> | Tue Feb 22 15:39:40 2022 +0100 |
| committer | Tomasz Wrobel <tomasz.wrobel@nokia.com> | Wed Feb 23 08:26:19 2022 +0100 |
| tree | 2dcbdffda2a5a91861dccf94549f57cd5d5ac24d | |
| parent | 044b886ee6c43d7087953ffa2267668f2a830a95 [diff] |
[SDC] Top up sdc-helm-validator Top up sdc-helm-validator to 1.3.1 Issue-ID: SDC-3879 Signed-off-by: Tomasz Wrobel <tomasz.wrobel@nokia.com> Change-Id: I9bf55ac9d6e6b5bcfa54324618b9db3d0d30341a
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.