| commit | 7b171084978107b8f57d2038ac7939900927dcdb | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 17 11:21:11 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 17 11:24:06 2022 +0200 |
| tree | 4d0766d722c4b62c6d30c6ed43c149c4539fd427 | |
| parent | 9a51e07a2164c9be42d9d329559f4d2081b8f3fc [diff] |
[POLICY] Correction on PAP MR connection port On non-TLS setup the MR port is 3904 instead of 3905, which needs to be set in the papParameters file Issue-ID: OOM-3003 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ie5ee14209660f00e69b6e4b1df5a992731f500f6
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.