Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
ONAP is too big to be deployed using helm install so we need to
use a custom helm plugin helm deploy. This script deloys onap
component by component instead of deploying evrything at
once. Unfortunately this script also modifies the helm release by
appending component name to it.
As a result of this behavior our objects are called for example:
onap-mariadb-galera-mariadb-galera-0
instead of just being called onap-mariadb-galera-0.
This patch simplifies this naming convention by replacing all direct
usages of .Release.Name with common.release macro which strips the
component specific part from the release name.
Issue-ID: OOM-2275
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
|
|
OOM has now templates in order to create the needed PVC, using:
* a PV with a specific class when using a common nfs mount path between
nodes (sames as today use) --> is the default behavior today
* or a storage class if we want to use dynamic PV.
On this case, we use (in order of priority):
- persistence.storageClassOverride if set on the chart
- global.persistence.storageClass if set globally
- persistence.storageClass if set on the chart
Change-Id: Ibc8825b97cbe8939cf085d1cdd17e0a67e45c96b
Issue-ID: OOM-1227
Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com>
|
|
Issue-ID: OOM-1623
Change-Id: Idd9ecfaa99a7e4e8b57e12a5c442a4a1a3c3a6a0
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|