| commit | 702d68ae02195cbe56ab5f5cd61bddc816880076 | [log] [tgz] |
|---|---|---|
| author | wr148d <wr148d@att.com> | Thu Oct 20 18:26:54 2022 -0400 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 24 06:35:39 2022 +0000 |
| tree | 309975db9e1d8eae56767027f908140095dc95c7 | |
| parent | 39e72c96e5675fd3bc2e7966a359bfb101bd809a [diff] |
[AAI] Release 1.11.0 images for Kohn Releasing the latest docker images aai-babel aai-graphadmin aai-modelloader aai-schema-service aai-traversal Issue-ID: AAI-3537 Signed-off-by: wr148d <wr148d@att.com> Change-Id: I8fdec3465b63a5e445f7e567884bbc8ee74c4e95
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.