| commit | 5846a6e2d0faa43d5abf23d79bd556508bb87d2d | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Mar 30 17:26:14 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Mar 31 11:37:50 2023 +0000 |
| tree | ff025a2c19491869614ec4497277e5760ad7b3cc | |
| parent | 38525b9ce0e8ff2dd9289220c098c00da8219d60 [diff] |
[AAI] Update Service definitions to support Ingress case Fix the service definitions to automatically change NodePorts to ClusterIPs in case of Ingress enabled Issue-ID: OOM-3111 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I27fbcc917190f1df3d39f1bfc789664bb55809a2
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.