Code Review / oom.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 0f90269) | patch
Remove catalog component from VFC 18/103918/4
authoryangyan <yangyanyj@chinamobile.com>
Thu, 19 Mar 2020 06:27:44 +0000 (14:27 +0800)
committeryangyan <yangyanyj@chinamobile.com>
Fri, 20 Mar 2020 02:04:40 +0000 (10:04 +0800)
commit29760bf3178147fbedfe3a531edfd1ebb3a2dbad
tree8b2c4b4c803085c17abbca5ff9d7105c9f07c367tree | snapshot
parent0f90269b150bbb38773e421ac754f1c022cf9ea3commit | diff
Remove catalog component from VFC

Because Modeling project has created etsicatalog repo to intent to provide common ETSI catalog service,
VF-C catalog migrates to modeling can help reduce duplication of work and promote unified architecture.

This has reported in Architecture meeting 2019-10-15,and also been confirmed during VF-C Frankfurt Architecture Review.

So the corresponding catalog chart need also be removed

Change-Id: I63172ee17d8ffcdb59ac730c05d85b9a63e4d7a0
Issue-ID: VFC-1649
Signed-off-by: yangyan <yangyanyj@chinamobile.com>
kubernetes/vfc/charts/vfc-catalog/.helmignore [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/Chart.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/resources/config/logging/log.yml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/configmap.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/deployment.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/pv.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/pvc.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/secrets.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/templates/service.yaml [deleted file] blob | history
kubernetes/vfc/charts/vfc-catalog/values.yaml [deleted file] blob | history
kubernetes/vfc/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).