Author: buildbot
Date: Wed Dec 19 19:16:46 2012
New Revision: 843141

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    
websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 19 19:16:46 2012
@@ -1 +1 @@
-1424040
+1424041

Modified: 
websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html
==============================================================================
--- 
websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html
 (original)
+++ 
websites/staging/vcl/trunk/content/docs/authorization/administrationconcepts.html
 Wed Dec 19 19:16:46 2012
@@ -82,37 +82,29 @@
 <div class="toc">
 <ul>
 <li><a href="#resources">Resources</a><ul>
-<li><a href="#imagesenvironments">Images/Environments</a><ul>
+<li><a href="#imagesenvironments">Images/Environments</a></li>
 <li><a href="#computers">Computers</a></li>
 <li><a href="#schedules">Schedules</a></li>
 </ul>
 </li>
-</ul>
-</li>
 <li><a href="#groups">Groups</a><ul>
-<li><a href="#user-groups">User Groups</a><ul>
+<li><a href="#user-groups">User Groups</a></li>
 <li><a href="#resource-groups">Resource Groups</a></li>
 </ul>
 </li>
-</ul>
-</li>
 <li><a href="#resource-management">Resource Management</a><ul>
-<li><a href="#resource-grouping">Resource Grouping</a><ul>
+<li><a href="#resource-grouping">Resource Grouping</a></li>
 <li><a href="#resource-mapping">Resource Mapping</a></li>
 </ul>
 </li>
-</ul>
-</li>
 <li><a href="#privileges">Privileges</a><ul>
-<li><a href="#user-permissions">User Permissions</a><ul>
+<li><a href="#user-permissions">User Permissions</a></li>
 <li><a href="#resource-attributes">Resource Attributes</a></li>
 </ul>
 </li>
 </ul>
-</li>
-</ul>
 </div>
-<h1 id="resources">Resources</h1>
+<h2 id="resources">Resources</h2>
 <p>VCL manages sets of resources. There are four types of resources: images, 
computers, 
 management nodes, and schedules. Each of these resources types are described 
below.</p>
 <h3 id="imagesenvironments">Images/Environments</h3>
@@ -144,7 +136,7 @@ computers to be managed by another syste
 computers in a traditional university computing lab may be available through 
VCL when 
 the lab is physically closed, but you wouldn't want to be assigning remote 
users to 
 those computers when the lab is open.</p>
-<h1 id="groups">Groups</h1>
+<h2 id="groups">Groups</h2>
 <p>Users and resources are placed into groups to make management of them 
easier.</p>
 <h3 id="user-groups">User Groups</h3>
 <p>There are two types of user groups in VCL: those whose membership is 
manually managed 
@@ -158,7 +150,7 @@ management node, or schedule. The resour
 resources and also to allow VCL to know which resources can be used in 
relation to other 
 resources. One example of this is to configure which images can be deployed to 
which 
 computers. Another example is which management nodes can manage which 
computers.</p>
-<h1 id="resource-management">Resource Management</h1>
+<h2 id="resource-management">Resource Management</h2>
 <p>VCL needs to know how resources related to one another. This is done by 
adding the 
 resources to a resource group, and then mapping one type of resource group to 
another.</p>
 <h3 id="resource-grouping">Resource Grouping</h3>
@@ -183,7 +175,7 @@ of hardware to an incompatible type of h
 mapping is to partition off parts of your hardware. For example, if you had a 
set of 
 users purchase their own hardware to be managed by VCL, you could map only 
their image 
 groups to their computer groups.</p>
-<h1 id="privileges">Privileges</h1>
+<h2 id="privileges">Privileges</h2>
 <p>Users are granted access to parts of the VCL web site and to resources 
through the 
 Privilege tree. User permissions and resource attributes can both be cascaded 
down 
 from one node to all of its children. Additionally, cascaded user permissions 
and 


Reply via email to