Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / ee7e3ada3228e4c80b622aa588d48ac34789cedd
commitee7e3ada3228e4c80b622aa588d48ac34789cedd[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Wed Feb 28 14:30:53 2024 +0100
committerAndreas Geissler <andreas-geissler@telekom.de>Wed Feb 28 14:32:45 2024 +0100
treebbf2c0374de2090469dfb766f8b56c725020fcf9
parent634ae79cabf677e32fadcd44d8dc935a2a7a5a3b [diff]
[DOC] In tox.ini update link to upper-constraints.txt

Fix breaking tox execution

Issue-ID: DOC-823

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