Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I21f65eebaa0f4655c37bba2ccbd965b6111a2c61
Issue-ID: VFC-1710
Signed-off-by: dyh <dengyuanhong@chinamobile.com>
|
|
Change-Id: I8602f2cbe425a061470e62d2a6fc490904f42256
Issue-ID: VFC-1601
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
|
|
Issue-ID: OOM-906
Change-Id: Ic65127d3981cb0a696c784392cab59fbf06b1e66
Signed-off-by: BorislavG <Borislav.Glozman@amdocs.com>
|
|
The service name of vfc-workflow and vfc-workflow-engine are both "workflow" in MSB register annotations. Actually they are two different service.
Change-Id: I45bb3a131431bb4893c0dc992cdb008c1045cf84
Issue-ID: OOM-949
Signed-off-by: LiZi <li.zi30@zte.com.cn>
|
|
Change-Id: Ie7064b59032c6cd81ee37466c89a5dee74530939
Issue-ID: OOM-750
Signed-off-by: Mike Elliott <mike.elliott@amdocs.com>
|