Author: buildbot
Date: Mon Feb 11 18:04:07 2013
New Revision: 850263
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 Mon Feb 11 18:04:07 2013
@@ -1 +1 @@
-1443491
+1444908
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
Mon Feb 11 18:04:07 2013
@@ -150,6 +150,8 @@ 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>
+<p>Resource Groups also have an <em>Owning User Group</em> associated with
them. The owning
+user group has administrative access to the group to manage the group within
VCL. </p>
<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>
