Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / ee119102020f1dc6044f686c748a37ff0e7487de
commitee119102020f1dc6044f686c748a37ff0e7487de[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Thu Apr 11 13:53:39 2024 +0200
committerAndreas Geissler <andreas-geissler@telekom.de>Thu Apr 11 18:41:30 2024 +0200
treeefa4eaf61a118e50697a17ac7853ca62433332d1
parent16d200e4f99dbad508156d936b9481bed051055b [diff]
[COMMON] Update all ReadinessChecks

Use the new "service" feature of the readiness image to
resolve startup dependencies.

Issue-ID: OOM-3280

Change-Id: Ia331d51528676744e5e0479d1fd0ca02830c3499
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
93 files changed
tree: efa4eaf61a118e50697a17ac7853ca62433332d1
  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.