regulus/lab.config.template at main · redhat-performance/regulus · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
#
# Lab environment settings specific to your SUT cloud
# Make sure variables are wrapped by double quote i.e export VAR="my-value"
#

# full path name to kubeconfig. Example, KUBECONFIG="/root/mno/kubeconfig"
export KUBECONFIG=""

# Bastion login username i.e "root" or "kni"
export REG_KNI_USER=""
# Bastion hostname. i.e "my-host.my-company.com"
export REG_OCPHOST=""

# Three workers that Regulus will run tests on. Example below i.e worker-1.company.com
export OCP_WORKER_0=""
export OCP_WORKER_1=""
export OCP_WORKER_2=""

# The list of external host/RHEL that will host INGRESS,EGRESS and TREX. Example BM_HOSTS="host_1 host_2 host_3"
export BM_HOSTS=""

# Provide OVNK primary interface info
export REG_OVN_NIC=
export REG_OVN_NIC_MODEL=
export REG_OVN_NIC_MTU=

# To select the NICs for SRIOV, MACVLAN and TREX. You need to understand your worker nodes connectivity.

# For SRIOV
export REG_SRIOV_NIC=""
export REG_SRIOV_MTU""
export REG_SRIOV_NIC_MODEL=""   # valid models: CX5,CX6,E810,E820,X710,XXV710,BF3

# For MACVLAN
export REG_MACVLAN_NIC=""
export REG_MACVLAN_MTU=""
# MACVLAN config does not care NIC_MODEL

# For TESTPMD
export REG_DPDK_NIC_1=""
export REG_DPDK_NIC_2=""
export REG_DPDK_NIC_MODEL=""

# The remotehost to host TREX. Example e16-h12-b02-fc640.rdu2.scalelab.redhat.com
export TREX_HOSTS=""

# For TREX, choose NICs.
export TREX_SRIOV_INTERFACE_1=""
export TREX_SRIOV_INTERFACE_2=""
export TREX_DPDK_NIC_MODEL=""

# Auto config the TREX NICs. Example, REM_DPDK_CONFIG="true"
export REM_DPDK_CONFIG="false"

#
# ElasticSearch configuration for summary report upload
#
# Note: ES_INDEX is now hardcoded in REPORT/es_integration/es_config.py
# as 'regulus-results-*' to match the rollover index structure.
# DO NOT change it unless you are an expert and understand the ISM/rollover architecture.
#

# For Regulus dev, use local ES server.
# export ES_URL="http://localhost:9200"

# For development http or https server
# export ES_URL="https://$ES_USER:$ES_PASSWORD@$ES_HOST"

# For production, the ci-tools/Prow/CPT invokes a chain: run_cpt.sh -> run_es.sh - run_es.sh constructs ES_URL from /secret
# You do not need to define ES_URL here.

# EXECUTION_LABEL is optional. A user-defined tag (i.e nighlty, weekly, EUS, nok, vz etc.) added to each document,
# export EXECUTION_LABEL="your-token"
#