| commit | 60f33d7fa1d42a7d75df330852cd35d2cd316f10 | [log] [tgz] |
|---|---|---|
| author | nandkishorpatke <nandkishor-laxman.patke@t-systems.com> | Thu Nov 16 15:16:54 2023 +0530 |
| committer | Nandkishor Patke <nandkishor-laxman.patke@t-systems.com> | Thu Nov 16 15:26:57 2023 +0000 |
| tree | 2deedc3a8c79489a0f8ef6a6048df8cc9df44284 | |
| parent | 546e7acd3e3bdcfbbf31c28fcf81703dc994f384 [diff] |
[AAI] Update OOM to include the latest version v28 for AAI schema - Updates included to bump to the latest version of the schema v28 - Update latest maven version to 1.12.3 for aai-schema - Maven version to 1.12.3 for resources, graphadmin, traversal, babel Issue-ID: AAI-3663 Change-Id: Ib8f28cb95e9834851941e8676ee242f856c87f83 Signed-off-by: nandkishorpatke <nandkishor-laxman.patke@t-systems.com>
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.