Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / 1e2a197128b2d4faf9b2938aaeed50a5b3d164ad
commit1e2a197128b2d4faf9b2938aaeed50a5b3d164ad[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Thu Oct 17 15:24:46 2024 +0200
committerAndreas Geissler <andreas-geissler@telekom.de>Thu Oct 17 15:24:46 2024 +0200
tree3d9738c45712ca8e2dbaba69aba893d4dc4f89bb
parentcf70098d182c07c4091fd83b3a704a249a4eac7e [diff]
[DOC] Update OOM Documentation

Replace wiki.onap.org links with altassian ones.

Issue-ID: OOM-3317

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