Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / ad047fa5ad6fcdf27e65dbe3b9dd61c6dfabcd01
commitad047fa5ad6fcdf27e65dbe3b9dd61c6dfabcd01[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Wed Jul 03 17:56:21 2024 +0200
committerAndreas Geissler <andreas-geissler@telekom.de>Wed Jul 03 17:56:21 2024 +0200
tree94e36d30952e01f8a394e4f1cc50873a768d3e9c
parente5cad98137d9403bcb43a8715dbd7ad9b4967615 [diff]
[COMMON] Bump ONAP version

Set new ONAP main chart version to 15.0.0 (Oslo)

Issue-ID: OOM-3303

Change-Id: I3e2e05a9a46a6e179d30412b133bbff3ec1743f3
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
1 file changed
tree: 94e36d30952e01f8a394e4f1cc50873a768d3e9c
  1. .ci/
  2. .gitlab/
  3. docs/
  4. kubernetes/
  5. TOSCA/
  6. .gitignore
  7. .gitlab-ci.yml
  8. .gitlint
  9. .gitreview
  10. .pre-commit-config.yaml
  11. .pylintrc
  12. .readthedocs.yaml
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. docker-compose.yml
  16. INFO.yaml
  17. README.md
  18. requirements.txt
  19. tox.ini
README.md

ONAP Operations Manager

Description

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.

Contributing

Please see contributing file to learn on how to contribute

Issues

All issues should be filled in ONAP Jira.