Mark Huang <mlhuang@cs.princeton.edu>
Copyright (C) 2006 The Trustees of Princeton University
-$Id$
-$URL$
-->
<!DOCTYPE configuration PUBLIC "-//PlanetLab Central//DTD PLC configuration//EN" "plc_config.dtd">
<description>The SSH private key used to access the root
account on your nodes.</description>
</variable>
+
+ </variablelist>
+ </category>
+
+ <category id="plc_flavour">
+ <name>Flavours</name>
+ <description>Defaults for nodes and slices contents.</description>
+
+ <variablelist>
+ <variable id="virt_map" type="string">
+ <value> f8,f12,f14,centos5,centos6:vs; default:lxc </value>
+ <description>Allows to compute a virtualization mechanism
+ from an fcdistro. Starting with 5.2 MyPLC has support for
+ either 'vs' or 'lxc', and this gives a correspondance from
+ the node's fcdistro to the right virtualization mechanism.
+ This information is essentially used by the BootManager for
+ getting the installation phase right like e.g. when
+ partitioning disks, and not to figure the contents of the
+ nodeimage that depend only on fcdistro, pldistro and of
+ course arch. This can be overridden by setting the vrt tag
+ on that particular node. </description>
+ </variable>
+
+ <variable id="node_arch" type="string">
+ <name>arch for nodes</name>
+ <value>@ARCH@</value>
+ <description>The default 'arch' to use when installing nodes.
+ This is offered mostly for consistency with the rest of the
+ PLC_FLAVOUR category, but does not have much of a practical
+ interest. In any case, you need to have the corresponding
+ bootstrapfs images available for nodes.</description>
+ </variable>
+
+ <variable id="node_fcdistro" type="string">
+ <name>fcdistro for nodes</name>
+ <value>@FCDISTRO@</value>
+ <description>THIS CURRENTLY HAS NO EFFECT.
+ The default 'fcdistro' to use when installing
+ nodes.You need to have the corresponding bootstrapfs images
+ available for nodes. THIS CURRENTLY HAS NO EFFECT.</description>
+ </variable>
+
+ <variable id="node_pldistro" type="string">
+ <name>pldistro for nodes</name>
+ <value>@PLDISTRO@</value>
+ <description>The default 'pldistro' to use when installing
+ nodes. You need to have the corresponding bootstrapfs
+ images available for nodes.</description>
+ </variable>
+
+ <variable id="slice_arch" type="string">
+ <name>arch for slivers</name>
+ <value>@ARCH@</value>
+ <description>The default 'arch' to use for slivers. This is
+ useful if you have heterogeneous nodes (i686 and x86_64),
+ but want slivers to be homogeneous. You need to have the
+ corresponding vserver variant rpm available for
+ nodes.</description>
+ </variable>
+
+ <variable id="slice_fcdistro" type="string">
+ <name>fcdistro for slivers</name>
+ <value>@FCDISTRO@</value>
+ <description>The default 'fcdistro' to use for creating
+ slivers. You need to have the corresponding vserver variant
+ rpm available for nodes.</description>
+ </variable>
+
+ <variable id="slice_pldistro" type="string">
+ <name>pldistro for slivers</name>
+ <value>@PLDISTRO@</value>
+ <description>The default 'pldistro' to use for creating
+ slivers. You need to have the corresponding vserver variant
+ rpm available for nodes.</description>
+ </variable>
+
</variablelist>
</category>
</variablelist>
</category>
+ <category id="plc_hosts">
+ <name>/etc/hosts</name>
+ <description>MyPLC can setup /etc/hosts with the hostnames and
+ IP addresses specified for *_NAME and *_IP, or look up the IP
+ addresses if they are not specified in this configuration.
+ </description>
+
+ <variablelist>
+ <variable id="enabled" type="boolean">
+ <name>Enable /etc/hosts configuration</name>
+ <value>true</value>
+ <description>Let PLC manage /etc/hosts</description>
+ </variable>
+ </variablelist>
+ </category>
+
<category id="plc_mail">
<name>Mail</name>
<description>Many maintenance scripts, as well as the API and
</variablelist>
</category>
+ <category id="plc_ratelimit">
+ <name>Planetlab Ratelimit Settings</name>
+ <description>Planetlab Ratelimit Settings</description>
+ <variablelist>
+ <variable id="enabled" type="bolean">
+ <name>Enable Ratelimit</name>
+ <value>false</value>
+ <description>Enable Ratelimit for sites</description>
+ </variable>
+ </variablelist>
+ </category>
+
+ <category id="plc_omf">
+ <name>Planetlab - OMF Integration</name>
+ <description>Planetlab - OMF integration</description>
+ <variablelist>
+ <variable id="enabled" type="boolean">
+ <name>OMF integration</name>
+ <value>false</value>
+ <description>Enable OMF integration.</description>
+ </variable>
+
+ <!-- xmpp server configuration -->
+ <variable id="xmpp_server" type="string">
+ <name>XMPP server</name>
+ <value>localhost.localdomain</value>
+ <description>The fully qualified hostname of the XMPP server.</description>
+ </variable>
+
+ </variablelist>
+ </category>
+
+ <category id="plc_reservation">
+ <name> Reservable Nodes</name>
+ <description> Settings related to reservable nodes </description>
+
+ <variablelist>
+ <variable id="granularity" type="int">
+ <name>Lease granularity</name>
+ <value>3600</value>
+ <description>The smallest timeslot that can be allocated to
+ a node. All leases will be rounded to this granularity, so
+ e.g. if you set 3600 all leases will start and stop at round
+ hours.</description>
+ </variable>
+ </variablelist>
+ </category>
<category id="plc_planetflow">
<name>PlanetFlow Service Configuration</name>
</variable>
</variablelist>
</category>
+
<category id="plc_monitor">
<name>Monitoring Service</name>
<description>The Monitor service that tracks node availablity and repair.</description>
<value>support</value>
<description>All messages from Monitor will be copied to this address.</description>
</variable>
+ <variable id="dbhost" type="hostname">
+ <name>Database Hostname</name>
+ <value>localhost</value>
+ <description>The hostname for the monitor database.</description>
+ </variable>
+ <variable id="dbuser" type="string">
+ <name>Database User</name>
+ <value>monitoruser</value>
+ <description>The username for connecting to the monitor database.</description>
+ </variable>
+ <variable id="dbname" type="string">
+ <name>Database Name</name>
+ <value>monitor</value>
+ <description>Name of monitor database.</description>
+ </variable>
<variable id="dbpassword" type="password">
<name>Database Password</name>
<value></value>
</variable>
</variablelist>
</category>
+
+ <category id="myslice">
+ <name>MySlice</name>
+ <description>MySlice configuration parameters</description>
+ <variablelist>
+ <variable id="comon_url" type="string">
+ <name>comon</name>
+ <value></value>
+ <description>The address of the CoMon url that provides information for this PLC's nodes (if not the default http://comon.cs.princeton.edu/)</description>
+ </variable>
+ <variable id="comon_available" type="boolean">
+ <name>comon</name>
+ <value>false</value>
+ <description>True, if comon data are available for this PLC's nodes</description>
+ </variable>
+ <variable id="tophat_available" type="boolean">
+ <name>tophat</name>
+ <value>false</value>
+ <description>True, if tophat data are available for this PLC's nodes</description>
+ </variable>
+ </variablelist>
+ </category>
+
+ <category id="plc_vsys">
+ <name>vsys</name>
+ <description>Default values for the vsys tag</description>
+ <variablelist>
+ <variable id="defaults" type="string">
+ <name>vsys tags set by default</name>
+ <value> </value>
+ <description>Comma-separated list of vsys script names that all newly created slices will have as their vsys tags. For older slices, see the check-vsys-defaults.py script as part of the myplc package</description>
+ </variable>
+ </variablelist>
+ </category>
</variables>
<comps>