| commit | 64da4e7f878c9744a8cd2e6380654a1d3b72ca3c | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Fri Mar 03 14:46:05 2023 -0500 |
| committer | Jack Lucas <jflos@sonoris.net> | Tue Mar 14 13:20:26 2023 +0000 |
| tree | 8a20c68b9beffb512e940a54ffe993967716a1ab | |
| parent | 54f3d17790740f7c249318de2ae832c54b90ae0a [diff] |
[DCAE] Remove references to AAF Remove chart elements that deploy an AAF init container and set up volumes that hold AAF-certificates. Remove AAF values.yaml entries that are no longer needed. Issue-ID: OOM-3068 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I8e6659cf6aa4c214d485b9e78c28f55622e3a864
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.