Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: VFC-1751
Change-Id: I27c96ead9ab0bf5054d9abc4c6664262a0430111
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
Two main process in vfc-redis: redis + mysql
Issue-ID: VFC-1727
Change-Id: Ied784a4ff8270d23f3609a7942dbfb8d81e74084
Signed-off-by: dengyh <dengyuanhong@chinamobile.com>
|
|
Issue-ID: OOM-2469
Signed-off-by: Grzegorz Lis <grzegorz.lis@nokia.com>
Change-Id: Ib7c794cca28ac2494eedba31903dcbd9348820c7
|
|
microserice
Becaue now oom can register the microservice to msb automatically,
if without K8S, we can also register vfc microservice to msb
automatically by vfc container itself.
IF it is set to false, vfc contanier will not register again, if it is
set to true, vfc will register by itself.
we use this flag to determine who is responbile for serice registeration
and it can reduce duplicate registration.
Change-Id: Ie79a8803725ae0c762d9c39a04f922d9823c46e2
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: VFC-1374
Change-Id: I7075ea58836d5a1dafb72eeaf99f90c52d909db6
Signed-off-by: yangyanyj <yangyanyj@chinamobile.com>
|