| commit | e05d9d505e41d24065dcab5ab09d4da9aec5ae01 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Sat May 18 18:11:21 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Sat May 18 18:11:21 2024 +0200 |
| tree | 24eb5845c1f647cbc0cb1ac321623680e807a182 | |
| parent | a9c755eed08ec9c22f4e7190fc9691bbfad734f4 [diff] |
[PORTALNG] Dns resolver ip not configured in portal-ng-ui chart - define CLUSTER_NAMESERVER_IP since it is needed in the nginx config Issue-ID: PORTALNG-103 Change-Id: I60a9784dffcfd0c4a575e6c66641f69b0f6204e2 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@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.