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
|
Template: nws/debconf
Type: boolean
Default: true
_Description: Configure NWS using debconf?
There is several way to configure the NWS within Debian.
.
The first one is to use debconf, and let the scripts generate a NWS
configuration file. You can also choose to copy and adapt the file located
in /usr/share/doc/nws/nws.conf.example.gz
.
This second option may be preferable if you want to configure a large park
of hosts since this file is designed to be shared between hosts. It is
definitivly preferable for experts since some options cannot be accessed
from the debconf interface.
.
In any case, modifications to /etc/nws.conf will be preserved on upgrade
(using ucf).
Template: nws/run_nameserver
Type: boolean
Default: true
_Description: Run a NWS nameserver on this host?
In orfer to run, the Network Weather Service must contain one (and only
one) nameserver.
.
If you choose not to run the nameserver on this machine, you will be
prompted for the location of the nameserver to use.
Template: nws/run_memory
Type: boolean
Default: true
_Description: Run a NWS memory on this host?
In order to run, the Network Weather Service must contain one memory
server. You may run several memory servers, and one per cluster is usually a
good idea.
.
If you choose not to run any memory server on this machine, you will be
prompted for the location of the server to use.
Template: nws/nameserver
Type: string
_Description: Nameserver location:
Please give the location of the nameserver to use. Simply giving the name
of the host on which this server runs is enough. You can use the IP adress
instead of its name. If the server listen does not listen on the regular
port (8090), specify it after a colon.
.
Some example of valid values are: "bluehost", "192.168.0.1",
"fender.ucsb,edu", "bluehost:890".
Template: nws/memory
Type: string
_Description: Memory location:
Please give the location of the memory server to use. Simply giving the name
of the host on which this server runs is enough. You can use the IP adress
instead of its name. If the server listen does not listen on the regular
port (8060), specify it after a colon.
.
Some example of valid values are: "bluehost", "192.168.0.1",
"fender.ucsb,edu", "bluehost:860".
Template: nws/skills
Type: multiselect
_Choices: cpu, disk, memory, tcpConnect, tcpMessage
Default: cpu, memory
_Description: Monitors to use:
cpu: the fraction of CPU available to both newly-started and existing processes.
.
disk: the amount of space available on a disk.
.
memory: the amount of free memory available on the machine.
.
tcpConnect: the time requiered to establish a TCP connection.
.
tcpMessage: TCP bandwidth and latency. Only the clique leader needs to
specify this, the other members should not select this.
.
For more information, see the NWS userguide.
Template: nws/tcpConnect/members
Type: string
_Description: Members of this tcpConnect experiment:
Please give the list (space or comma separated) of all machines between
which you want to monitor the tcpConnect time.
.
Please do not list the host on which we are running currently.
Template: nws/tcpMessage/members
Type: string
_Description: Which machines should participate to this tcpMessage experiment ?
Please give the list (space or comma separated) of all machines between
which you want to monitor the tcp communication capacities.
.
Please do not list the host on which we are running currently.
|
