Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 98b40be) | patch
[DCAEGEN2] Move ves-openapi-manager to dcaegen2-services 60/126560/2
authorJack Lucas <jflos@sonoris.net>
Tue, 11 Jan 2022 17:57:19 +0000 (12:57 -0500)
committerJack Lucas <jflos@sonoris.net>
Wed, 12 Jan 2022 17:27:35 +0000 (12:27 -0500)
commitc1aa16001293e9ef6c36127c55b47e887f5f9250
tree2d84c48ff606658b71960edb64013139713971eatree | snapshot
parent98b40be0f580491e015b0c1c33debfccb40a404fcommit | 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
kubernetes/dcaegen2-services/Chart.yaml diff | blob | history
kubernetes/dcaegen2-services/components/dcae-ves-openapi-manager/Chart.yaml [moved from kubernetes/dcaegen2/components/dcae-ves-openapi-manager/Chart.yaml with 100% similarity] blob | history
kubernetes/dcaegen2-services/components/dcae-ves-openapi-manager/templates/deployment.yaml [moved from kubernetes/dcaegen2/components/dcae-ves-openapi-manager/templates/deployment.yaml with 100% similarity] blob | history
kubernetes/dcaegen2-services/components/dcae-ves-openapi-manager/values.yaml [moved from kubernetes/dcaegen2/components/dcae-ves-openapi-manager/values.yaml with 100% similarity] blob | history
kubernetes/dcaegen2-services/resources/expected-components.json diff | blob | history
kubernetes/dcaegen2-services/values.yaml diff | blob | history
kubernetes/dcaegen2/Chart.yaml diff | blob | history
kubernetes/dcaegen2/resources/expected-components.json diff | blob | history
kubernetes/dcaegen2/values.yaml diff | blob | history
Introduces the ONAP Platform OOM (ONAP Operations Manager) to efficiently Deploy, Manage, Operate the ONAP platform and its components (e.g. MSO, DCAE, SDC, etc.) and infrastructure (VMs, Containers).