| commit | b5e285018790c9e40b4e8434a05153c422a129ce | [log] [tgz] |
|---|---|---|
| author | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Mon Oct 02 17:04:40 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Nov 14 14:24:12 2023 +0100 |
| tree | c2c2bd797c59f27f0a9935c46360546b3020ce9e | |
| parent | eebb77d435b870f92e70a9d6bcd98953b02bdc32 [diff] |
[CDS] Bump CDS version to 1.5.3 Bug fixes related with UATesting and added PROTOCOL "http" for cds-ui Issue-ID: CCSDK-3934 Signed-off-by: Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> Change-Id: I91526c358c83d06bca694b794b5efe62f4cc4c75
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.