Author: buildbot
Date: Wed Dec 19 19:15:45 2012
New Revision: 843140
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:15:45 2012
@@ -1 +1 @@
-1424039
+1424040
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:15:45 2012
@@ -82,32 +82,40 @@
<div class="toc">
<ul>
<li><a href="#resources">Resources</a><ul>
-<li><a href="#imagesenvironments">Images/Environments</a></li>
+<li><a href="#imagesenvironments">Images/Environments</a><ul>
<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></li>
+<li><a href="#user-groups">User Groups</a><ul>
<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></li>
+<li><a href="#resource-grouping">Resource Grouping</a><ul>
<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></li>
+<li><a href="#user-permissions">User Permissions</a><ul>
<li><a href="#resource-attributes">Resource Attributes</a></li>
</ul>
</li>
</ul>
+</li>
+</ul>
</div>
<h1 id="resources">Resources</h1>
<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>
-<h2 id="imagesenvironments">Images/Environments</h2>
+<h3 id="imagesenvironments">Images/Environments</h3>
<p>An image is a collection of software that is installed on an operating
system. For the
most part, these images can be deployed, used, modified, and saved (captured).
However,
there are some cases where only some of the operations could be proformed on
an image.
@@ -121,7 +129,7 @@ VMWare can be used to provision virtuali
sturctured in a modularized way such that it is easy to add support for other
provisioning technologies. We plan on adding support for other hypervisor
technologies
in the near future.</p>
-<h2 id="computers">Computers</h2>
+<h3 id="computers">Computers</h3>
<p>Images are deployed on to computers. VCL needs to know about all of the
computers it
will be managing. Entries for both physical computers and Virtual Machines
(some people
call these "slots") need to be created in VCL for it to be able to manage them.
@@ -129,7 +137,7 @@ Management Nodes</p>
<p>Management nodes run the VCL backend code (vcld) that is responsible for
deploying
images to computers when users make reservations for images. Each management
node can
manage a mix of physical and virtual computers.</p>
-<h2 id="schedules">Schedules</h2>
+<h3 id="schedules">Schedules</h3>
<p>Each computer must have a schedule associated with it. Schedules provide a
way to
define what times during a week a computer is available through VCL. This
allows for
computers to be managed by another system during certain parts of a week. For
example,
@@ -138,13 +146,13 @@ the lab is physically closed, but you wo
those computers when the lab is open.</p>
<h1 id="groups">Groups</h1>
<p>Users and resources are placed into groups to make management of them
easier.</p>
-<h2 id="user-groups">User Groups</h2>
+<h3 id="user-groups">User Groups</h3>
<p>There are two types of user groups in VCL: those whose membership is
manually managed
through the web frontend or XML RPC API, and those whose membership is
automatically
managed by mirroring user groups in an LDAP system. Each user group has
certain attributes
associated with it. There are various places within VCL that user groups can
be used,
with the primary place being granting access to resources in the privilege
tree.</p>
-<h2 id="resource-groups">Resource Groups</h2>
+<h3 id="resource-groups">Resource Groups</h3>
<p>Each resource group has a type associated with it which can be one of
image, computer,
management node, or schedule. The resource groups are used to grant users
access to
resources and also to allow VCL to know which resources can be used in
relation to other
@@ -153,7 +161,7 @@ computers. Another example is which mana
<h1 id="resource-management">Resource Management</h1>
<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>
-<h2 id="resource-grouping">Resource Grouping</h2>
+<h3 id="resource-grouping">Resource Grouping</h3>
<p>Resource groups can contain any number of resources. Each resource group
has a resource
type associated with it. Only resources matching that type can be added to the
group.
Also, it is important to note that when working with computers, physical and
virtual
@@ -161,7 +169,7 @@ computers should not be combined into th
to assign a physical image to a virtual computer or vice versa. Some upcoming
changes
to the code will remove this restriction, but for now, keep this restriction
in mind
while grouping computers.</p>
-<h2 id="resource-mapping">Resource Mapping</h2>
+<h3 id="resource-mapping">Resource Mapping</h3>
<p>After you have grouped your resources, you need to map them together. Image
groups are
mapped to computer groups, and management node groups are mapped to computer
groups.
Schedule groups are not mapped to anything (instead, every computer is
directly assigned
@@ -181,7 +189,7 @@ Privilege tree. User permissions and res
from one node to all of its children. Additionally, cascaded user permissions
and
resource attributes can be blocked at a node so that they do not cascade down
to that
node or any of its children.</p>
-<h2 id="user-permissions">User Permissions</h2>
+<h3 id="user-permissions">User Permissions</h3>
<p>There are nine user permissions that can be granted to users. They can be
granted
to users directly or to user groups.</p>
<ul>
@@ -202,7 +210,7 @@ groups with administer or manageGroup gr
<li><strong>userGrant</strong> - grants users access to control what user
permissions are assigned at
the same node</li>
</ul>
-<h2 id="resource-attributes">Resource Attributes</h2>
+<h3 id="resource-attributes">Resource Attributes</h3>
<p>There are three resource attributes that can be assigned to a resource
group at any
node in the privilege tree.</p>
<ul>
