Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / 353a8c92280d3a92133ea077e5160f5b93774556
commit353a8c92280d3a92133ea077e5160f5b93774556[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Wed Mar 15 16:15:11 2023 +0100
committerAndreas Geissler <andreas-geissler@telekom.de>Mon Mar 20 14:18:33 2023 +0100
tree1b3a02a41642cbd846da5e8dafa5d0982f4c7f53
parent8a626708ed05ca337586695b2056441fc6405fec [diff]
[A1P] Chart Cleanup from TLS/AAF

Update the charts and remove all TLS/AAF related entries

Issue-ID: OOM-3112

Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: I50dc3aea3360ee0d593942481edcb7ff7b572cbd
6 files changed
tree: 1b3a02a41642cbd846da5e8dafa5d0982f4c7f53
  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. INFO.yaml
  16. README.md
  17. requirements.txt
  18. 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.