| commit | 74a277101800ff2729429e51946070878c046952 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Wed Apr 19 07:12:46 2023 +0000 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Wed Apr 19 08:09:45 2023 +0000 |
| tree | eb33572ece3fae805b58ebce4e4194d9733eb043 | |
| parent | 6356e07a0caa7caef201d64977bd9615f6837853 [diff] |
[COMMON] Add app label to common.labels - add an app label to all resources because this is picked up by Istio Issue-ID: OOM-3164 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de> Change-Id: I71831b29c5c5b9ddc2bcafbc1567ed0dfa971e5c
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.