| commit | 1da9965f3e8aa658e08d26e93270d284ff738d19 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue May 28 08:51:51 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Wed May 29 10:51:06 2024 +0200 |
| tree | 97e527b22f9ef7cb728e47b7906bab9933a6f883 | |
| parent | 97946874d18f0b9a43b93e8312f138c1b32de640 [diff] |
[AAI] Deploy latest AAI images - resources from 1.13.4 to 1.13.5 - traversal from 1.13.4 to 1.13.5 - graphadmin from 1.12.3 to 1.13.7 - model-loader from 1.13.6 to 1.14.1 - babel from 1.12.3 to 1.13.1 - schema-service from 1.12.3 to 1.12.4 Generally this includes the DmaaP removal and version upgrade to v29 Issue-ID: AAI-3862 Change-Id: Ide32cc4ddc8dcc32ca43351e4e85ac9b0d512f55 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
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.