Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / 904b8911706aa930c12dd0ac38f0f212378ae9e9
commit904b8911706aa930c12dd0ac38f0f212378ae9e9[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Wed Jul 13 11:51:58 2022 +0200
committerFiachra Corcoran <fiachra.corcoran@est.tech>Fri Jul 29 06:35:33 2022 +0000
tree45c08be8206d7a65735ca3694165f5b3e1f9f92d
parentce8a39cd431e251d3effedbca07063fe25ce45c1 [diff]
[COMMON][CASSANDRA] Cassandra ServiceMesh Improvements

Disable inter-cluster ports from the Sidecar communication

Issue-ID: OOM-2820

Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
Change-Id: Ie9b523e881a6dd5bef62debdf208994d03a08f29
1 file changed
tree: 45c08be8206d7a65735ca3694165f5b3e1f9f92d
  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.