| commit | 63db716df5e8a66512a5e843b9b3588c3fc07ed4 | [log] [tgz] |
|---|---|---|
| author | Rommel Pawar <rommel.pawar@bell.ca> | Wed Nov 16 10:11:24 2022 -0800 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Nov 23 07:51:27 2022 +0000 |
| tree | a635e83312cb0ff19b1abb0cad5be64009685199 | |
| parent | 3502e73a2762fc50f9ba3ae5d65a3efe5f05bead [diff] |
[AAI] OOM AAI Rolling Update fixes Rolling update fixes for aai submodules below aai babel modelloader schema service traversal sparkybe Issue-ID: AAI-3605 Signed-off-by: Rommel Pawar <rommel.pawar@bell.ca> Change-Id: Ia3949ce9e60542a7b0a4f69fb41ba86fe8399739
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.