| commit | edfcd494c54a435ee4c4257ff1abe0e67fc9456f | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Apr 17 14:01:32 2024 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Apr 17 14:03:26 2024 +0200 |
| tree | 02e548a213b204e8f45ea888d098009f4a0b629f | |
| parent | f8a899c48c91681eb61f3968583862ffc9e9ad73 [diff] |
[SDNC] Disable MessageRouter ReadinessCheck in UEB Listener As the UEB Listener is already migrated to Kafka, the ReadinessCheck in the deployment.yaml is deleted Issue-ID: OOM-3291 Change-Id: If940f1e90b3bf3762ae70d7f96acd71357e4ffe7 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
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.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.