| commit | 464b6507d43dc2473ed2baf96f84369c7819136a | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Aug 06 15:00:30 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Mon Aug 19 13:17:35 2024 +0200 |
| tree | 095962b42b92b3b241bd2770bb1273636af4d7c5 | |
| parent | bf35e55286a0ac2f4fe05f595cda7109f22a5e6a [diff] |
[AAI] Release 14.0.1 chart with Janusgraph update to 0.6.0 - 1.14.5 images for resources, traversal and graphadmin with Janusgraph update (0.5.3 -> 0.6.0) - cleanup janusgraph-realtime.properties file since the 'cassandra' storage.backend option is not supported anymore - use more descriptive port names for schema-service - reduce terminationGracePeriodSeconds of pods to enable quicker deployment - declare pod revisionHistoryLimit for all components - make root log level configurable for all components (via log.level.root) Issue-ID: AAI-3950 Change-Id: I6221963139fcf4b748167940b6e59367661ba1e5 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.