| commit | 11fcd6c6fccd43a3d59936ee987ab99beeb15835 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu May 25 14:33:16 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu May 25 14:36:49 2023 +0200 |
| tree | e3ee042e428b65bd2ca07406bbf1270f0d60916b | |
| parent | f0f8339055f0b5f9d46456009d9437aca50839ed [diff] |
[CDS] Chart cleanup from TLS/AAF options Remove checks and add the usage of common templates Issue-ID: OOM-3113 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I8e08f1cdd7aa29619a7928ffb6e32d81c2d1b802
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.