Gitiles
Code Review Sign In
gerrit.nordix.org / onap / oom / cf911895c5b725fcea8a70104dd1acbb4e9e74e3
commitcf911895c5b725fcea8a70104dd1acbb4e9e74e3[log] [tgz]
authorAndreas Geissler <andreas-geissler@telekom.de>Thu Jun 06 15:27:38 2024 +0200
committerAndreas Geissler <andreas-geissler@telekom.de>Mon Jun 10 11:53:19 2024 +0200
tree1457074f7869daecf89a6c44f573ad438d4f82f9
parent3aca0e2323480a220cd4064731755cf9aab0278b [diff]
[COMMON] Disable components in default deployment in NewDelhi

Components are disabled from the default deployment, which
- do not support the native Kafka interfaces (DMaaP MR removal)
  - dmaap/message-router
  - dcaegen2-services/dcae-datafile-collector
  - dcaegen2-services/dcae-heartbeat
  - dcaegen2-services/dcae-kpi-ms
  - dcaegen2-services/dcae-pm-mapper
  - dcaegen2-services/dcae-pmsh
  - dcaegen2-services/dcae-restconf-collector
  - dcaegen2-services/dcae-slice-analysis-ms
  - dcaegen2-services/dcae-snmptrap-collector
  - dcaegen2-services/dcae-son-handler
  - dcaegen2-services/dcae-tcagen2
  - dcaegen2-services/dcae-ves-mapper
  - nbi
  - sdnc/dmaap-listener

- are not supported by multiple releases
  - cli
  - holmes
  - oof
  - msb
  - vfc
  - vnfsdk
  - modelling

- deactivation is agreed by TSC
- change the order of deployment in helm deploy plugin

Issue-ID: OOM-3301

Change-Id: I692117405473a2eb666304b421bdf7e4c4be06b3
Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
5 files changed
tree: 1457074f7869daecf89a6c44f573ad438d4f82f9
  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.