| commit | c27078435ace81f7723fa06dc35b446a6c9fc307 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Nov 18 17:52:50 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Nov 25 10:20:16 2022 +0100 |
| tree | 5f5eac8211c4b03289c7d2a30b7a7305929759eb | |
| parent | 5086720a72016fbac0c768bb2f02102118c3de7f [diff] |
[COMMON] Correct Ingress template to create Istio GW/VS The template should create for each Ingress service a single Gateway/VirtualService Resource, small update of service template Issue-ID: OOM-3000 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I480f8c7b6b9ca3a84813a9e96c4d796d332facc7
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.