1
|
# ================================================================== #
|
2
|
# #
|
3
|
# SAMPLE MULTI-CONFIGURATION FILE #
|
4
|
# #
|
5
|
# ================================================================== #
|
6
|
|
7
|
# Haizea's regular configuration file (the one that is provided
|
8
|
# to the Haizea daemon) allows for, at most, one tracefile to
|
9
|
# be used. However, when running simulations, it is often necessary
|
10
|
# to run through multiple tracefiles in a variety of configurations.
|
11
|
# The "multi-configuration" file allows you to easily do just this.
|
12
|
# It is similar to the regular configuration files (all the options
|
13
|
# are the same), but it allows you to specify multiple tracefiles
|
14
|
# and multiple configuration profiles.
|
15
|
#
|
16
|
# The multi-configuration file must contain a section called "multi"
|
17
|
# where some general options are specified (e.g., the tracefiles you
|
18
|
# want to use). Then, for each section you would ordinarily include
|
19
|
# in a regular configuration file, you can include common options
|
20
|
# (shared by all profiles) and profile-specific options. For example,
|
21
|
# suppose you want to specify options in the "general" and
|
22
|
# "simulation" sections, and you want to create two profiles
|
23
|
# called "nobackfilling" and "withbackfilling". You would
|
24
|
# have to create the following sections:
|
25
|
#
|
26
|
# [common:general]
|
27
|
# ...
|
28
|
#
|
29
|
# [common:simulation]
|
30
|
# ...
|
31
|
#
|
32
|
# [nobackfillingn:general]
|
33
|
# ...
|
34
|
#
|
35
|
# [nobackfilling:simulation]
|
36
|
# ...
|
37
|
#
|
38
|
# [withbackfilling:general]
|
39
|
# ...
|
40
|
#
|
41
|
# [withbackfilling:simulation]
|
42
|
# ...
|
43
|
#
|
44
|
# Once you've created the multi-configuration file, you must
|
45
|
# feed it into the "haizea-generate-configs" command, which will
|
46
|
# generate a regular configuration file for every combination
|
47
|
# of tracefile and configuration profile. Since running each
|
48
|
# configuration individually would be cumbersome, you can
|
49
|
# also use the "haizea-generate-script" command to generate
|
50
|
# a script that will run through all the generated configuration
|
51
|
# files.
|
52
|
|
53
|
# The following example file uses two example tracefiles, one where
|
54
|
# best-effort leases end prematurely, and one where they don't, and
|
55
|
# two injections of AR leases (with no special characteristic other
|
56
|
# than the fact that the two are different). The file defines
|
57
|
# four configuration profiles:
|
58
|
#
|
59
|
# - "nobackfilling": best-effort leases are scheduled without
|
60
|
# backfilling
|
61
|
# - "backfilling": best-effort leases are scheduled with
|
62
|
# aggressive backfilling, but without suspend/resume
|
63
|
# - "backfilling+SR": best-effort leases are schedules with
|
64
|
# aggressive backfilling and suspend/resume, but without
|
65
|
# migration.
|
66
|
# - "backfilling+SR+M": The whole shebang: backfilling,
|
67
|
# suspend/resume, and migration.
|
68
|
|
69
|
[multi]
|
70
|
tracedir: /usr/share/haizea/traces/multi
|
71
|
tracefiles: withprematureend.lwf withoutprematureend.lwf
|
72
|
injectiondir: /usr/share/haizea/traces/multi
|
73
|
injectionfiles: inj1.lwf inj2.lwf
|
74
|
datadir: /var/tmp/haizea/results
|
75
|
|
76
|
[common:general]
|
77
|
loglevel: STATUS
|
78
|
mode: simulated
|
79
|
lease-preparation: unmanaged
|
80
|
persistence-file: none
|
81
|
|
82
|
[common:accounting]
|
83
|
probes: ar best-effort cpu-utilization
|
84
|
|
85
|
[common:simulation]
|
86
|
clock: simulated
|
87
|
starttime: 2006-11-25 13:00:00
|
88
|
resources: 4 CPU:100 Memory:1024
|
89
|
imagetransfer-bandwidth: 100
|
90
|
status-message-interval: 15
|
91
|
|
92
|
[common:scheduling]
|
93
|
suspend-rate: 50
|
94
|
resume-rate: 50
|
95
|
|
96
|
[nobackfilling:scheduling]
|
97
|
backfilling: off
|
98
|
suspension: none
|
99
|
migration: no
|
100
|
|
101
|
[backfilling:scheduling]
|
102
|
backfilling: aggressive
|
103
|
suspension: none
|
104
|
migration: no
|
105
|
|
106
|
[backfilling+SR:scheduling]
|
107
|
backfilling: aggressive
|
108
|
suspension: all
|
109
|
migration: no
|
110
|
|
111
|
[backfilling+SR+M:scheduling]
|
112
|
backfilling: aggressive
|
113
|
suspension: all
|
114
|
migration: yes
|
115
|
|