From 1ee85dfee285612fa6bf7cc5a2b28b733f52e06a Mon Sep 17 00:00:00 2001 From: Bartek Grzybowski Date: Thu, 10 Oct 2019 14:57:13 +0200 Subject: [PATCH] Fix setting onap namespace and environment name separately Onap namespace and environment name can be distinct on a per deployment basis and this allows to set them accordingly. Change-Id: Id1b6fdc4f3b4c159117536187197cb308527f8d2 Signed-off-by: Bartek Grzybowski Issue-ID: INT-1323 --- test/vcpe/vcpecommon.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/test/vcpe/vcpecommon.py b/test/vcpe/vcpecommon.py index 1f1c8289a..4b69fe429 100755 --- a/test/vcpe/vcpecommon.py +++ b/test/vcpe/vcpecommon.py @@ -60,8 +60,9 @@ class VcpeCommon: ############################################################################# # Set name of Onap's k8s namespace and sdnc controller pod # CHANGEME part - onap_namespace = 'dev' - sdnc_controller_pod = '-'.join([onap_namespace,'sdnc-sdnc-0']) + onap_namespace = 'onap' + onap_environment = 'dev' + sdnc_controller_pod = '-'.join([onap_environment, 'sdnc-sdnc-0']) template_variable_symbol = '${' cpe_vm_prefix = 'zdcpe' -- 2.16.6