| commit | c1aa16001293e9ef6c36127c55b47e887f5f9250 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Tue Jan 11 12:57:19 2022 -0500 |
| committer | Jack Lucas <jflos@sonoris.net> | Wed Jan 12 12:27:35 2022 -0500 |
| tree | 2d84c48ff606658b71960edb64013139713971ea | |
| parent | 98b40be0f580491e015b0c1c33debfccb40a404f [diff] |
[DCAEGEN2] Move ves-openapi-manager to dcaegen2-services In preparation for disabling the entire dcaegen2 chart tree later in the Jakarta release cycling, move the dcae-ves-openapi-manager chart from dcaegen2 to dcaegen2-services. Add dcae-ves-openapi-manager to the list of components to be healthchecked as part of dcaegen2-services. Issue-ID: DCAEGEN2-2968 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I2fcc55ba0a8af7f249454f98a8d4749138a76948
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.