svn commit: r826871 - in /websites/staging/vcl/trunk/content: ./ configsystem.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jul 24 21:27:46 2012
New Revision: 826871

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/configsystem.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul 24 21:27:46 2012
@@ -1 +1 @@
-1365290
+1365300

Modified: websites/staging/vcl/trunk/content/configsystem.html
==============================================================================
--- websites/staging/vcl/trunk/content/configsystem.html (original)
+++ websites/staging/vcl/trunk/content/configsystem.html Tue Jul 24 21:27:46 2012
@@ -75,6 +75,41 @@
     <h1 class="title"></h1>
     <h1 id="new-configuration-system">New Configuration System</h1>
 <p>This page describes a new configuration system that will be added to VCL that can be used to dynamically configure deployed systems.</p>
+<h2 id="database-schema">Database schema</h2>
+<p>config:</p>
+<ul>
+<li>id - id of record</li>
+<li>name - name of record</li>
+<li>ownerid - owner of this record (reference to user.id)</li>
+<li>configtypeid - type of record (reference to configtype.id)</li>
+<li>data - any data associated with this (ex. puppet manifest)</li>
+<li>optional - 0/1 - when this config is mapped to something, can the user specify to apply it or not</li>
+</ul>
+<p>configtype:</p>
+<ul>
+<li>id - id of record</li>
+<li>name - name of record</li>
+<li>moduleid - id of module that handles this type of record (reference to module.id)</li>
+</ul>
+<p>initial types: puppet, subimage, shellcommand, perlfunction</p>
+<p>configvariable:</p>
+<ul>
+<li>id - id of record</li>
+<li>name - name of record</li>
+<li>configid - config this is associated with (reference to config.id)</li>
+<li>value - default value of this variable</li>
+<li>required - 0/1 - when mapped to something, is this variable always applied</li>
+<li>ask - 0/1 - will the user be prompted for a value for this variable, or will the default value always be used</li>
+<li>key - string in config.data to replace with the value of this variable</li>
+<li>datatype - enum(int, string) - type of this variable so that the frontend knows how to validate it</li>
+</ul>
+<p>There are some initial, special names:
+ * subimage - used for clusters, specifies a subimage to be deployed
+ * min - used in conjunction with subimage to specify a minimum number of those subimages
+ * max - used in conjunction with subimage to specify a maximum number of those subimages
+ * runbefore - used to relate to other configs to specify that this should be run before the ones specified in 'value'
+ * runafter - used to relate to other configs to specify that this should be run after the ones specified in 'value'
+ * getdata - ??</p>
   </div>
   
   <div id="footer">