3-fold nodefamily now has fcdistro as well
[myplc.git] / default_config.xml
index 5214886..ae4f5e1 100644 (file)
@@ -7,6 +7,7 @@ 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">
@@ -118,6 +119,67 @@ $Id$
       </variablelist>
     </category>
 
+    <category id="plc_flavour">
+      <name>Flavours</name>
+      <description>Defaults for nodes and slices contents.</description>
+      
+      <variablelist>
+       <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>
+
     <category id="plc_net">
       <name>Network</name>
       <description>Network environment.</description>
@@ -160,6 +222,22 @@ $Id$
       </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
@@ -606,6 +684,32 @@ $Id$
           <description>The password to use when accessing the
           database, Monitor user account in the local PLC.</description>
         </variable>
+
+           <variable id="ssl_key" type="file">
+                 <name>SSL Private Key</name>
+                 <value>/etc/planetlab/monitor_ssl.key</value>
+                 <description>The SSL private key to use for encrypting HTTPS
+                 traffic.</description>
+               </variable>
+
+               <variable id="ssl_crt" type="file">
+                 <name>SSL Public Certificate</name>
+                 <value>/etc/planetlab/monitor_ssl.crt</value>
+                 <description>The corresponding SSL public certificate for
+                 the HTTP server. By default, this certificate is
+                 self-signed. You may replace the certificate later with one
+                 signed by a root CA.</description>
+               </variable>
+
+               <variable id="ca_ssl_crt" type="file">
+                 <name>Root CA SSL Public Certificate</name>
+                 <value>/etc/planetlab/monitor_ca_ssl.crt</value>
+                 <description>The certificate of the root CA, if any, that
+                 signed your server certificate. If your server certificate is
+                 self-signed, then this file is the same as your server
+                 certificate.</description>
+               </variable>
+
       </variablelist>
     </category>
     <category id="plc_rt">
@@ -627,11 +731,16 @@ $Id$
           <value/>
           <description>The IP address of the RT server.</description>
         </variable>
+        <variable id="cc_address" type="email">
+          <name>CC Email Address</name>
+          <value>root+cclist@localhost.localdomain</value>
+          <description>All messages to and from PLCRT will be copied to this address.</description>
+        </variable>
         <variable id="web_user" type="string">
           <name>root</name>
           <value>root</value>
           <description>Username of a privileged user in RT who can create
-                 tickets in the queue named PLC_MONITOR_RT_QUEUE.</description>
+                 tickets for any RT Queue.</description>
         </variable>
         <variable id="web_password" type="password">
           <name>password</name>