/
meshconfig-agent.conf
144 lines (126 loc) · 6.97 KB
/
meshconfig-agent.conf
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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
## Use 'mesh' blocks to to specify each mesh that the agent should
## configure the host against
#<mesh>
# ## Use 'configuration_url' to specify the URL where the agent should obtain
# ## the mesh configuration from
# configuration_url https://host.domain.edu/example.json
#
# ## To ensure that the configuration is trusted, you can set the
# ## 'validate_certificate' option to 1. This will validate that the certificate
# ## is valid, and matches the hostname. If the 'validate_certificate' option is
# ## set to 1, the 'ca_certificate_file' option must be set.
# #validate_certificate 0
#
# ## The 'ca_certificate_file' specifies which CAs to use to validate the
# ## certificates.
# #ca_certificate_file /etc/pki/tls/certs/ca-bundle.crt # the default RedHat 6 CAs
#
# ## The 'required' field specifies that if this mesh isn't available, or has
# ## problems, to skip making any changes to the host configuration.
# #required 1
#
# ## The 'permit_non_participation' specifies that if the host isn't
# ## included in this mesh, the agent shouldn't thrown an error.
# #permit_non_participation 1
#</mesh>
## You can define more meshes to configure against by adding more 'mesh' blocks.
#<mesh>
# configuration_url https://host.domain.edu/example2.json
# #validate_certificate 0
# #ca_certificate_file /etc/pki/tls/certs/ca-bundle.crt
#</mesh>
# You can use the 'configure_archives' variable to have the mesh configuration generate
# measurement_archive blocks using the write_url from your configuration file. This is disabled
# by default but you can enable it by setting to to 1.
# configure_archives 0
## Use the 'tasks_conf' variable to change the location of the
## meshconfig-agent-tasks.conf file. This is where you can define tasks locally
## and where tests from remote meshes will be populated. This file contains a list of all the
## tests you want run. In a normal configuration, these should be left as what's included below.
#tasks_conf /etc/perfsonar/meshconfig-agent-tasks.conf
## Frequency with which to check the remote meshes, local tasks_conf file, and pScheduler
## server for changes. If any found it will attempt to build any new tasks and delete any old
## ones as required. See also check_config_interval which is the frequency with which to
## check for local configuration file changes
#check_interval 3600
## Frequency in seconds with which to poll this file and the tasks_conf file for changes.
## If any changes are detected, it will attempt to build any new tasks and delete any old
## ones as required. Should generally be less than check_interval to have any value.
#check_config_interval 60
# You can include one or more 'address' options to specify which address
## corresponds to this host. By default, the agent will attempt to guess the
## address using the hostname of the host, as well as the hostname IPs.
#address client-host.domain.edu
## You can use the "local_host" directive to define properties for a host
## you'd normally define in a MeshConfig host directive. This allows you to tag the host
## and addresses locally, which is especially useful for meshes dynamically generated
## using host tags. You can also define <measurement_archive> blocks to define the
## archives you want tho host to use.
# <local_host>
# tag myorganization
#
# <address>
# address 10.0.1.1
# tag latency
# </address>
# <address>
# address 10.0.1.2
# tag throughput
# </address>
#
# <measurement_archive>
# type perfsonarbuoy/bwctl
# read_url http://client-ma.domain.edu/esmond/perfsonar/archive
# write_url http://client-ma.domain.edu/esmond/perfsonar/archive
# </measurement_archive>
# </local_host>
# The 'send_error_emails' option can be used to tell the agent to send an email
# (via sendmail) when an error occurs. These emails will be sent to the
# applicable administrators (e.g. the local administrator(s), the mesh
# administrator(s), the site administrator(s), and/or the host
# administrator(s).
#send_error_emails 1
## By default, the from address for the error emails will be
## mesh_agent@[hostname]. However, if you'd like to specify a different email
## address, you can do so here.
#from_address admin@host.site.edu
## One or more 'admin_email' options can be included to specify email addresses
## to send errors to. These email addresses will receive all errors (including
## parsing errors). This is in addition to the emails that will be sent to the
## various affected administrators (e.g. the mesh administrator or the site
## administrator).
#admin_email admin1@site.edu
#admin_email admin2@site.edu
## The 'skip_redundant_tests' can be used so that if the meshes end up creating
## multiple tests between hosts with the exact same test parameters, it will
## only setup the hosts to only run one test. If you enable this, you won't see
## the skipped tests in the Toolkit GUI
#skip_redundant_tests 1
## The file that stores a UUID included in every pScheduler task. This UUID is used to
## track tasks that this agent has created.
#client_uuid_file /var/lib/perfsonar/meshconfig/client_uuid
## The URL of the pScheduler instance to use as the 'assist' server to determine where
## to schedule tasks. Generally this is a local pScheduler instance that will be the lead
## participant on many of the tasks submitted, though technically speaking it is not required
## to be a participant in any task
#pscheduler_url https://127.0.0.1/pscheduler
## The file where the agent tracks which pScheduler servers it has previously submitted tasks
#pscheduler_tracker_file /var/lib/perfsonar/meshconfig/psc_tracker
## The number of times to try to connect to the local pScheduler when it fails after
# only waiting check_config_interval as opposed to the generally much larger check_interval.
#pscheduler_fail_attempts 5
## The minimum lifetime in seconds to set for a new test created. The greater of this value and
## that calculated from task_min_runs will be used to determine end time of the test. It is recommended
## to set this to a reasonable value as it greatly reduces the cost of an orphaned test
##(i.e. a test you create will live on if your host goes away)
#task_min_ttl 86400
## The minimum number of times a task should run before expiring. If you have a test
## scheduler to run once an hour and set this value to 2, then the minimum end time will
## be determined to be the greater of task_min_ttl and 2 hours.
#task_min_runs 2
## The percentage of check_interval after the next scheduled check that a task's end time
## must be below before you create a new task. For example if this is .25 and
## check_interval is 1 hour, than a task's end time must be 75 minutes (1.25 * 1 hour) in
## the future or else a new task will be created where the start time is the end time of
## the old.
#task_renewal_fudge_factor .25