| commit | 95ea136d97f812b0946b03f8d9b2df4cdf3673d3 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Jul 18 20:27:56 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Jul 19 11:14:10 2023 +0200 |
| tree | 1b6ea3ff7402600663e611911cd8670b4d90fb69 | |
| parent | 1be1c0f7ab523184b4c24cbc934d2bcd4afde69f [diff] |
[COMMON] Add version label to be Istio ready Add the "version" label (Chart.Version or Chart.AppVesrion if exists) Correct the metadata of CPS deployment. Issue-ID: OOM-3230 Change-Id: I0a6907ed95c6b0dfcf7f89fec9c3dafbc2fb1d9b Signed-off-by: Andreas Geissler <andreas-geissler@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.