Added SLAVE_NODE parameter to CVP-Shaker
With SLAVE_NODE the engineer can manage the slave where
the Shaker server will be started. At the same time this
slave should have the IP address of the
SHAKER_SERVER_ENDPOINT. Fixes the issue PROD-31400.
Change-Id: Iae42bc9f3b2adf5ed8c6ef78d9a2bce03970b94d
Related-Prod: PROD-31400
diff --git a/jenkins/client/job/validate.yml b/jenkins/client/job/validate.yml
index 65e2cd8..92d369c 100644
--- a/jenkins/client/job/validate.yml
+++ b/jenkins/client/job/validate.yml
@@ -559,6 +559,10 @@
type: string
default: "salt"
description: Credentials to the Salt API.
+ SLAVE_NODE:
+ type: string
+ default: "slave01"
+ description: Label or name of node to start the Shaker server (should be one of cicd nodes and should have the IP address of SHAKER_SERVER_ENDPOINT).
SHAKER_PARAMS:
type: text
default: |
@@ -579,8 +583,8 @@
# - SHAKER_EXTERNAL_NET='public'
description: |
YAML context with parameters for running Shaker tests, where
- "SHAKER_SERVER_ENDPOINT" - Address for Shaker server connections (host:port). Should be accessible
- from tenant's VM network (usually equals to public address of cicd node)
+ "SHAKER_SERVER_ENDPOINT" - Address for Shaker server connections (host:port). The IP address of SLAVE_NODE with the port. Should be accessible
+ from tenant's VM network (floating network)
"SHAKER_SCENARIOS" - Path to shaker scenarios in the cvp-shaker docker image
(can be directory or specific file). Main categories are
scenarios/essential/l2