You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@vcl.apache.org by jf...@apache.org on 2013/02/11 19:04:02 UTC

svn commit: r1444908 - /vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext

Author: jfthomps
Date: Mon Feb 11 18:04:02 2013
New Revision: 1444908

URL: http://svn.apache.org/r1444908
Log:
added bit about owning user group for resource groups

Modified:
    vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext

Modified: vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext?rev=1444908&r1=1444907&r2=1444908&view=diff
==============================================================================
--- vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext (original)
+++ vcl/site/trunk/content/docs/authorization/administrationconcepts.mdtext Mon Feb 11 18:04:02 2013
@@ -81,6 +81,9 @@ resources and also to allow VCL to know 
 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.
 
+Resource Groups also have an *Owning User Group* associated with them. The owning 
+user group has administrative access to the group to manage the group within VCL. 
+
 ##Resource Management
 
 VCL needs to know how resources related to one another. This is done by adding the