| commit | 2900765560071572d8a5c53482855048cddfac92 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Mar 23 14:05:45 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Mar 27 13:00:51 2023 +0200 |
| tree | 55be0cddd23c1ca39a91a0168edc089dbddd7a3e | |
| parent | 5b76eca5250aa16c7a3fcf8ef984acff2807d656 [diff] |
[STRIMZI] Correction for external Access via Ingress VirtualService TCP route added in _ingress.tpl using protocol option in onap-strimzi ingress configuration Added support for multiple ports in _ingress.tpl added Fixed port setting in onap-strimzi for external interface Add information to the documents section Issue-ID: OOM-3109 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: If8507278d952ee29ceaa3f134b99d18bd6f31cb7
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.