forked from gormanm/mmtests
-
Notifications
You must be signed in to change notification settings - Fork 0
/
host_config
129 lines (110 loc) · 5.16 KB
/
host_config
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
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
# Example MM Test host config file, for run-kvm.sh
export MMTESTS_HOST_IP="192.168.122.1"
export AUTO_PACKAGE_INSTALL="yes"
# SSH options, in the sshd_config(5) format (see `-o` in `man ssh`). MMTests
# already uses `-o StrictHostKeyChecking=no` (and a few others, e.g., for
# passwordless login).
#
# Note that all the options specified here, will be used for `pssh` too (via
# `-O`, see `man pssh`).
#export MMTESTS_SSH_CONFIG_OPTIONS="-o LogLevel=INFO"
# Options to be passed to `pssh` (see `man pssh`). MMTests deal by itself with
# all the options related to the various "hosts" to which we will connect during
# the test (namely, `-H`). And where the output is saved (if desired) can be
# controlled with MMTESTS_PSSH_OUTDIR (see below). This should contain other
# options, if they are desired, such as, for instance, `-v`).
#export MMTESTS_PSSH_CONFIG_OPTIONS="-v"
# Let's have run-mmtests.sh output from the VMs in /tmp
#export MMTESTS_PSSH_OUTDIR=/tmp
# List of VMs inside which to run the tests
# (if not specified via command line)
#export MMTESTS_VMS="vm1 vm2"
# When running benchmarks in multiple VMs, coordination between the host and
# the VMs happens over network. VMs will contact the host at MMTESTS_HOST_PORT
# (TCP) port, while host will contact guests at MMTESTS_GUEST_PORT (TCP) port.
#export MMTESTS_HOST_PORT=1234
#export MMTESTS_GUEST_PORT=4321
# If we find already defined VMs in the system, shall we undefine them and
# (try to) re-create them from scratch? Set this variable to yes, if that is
# the case
#export MMTESTS_VMS_UNDEF_BEFORE_START="yes"
#export MMTESTS_VMS_UNDEF_REMOVE_STORAGE="yes"
# The location of config files for guests (e.g., libvirt xml config files for
# VMs) that are not defined already when starting the benchmark can be listed
# in this variable. They will then be read and an attempt to define such VMs
# will be made, before starting the tests. A (coma separated) list of dirs
# can be specified.
#
# If using both this variable and the --vm-xml-dir command line switch, the
# latter has priority. Also, MMTests will always check if there are suitable
# xml files in the main directory (see $SCRIPTDIR), as last resort.
#
# Order matters as, for each VM, we will stop and use the first suitable
# config file that we find.
#export MMTESTS_VMS_XML_DIR=
# If `numad` should be used on the host
#export MMTESTS_NUMA_POLICY="numad"
# The `tuned` that will be used on the host
#export MMTESTS_TUNED_PROFILE="latency-performance"
# XXX
#export MMTESTS_VMS_SSHKEY=./mmtests_vms_sshkey
# List of monitors for the host
export RUN_MONITOR=yes
export MONITORS_ALWAYS="top"
export MONITORS_GZIP="proc-vmstat mpstat"
export MONITORS_WITH_LATENCY="vmstat"
export MONITORS_TRACER="perf-event-stat"
export MONITOR_PERF_EVENTS=cpu-migrations,context-switches
export MONITOR_UPDATE_FREQUENCY=10
# If the VMs are up already, and we know their IPs, we can
# use them directly. Note that this means:
# - run-kmv.sh will not (try to) power on the VMs, it will
# assume that they're up already and go straight to try
# to connect to them
# - run-kvm.sh will not (try to) shutdonw the VMs at the
# end of the benchmark, it will just leave them as they
# are
# - the MMTESTS_VMS array must be provided as well, and it
# must have the same number of entries than MMTESTS_VMS_IP
# (and names will be associated with IPs in the order they
# are found in the two arrays)
#export MMTESTS_VMS_IP="192.168.122.24 192.168.122.38"
#export MMTESTS_VMS="vm_a vm_b"
# List of VMs inside which to run the tests
# (if not specified via command line)
#export MMTESTS_VMS="vm1 vm2"
# XXX
# - kvm-set-hostname: set the hostname of each VM to their name
# (as defined in this file, e.g., vm1, vm2, ecc)
#export MMTESTS_POST_VM_START_SCRIPTS=kvm-pkg-update,kvm-set-hostname
# The location of config files for guests (e.g., libvirt xml
# config files for VMs) that are not defined already when
# starting the benchmark and that MMTests have then to create,
# can be speficied in this variable. Note that, If using both
# this variable and the --vm-cfg-path command line switch, the
# latter will have priority. And, as a last resort, we will
# also always check in MMTests directory.
#export MMTESTS_VMS_CFG_DIR=
# XXX
#export MMTESTS_VMS_COPY_DISK_FILE=/vmimages/vms.disk
#export MMTESTS_VMS_COPY_DISK_COW="false"
# XXX Guests configurations
#
# XXX For all VMs / Defaults, for installing
#export MMTESTS_VMS_INSTALL_LOCATION=
#export MMTESTS_VMS_AUTOYAST_DIR=
#export MMTESTS_VMS_AUTOYAST="${SCRIPTDIR}/autoyast/opensuse.xml.erb"
#export MMTESTS_DEPLOY_DISTRO_SPEC="
#openSUSE-Tumbleweed@https://download.opensuse.org/pub/opensuse/tumbleweed/repo/oss/@$MMTESTS_VMS_AUTOYAST
#openSUSE-Leap-15.4@https://download.opensuse.org/pub/opensuse/distribution/leap/15.4/repo/oss/@openSUSE-Leap.xml
#openSUSE-Leap-15.3@https://download.opensuse.org/pub/opensuse/distribution/leap/15.3/repo/oss/@openSUSE-Leap-15.3.xml
"
#export MMTESTS_VMS_DEPLOY_DISTRO="openSUSE-Tumbleweed"
# XXX For all VMs / Defaults, for VM config
#export MMTESTS_VMS_MEMORY=
#export MMTESTS_VMS_CPUS=
#export MMTESTS_VMS_DISK_FILE_SIZE=
#export MMTESTS_VMS_DISK_POOL=
export vmtest1_DEPLOY_DISTRO="openSUSE-Tumbleweed"
export vmtest1_CPUS=4
export vmtest1_MEMORY=4096