| commit | 2e26b58b9d09edee0b517c87f916eef08d567270 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Feb 09 10:39:55 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Feb 09 10:42:38 2024 +0100 |
| tree | bdf100b646f125699b4d1a3a52281bf6e8e3cf4b | |
| parent | ad8e7c7a9b5da7c348d9c1c6a3eda61f49301150 [diff] |
[SDC] Remove MR connection in SDC-BE SDC-BE still uses "healthcheck" calls to MR. To avoid these calls and possible autocreated Topics, this patch changes the MR connection URLs to avoid these calls Issue-ID: OOM-3272 Change-Id: I06834b9b12d1ad92f83e5c8ff1a096948b2ebf71 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.