1 <?xml version="1.0" encoding="utf-8"?>
4 Default PLC configuration file
6 Mark Huang <mlhuang@cs.princeton.edu>
7 Copyright (C) 2006 The Trustees of Princeton University
12 <!DOCTYPE configuration PUBLIC "-//PlanetLab Central//DTD PLC configuration//EN" "plc_config.dtd">
18 <description>Basic system variables. Be sure that the values of
19 these variables are the same across all machines in your
20 installation.</description>
23 <variable id="name" type="string">
25 <value>PlanetLab Test</value>
26 <description>The name of this PLC installation. It is used in
27 the name of the default system site (e.g., PlanetLab Central)
28 and in the names of various administrative entities (e.g.,
29 PlanetLab Support).</description>
32 <variable id="slice_prefix" type="string">
33 <name>Slice Prefix</name>
35 <description>The abbreviated name of this PLC
36 installation. It is used as the prefix for system slices
37 (e.g., pl_conf). Warning: Currently, this variable should
38 not be changed.</description>
41 <variable id="root_user" type="email">
42 <name>Root Account</name>
43 <value>root@localhost.localdomain</value>
44 <description>The name of the initial administrative
45 account. We recommend that this account be used only to create
46 additional accounts associated with real
47 administrators, then disabled.</description>
50 <variable id="root_password" type="password">
51 <name>Root Password</name>
53 <description>The password of the initial administrative
54 account. Also the password of the root account on the Boot
58 <!-- The following are not actually meant to be configurable
59 as variables. The web interface should allow the file to
60 be downloaded, or its contents replaced by a file upload,
61 but the actual <value> shouldn't need to be changed. -->
63 <variable id="root_ssh_key_pub" type="file">
64 <name>Root SSH Public Key</name>
65 <value>/etc/planetlab/root_ssh_key.pub</value>
66 <description>The SSH public key used to access the root
67 account on your nodes.</description>
70 <variable id="root_ssh_key" type="file">
71 <name>Root SSH Private Key</name>
72 <value>/etc/planetlab/root_ssh_key.rsa</value>
73 <description>The SSH private key used to access the root
74 account on your nodes.</description>
77 <variable id="debug_ssh_key_pub" type="file">
78 <name>Debug SSH Public Key</name>
79 <value>/etc/planetlab/debug_ssh_key.pub</value>
80 <description>The SSH public key used to access the root
81 account on your nodes when they are in Debug mode.</description>
84 <variable id="debug_ssh_key" type="file">
85 <name>Debug SSH Private Key</name>
86 <value>/etc/planetlab/debug_ssh_key.rsa</value>
87 <description>The SSH private key used to access the root
88 account on your nodes when they are in Debug mode.</description>
91 <variable id="root_gpg_key_pub" type="file">
92 <name>Root GPG Public Keyring</name>
93 <value>/etc/planetlab/pubring.gpg</value>
94 <description>The GPG public keyring used to sign the Boot
95 Manager and all node packages.</description>
98 <variable id="root_gpg_key" type="file">
99 <name>Root GPG Private Keyring</name>
100 <value>/etc/planetlab/secring.gpg</value>
101 <description>The SSH private key used to access the root
102 account on your nodes.</description>
107 <category id="plc_net">
109 <description>Network environment.</description>
112 <variable id="dns1" type="ip">
113 <name>Primary DNS Server</name>
114 <value>127.0.0.1</value>
115 <description>Primary DNS server address.</description>
118 <variable id="dns2" type="ip">
119 <name>Secondary DNS Server</name>
121 <description>Secondary DNS server address.</description>
126 <category id="plc_dns">
128 <description>MyPLC can provide forward DNS resolution for itself
129 and for its nodes. To enable resolution for MyPLC itself, set
130 the Primary DNS Server address to 127.0.0.1 and provide external
131 IP addresses for the database, API, web, and boot servers
132 below. To enable resolution for nodes, use the external IP
133 address of this machine as the primary DNS server address for
134 each node.</description>
137 <variable id="enabled" type="boolean">
138 <name>Enable DNS</name>
140 <description>Enable the internal DNS server. The server does
141 not provide reverse resolution and is not a production
142 quality or scalable DNS solution. Use the internal DNS
143 server only for small deployments or for
144 testing.</description>
149 <category id="plc_mail">
151 <description>Many maintenance scripts, as well as the API and
152 web site themselves, send e-mail notifications and
153 warnings.</description>
156 <variable id="enabled" type="boolean">
157 <name>Enable Mail</name>
159 <description>Set to false to suppress all e-mail notifications
160 and warnings.</description>
163 <variable id="support_address" type="email">
164 <name>Support Address</name>
165 <value>root+support@localhost.localdomain</value>
166 <description>This address is used for support
167 requests. Support requests may include traffic complaints,
168 security incident reporting, web site malfunctions, and
169 general requests for information. We recommend that the
170 address be aliased to a ticketing system such as Request
171 Tracker.</description>
174 <variable id="boot_address" type="email">
175 <name>Boot Messages Address</name>
176 <value>root+install-msgs@localhost.localdomain</value>
177 <description>The API will notify this address when a problem
178 occurs during node installation or boot.</description>
181 <variable id="mom_list_address" type="email">
182 <name>Mom List Address</name>
183 <value>root+mom@localhost.localdomain</value>
184 <description>This address is used by operations staff
185 to monitor Mom (formerly pl_mom) messages indicating
186 excessive BW or memory usage by a slice. Mom messages sent
187 to slices will be cc'ed to this list so as not to clog
188 the Support Address list.</description>
191 <variable id="slice_address" type="email">
192 <name>Slice Address</name>
193 <value>root+SLICE@localhost.localdomain</value>
194 <description>This address template is used for sending
195 e-mail notifications to slices. SLICE will be replaced with
196 the name of the slice.</description>
201 <category id="plc_db">
202 <name>Database Server</name>
203 <description>Database server definitions.</description>
206 <variable id="enabled" type="boolean">
209 <description>Enable the database server on this
210 machine.</description>
213 <variable id="type" type="string">
215 <value>postgresql</value>
216 <description>The type of database server. Currently, only
217 postgresql is supported.</description>
220 <variable id="host" type="hostname">
221 <name>Hostname</name>
222 <value>localhost.localdomain</value>
223 <description>The fully qualified hostname of the database
224 server.</description>
227 <variable id="ip" type="ip">
228 <name>IP Address</name>
230 <description>The IP address of the database server, if not
231 resolvable.</description>
234 <variable id="port" type="int">
237 <description>The TCP port number through which the database
238 server should be accessed.</description>
241 <variable id="name" type="string">
242 <name>Database Name</name>
243 <value>planetlab4</value>
244 <description>The name of the database to access.</description>
247 <variable id="user" type="string">
248 <name>Database Username</name>
249 <value>pgsqluser</value>
250 <description>The username to use when accessing the
251 database.</description>
254 <variable id="password" type="password">
255 <name>Database Password</name>
257 <description>The password to use when accessing the
258 database. If left blank, one will be
259 generated.</description>
264 <category id="plc_api">
265 <name>API Server</name>
266 <description>API (XML-RPC) server definitions.</description>
269 <variable id="enabled" type="boolean">
272 <description>Enable the API server on this
273 machine.</description>
276 <variable id="debug" type="boolean">
279 <description>Enable verbose API debugging. Do not enable on
280 a production system!</description>
283 <variable id="host" type="hostname">
284 <name>Hostname</name>
285 <value>localhost.localdomain</value>
286 <description>The fully qualified hostname of the API
287 server.</description>
290 <variable id="ip" type="ip">
291 <name>IP Address</name>
293 <description>The IP address of the API server, if not
294 resolvable.</description>
297 <variable id="ipod_subnet" type="ip">
298 <name>IP Subnet</name>
299 <value>127.0.0.1</value>
300 <description>The IP Subnet for all API servers.
301 Used to identify IPoD packet senders.</description>
304 <variable id="ipod_mask" type="ip">
306 <value>255.255.255.255</value>
307 <description>The IP Mask that should be applied to incoming
308 packets to match the IP Subnet for IPoD packets.</description>
311 <variable id="port" type="int">
314 <description>The TCP port number through which the API
315 should be accessed.</description>
318 <variable id="path" type="string">
320 <value>/PLCAPI/</value>
321 <description>The base path of the API URL.</description>
324 <variable id="maintenance_user" type="string">
325 <name>Maintenance User</name>
326 <value>maint@localhost.localdomain</value>
327 <description>The username of the maintenance account. This
328 account is used by local scripts that perform automated
329 tasks, and cannot be used for normal logins.</description>
332 <variable id="maintenance_password" type="password">
333 <name>Maintenance Password</name>
335 <description>The password of the maintenance account. If
336 left blank, one will be generated. We recommend that the
337 password be changed periodically.</description>
340 <variable id="maintenance_sources" type="hostname">
341 <name>Authorized Hosts</name>
343 <description>A space-separated list of IP addresses allowed
344 to access the API through the maintenance account. The value
345 of this variable is set automatically to allow only the API,
346 web, and boot servers, and should not be
347 changed.</description>
350 <!-- The following are not actually meant to be configurable
351 as variables. The web interface should allow the file to
352 be downloaded, or its contents replaced by a file upload,
353 but the actual <value> shouldn't need to be changed. -->
355 <variable id="ssl_key" type="file">
356 <name>SSL Private Key</name>
357 <value>/etc/planetlab/api_ssl.key</value>
358 <description>The SSL private key to use for encrypting HTTPS
359 traffic. If non-existent, one will be
360 generated.</description>
363 <variable id="ssl_crt" type="file">
364 <name>SSL Public Certificate</name>
365 <value>/etc/planetlab/api_ssl.crt</value>
366 <description>The corresponding SSL public certificate. By
367 default, this certificate is self-signed. You may replace
368 the certificate later with one signed by a root
372 <variable id="ca_ssl_crt" type="file">
373 <name>Root CA SSL Public Certificate</name>
374 <value>/etc/planetlab/api_ca_ssl.crt</value>
375 <description>The certificate of the root CA, if any, that
376 signed your server certificate. If your server certificate is
377 self-signed, then this file is the same as your server
378 certificate.</description>
383 <category id="plc_www">
384 <name>Web Server</name>
385 <description>Web server definitions.</description>
388 <variable id="enabled" type="boolean">
391 <description>Enable the web server on this
392 machine.</description>
395 <variable id="debug" type="boolean">
398 <description>Enable debugging output on web pages. Do not
399 enable on a production system!</description>
402 <variable id="host" type="hostname">
403 <name>Hostname</name>
404 <value>localhost.localdomain</value>
405 <description>The fully qualified hostname of the web
406 server.</description>
409 <variable id="ip" type="ip">
410 <name>IP Address</name>
412 <description>The IP address of the web server, if not
413 resolvable.</description>
416 <variable id="port" type="int">
419 <description>The TCP port number through which the
420 unprotected portions of the web site should be
421 accessed.</description>
424 <variable id="ssl_port" type="int">
425 <name>SSL Port</name>
427 <description>The TCP port number through which the protected
428 portions of the web site should be accessed.</description>
431 <!-- The following are not actually meant to be configurable
432 as variables. The web interface should allow the file to
433 be downloaded, or its contents replaced by a file upload,
434 but the actual <value> shouldn't need to be changed. -->
436 <variable id="ssl_key" type="file">
437 <name>SSL Private Key</name>
438 <value>/etc/planetlab/www_ssl.key</value>
439 <description>The SSL private key to use for encrypting HTTPS
440 traffic. If non-existent, one will be
441 generated.</description>
444 <variable id="ssl_crt" type="file">
445 <name>SSL Public Certificate</name>
446 <value>/etc/planetlab/www_ssl.crt</value>
447 <description>The corresponding SSL public certificate for
448 the HTTP server. By default, this certificate is
449 self-signed. You may replace the certificate later with one
450 signed by a root CA.</description>
453 <variable id="ca_ssl_crt" type="file">
454 <name>Root CA SSL Public Certificate</name>
455 <value>/etc/planetlab/www_ca_ssl.crt</value>
456 <description>The certificate of the root CA, if any, that
457 signed your server certificate. If your server certificate is
458 self-signed, then this file is the same as your server
459 certificate.</description>
464 <category id="plc_boot">
465 <name>Boot Server</name>
466 <description>Boot server definitions. Multiple boot servers
467 may be brought up for load balancing, but we recommend that a
468 single DNS round-robin system be implemented so that the
469 following variables are the same across all of
473 <variable id="enabled" type="boolean">
476 <description>Enable the boot server on this
477 machine.</description>
480 <variable id="host" type="hostname">
481 <name>Hostname</name>
482 <value>localhost.localdomain</value>
483 <description>The fully qualified hostname of the boot
484 server.</description>
487 <variable id="ip" type="ip">
488 <name>IP Address</name>
490 <description>The IP address of the boot server, if not
491 resolvable.</description>
494 <variable id="port" type="int">
497 <description>The TCP port number through which the
498 unprotected portions of the boot server should be
499 accessed.</description>
502 <variable id="ssl_port" type="int">
503 <name>SSL Port</name>
505 <description>The TCP port number through which the protected
506 portions of the boot server should be
507 accessed.</description>
510 <!-- The following are not actually meant to be configurable
511 as variables. The web interface should allow the file to
512 be downloaded, or its contents replaced by a file upload,
513 but the actual <value> shouldn't need to be changed. -->
515 <variable id="ssl_key" type="file">
516 <name>SSL Private Key</name>
517 <value>/etc/planetlab/boot_ssl.key</value>
518 <description>The SSL private key to use for encrypting HTTPS
519 traffic.</description>
522 <variable id="ssl_crt" type="file">
523 <name>SSL Public Certificate</name>
524 <value>/etc/planetlab/boot_ssl.crt</value>
525 <description>The corresponding SSL public certificate for
526 the HTTP server. By default, this certificate is
527 self-signed. You may replace the certificate later with one
528 signed by a root CA.</description>
531 <variable id="ca_ssl_crt" type="file">
532 <name>Root CA SSL Public Certificate</name>
533 <value>/etc/planetlab/boot_ca_ssl.crt</value>
534 <description>The certificate of the root CA, if any, that
535 signed your server certificate. If your server certificate is
536 self-signed, then this file is the same as your server
537 certificate.</description>
543 <category id="plc_planetflow">
544 <name>PlanetFlow Service Configuration</name>
545 <description>Planetflow service definitions used in the netflow slice. </description>
548 <variable id="host" type="hostname">
549 <name>Hostname</name>
550 <value>localhost.localdomain</value>
551 <description>The fully qualified hostname of the boot
552 server.</description>
559 <!-- deprecated - not used anymore - use .lst files instead -->