vcl-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r845507 [8/17] - in /websites/staging/vcl/trunk/content: ./ confluence_export/
Date Tue, 08 Jan 2013 16:38:17 GMT
Added: websites/staging/vcl/trunk/content/confluence_export/example---granting-two-sets-of-users-access-to-two-different-sets-of-images.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/example---granting-two-sets-of-users-access-to-two-different-sets-of-images.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/example---granting-two-sets-of-users-access-to-two-different-sets-of-images.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,205 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Example - Granting Two Sets of Users Access to Two Different Sets of Images</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Example - Granting Two Sets of Users Access to Two Different Sets of Images</h1>
+    <p>This page explains how to grant one groups of users access to one set of
+images, and another set of users access to a separate set of images.</p>
+<p>After looking over these steps, you can <a href="video---granting-two-sets-of-users-access-to-two-different-sets-of-images.html">watch a video</a>
+ of the steps being performed.</p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-1.CreateaUserGroupforEachSetofUsers"></a></p>
+<h2 id="1-create-a-user-group-for-each-set-of-users">1. Create a User Group for Each Set of Users</h2>
+<p>First, you need to create two user groups - one for each set of users.
+1. Click Manage Groups
+1. Under the User Groups section (at the top):
+1. # Enter a name for the group (it can include spaces)
+1. # (Optionally, if it shows up) select an affiliation for the group
+1. # Enter an owner of the group - probably yourself
+1. # Select a group allowed to edit the user group
+1. # The rest of the fields can be left as defaults
+1. Click Add
+1. Repeat the steps for the second group</p>
+<p>For the rest of the page, I'll call the groups <em>faculty</em> and <em>student</em></p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-2.AddUserstoEachGroup"></a></p>
+<h2 id="2-add-users-to-each-group">2. Add Users to Each Group</h2>
+<p>You need to add users to each of the groups.
+1. Click Manage Groups if you're not still on that page
+1. Click Edit next to the <em>faculty</em> group
+1. Enter a userid in the box next to the Add button (NOTE: if you are not
+using LDAP authentication, the users' accounts will already need to exist
+in VCL)
+1. Click Add
+1. Repeat for all users you wish to add to the <em>faculty</em> group
+1. Repeat these steps for the <em>student</em> group</p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-3.CreateanImageGroupforEachSetofImages"></a></p>
+<h2 id="3-create-an-image-group-for-each-set-of-images">3. Create an Image Group for Each Set of Images</h2>
+<p>Next, you need to create an image group for each set of images.
+1. Click Manage Groups if you're not still on that page
+1. Under the Resource Groups section (further down the page):
+1. # Select Image as the type
+1. # Enter a name for the group (it can contain spaces)
+1. # Select a user group that will own the resource group (this user group
+will have access to manage some aspects of the resource group)
+1. Click Add
+1. Repeat the steps for the second group</p>
+<p>For the rest of the page, I'll call the groups <em>faculty images</em> and
+<em>student images</em></p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-4.AddImagestoEachGroup"></a></p>
+<h2 id="4-add-images-to-each-group">4. Add Images to Each Group</h2>
+<p>Now, you need to add the desired images to each group.
+1. Click Manage Images
+1. Select the Edit Image Grouping radio button
+1. Click Submit
+1. Click the <em>By Group</em> tab
+1. Select <em>faculty images</em>
+1. Click Get Images
+1. Select any images you want to be available to the <em>faculty</em> user group in
+the list on the right (Ctrl+click to select multiple images)
+1. Click the &lt;-Add button
+1. Repeat steps for the <em>student images</em> group</p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-5.MaptheImageGroupstoComputerGroups"></a></p>
+<h2 id="5-map-the-image-groups-to-computer-groups">5. Map the Image Groups to Computer Groups</h2>
+<p>In order for VCL to know on which computers the images can run, you must
+map the image groups to computer groups. I'll assume you already have one
+or more computer groups that contain computers.
+1. Click Manage Images
+1. Select the Edit Image Mapping radio button
+1. Click Submit
+1. Select the <em>faculty images</em> group
+1. Click Get Computer Groups
+1. Select at least one computer group to map it to from the list on the
+right
+1. Click the &lt;-Add button
+1. Repeat for the <em>student images</em> group (NOTE: It is okay to map both image
+groups to the same computer group. That will not affect what images the
+users have access to.)</p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-6.CreateaTwoPrivilegeNodes"></a></p>
+<h2 id="6-create-a-two-privilege-nodes">6. Create a Two Privilege Nodes</h2>
+<p>Now, you need to create one node for each user group to separate their
+access.
+1. Click Privileges
+1. In the tree at the top of the page, click a node under which you'll
+create the two new nodes
+1. Click the Add Child button
+1. Enter a name for the new node (spaces are allowed)
+1. Click Create Child
+1. Repeat for the second node for the other user group</p>
+<p>I'll refer to these nodes as <em>faculty access</em> and <em>student access</em></p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-7.AssignRightsatEachNode"></a></p>
+<h2 id="7-assign-rights-at-each-node">7. Assign Rights at Each Node</h2>
+<p>Finally, you need to give each user group the <em>imageCheckOut</em> privilege at
+their respective nodes, and give each image group the <em>available</em> attribute
+at their respective nodes.
+1. Click on the <em>faculty access</em> node
+1. Under User Groups, click Add Group
+1. Select the <em>faculty</em> group
+1. Select the checkbox for the <em>imageCheckOut</em> privilege
+1. Click Submit New User Group
+1. Scroll down to the Resources section and click Add Resource Group
+1. Select the <em>image/faculty images</em> group
+1. Select the checkbox for the <em>available</em> attribute
+1. Click Submit New Resource Group
+1. Click on the <em>student access</em> node
+1. Under User Groups, click Add Group
+1. Select the <em>student</em> group
+1. Select the checkbox for the <em>imageCheckOut</em> privilege
+1. Click Submit New User Group
+1. Scroll down to the Resources section and click Add Resource Group
+1. Select the <em>image/student images</em> group
+1. Select the checkbox for the <em>available</em> attribute
+1. Click Submit New Resource Group</p>
+<p><a name="Example-GrantingTwoSetsofUsersAccesstoTwoDifferentSetsofImages-Summary"></a></p>
+<h2 id="summary">Summary</h2>
+<p>Now, users in the <em>faculty</em> user group will have access to check out images
+in the <em>faculty images</em> image group, and users in the <em>student</em> user group
+will have access to check out images in the <em>student images</em> image group.</p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/for-vcl-users.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/for-vcl-users.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/for-vcl-users.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,240 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - For VCL Users</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">For VCL Users</h1>
+    <p>There are several concepts you need to understand when administering VCL.</p>
+<p>{toc:outline=true|style=none}</p>
+<p><a name="ForVCLUsers-Resources"></a></p>
+<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>
+<p><a name="ForVCLUsers-Images/Environments"></a></p>
+<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. For example, an image could
+exist that could be deployed and used, but not saved, or another image may
+exist that can have access to it brokered by VCL, but it cannot be deployed
+or saved. VCL provides a way to assign other images to be "subimages" of an
+image to create an environment (or cluster). Images can be designed to run
+directly on a computer (bare metal) or under a hypervisor (virtualized
+images). Currently, VCL uses xCAT as the provisioning engine to manage bare
+metal images. Various versions of VMWare can be used to provision
+virtualized images. The VCL backend code (vcld) is 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>
+<p><a name="ForVCLUsers-Computers"></a></p>
+<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. </p>
+<p><a name="ForVCLUsers-ManagementNodes"></a></p>
+<h3 id="management-nodes">Management Nodes</h3>
+<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>
+<p><a name="ForVCLUsers-Schedules"></a></p>
+<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, 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>
+<p><a name="ForVCLUsers-Groups"></a></p>
+<h2 id="groups">Groups</h2>
+<p>Users and resources are placed into groups to make management of them
+easier.</p>
+<p><a name="ForVCLUsers-UserGroups"></a></p>
+<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>
+<p><a name="ForVCLUsers-ResourceGroups"></a></p>
+<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 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><a name="ForVCLUsers-ResourceManagement"></a></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>
+<p><a name="ForVCLUsers-ResourceGrouping"></a></p>
+<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 computers should not be combined into
+the same group which could result in VCL trying 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>
+<p><a name="ForVCLUsers-{anchor:resourcemapping}ResourceMapping"></a></p>
+<h3 id="anchorresourcemappingresource-mapping">{anchor:resourcemapping}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 a schedule).</p>
+<p>Any image in an image group can be run on any computer in a computer group
+to which it is mapped (provided a user has sufficient privileges to do so).
+There are a few things this allows you to do. If you have incompatible
+hardware, you would create separate computer groups for each type. Then,
+you would have image groups corresponding to each type so that you don't
+end up with VCL trying to deploy images from one type of hardware to an
+incompatible type of hardware. Another thing you can do with the 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>
+<p><a name="ForVCLUsers-Privileges"></a></p>
+<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 resource attributes can be blocked at a node
+so that they do not cascade down to that node or any of its children.</p>
+<p><a name="ForVCLUsers-UserPermissions"></a></p>
+<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>
+<li>computerAdmin - allows users to do administrative tasks with computers in
+computer groups with administer or manageGroup granted at the same node</li>
+<li>groupAdmin - grants users access to the Manage Groups portion of the site</li>
+<li>imageAdmin - allows users to do administrative tasks with images in image
+groups with administer or manageGroup granted at the same node</li>
+<li>imageCheckOut - allows users to make reservations for images in image
+groups with available granted at the same node</li>
+<li>mgmtNodeAdmin - allows users to do administrative tasks with management
+nodes in management node groups with administer or manageGroup granted at
+the same node</li>
+<li>nodeAdmin - allows users to add and delete child nodes at the specified
+node</li>
+<li>resourceGrant - grants users access to control what resource attributes
+are assigned at the same node</li>
+<li>scheduleAdmin - allows users to do administrative tasks with schedules in
+schedule groups with administer or manageGroup granted at the same node</li>
+<li>userGrant - grants users access to control what user permissions are
+assigned at the same node</li>
+</ul>
+<p><a name="ForVCLUsers-ResourceAttributes"></a></p>
+<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>
+<li>available - makes resources in the group available at the node - this is
+only has meaning for image groups and computer groups and relates to the
+imageCheckOut and imageAdmin user permissions</li>
+<li>administer - makes the resources in the group available to be
+administered by users with the appropriate user permissions at the same
+node (i.e. imageAdmin for image groups, computerAdmin for computer groups,
+etc)</li>
+<li>manageGroup - makes the resources in the group available to have their
+grouping controlled by users with the appropriate user permissions at the
+same node</li>
+<li>manageMapping - makes the resources in the group available to have their
+mapping controlled by users with the appropriate user permissions at the
+same node</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/frontend.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/frontend.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/frontend.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Frontend</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Frontend</h1>
+    <p><a href="web-code-overview.html">Overview of code structure</a></p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-only-vmware.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-only-vmware.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-only-vmware.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,370 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Further steps if using only VMWare</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Further steps if using only VMWare</h1>
+    <p>If you are using standalone VMWare servers (i.e. ones that VCL did not
+deploy using xCAT), you first need to add the VMWare servers; then, you
+need to add the virtual machines. You can either add them individually
+(Adding Individual VMWare Servers/Virtual Machines), or if they have
+sequential hostnames and IP addresses, you can add them all at once (Adding
+Multiple VMWare Servers/Virtual Machines).</p>
+<p>Once you have added at least one computer, you can get to the "Add Single
+Computer" page by going to Manage Computers-&gt;Edit Computer Information and
+clicking Add. You can get to the "Add Multiple Computers" page by doing the
+same thing but checking the "Add Multiple" checkbox.</p>
+<p><a name="FurtherstepsifusingonlyVMWare-AddingIndividualVMWareServers"></a></p>
+<h3 id="adding-individual-vmware-servers">Adding Individual VMWare Servers</h3>
+<ol>
+<li>click "Manage Computers"</li>
+<li>select the "Add Single Computer" radio button</li>
+<li>click Submit</li>
+<li>fill in</li>
+<li>
+<ul>
+<li>Hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>IP Address</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>State - vmhostinuse - double check this because you will not be able to
+change it later</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>owner (admin@Local)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>RAM</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Proc Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Network Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Type - blade</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Provisioning Engine - xCAT 2.x Provisioning</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>click the checkbox under "allcomputers"</li>
+</ul>
+</li>
+<li>click Confirm Computer</li>
+<li>click Submit</li>
+<li>select a VM Host Profile to use with this host - you can edit the VM Host
+Profile later if needed</li>
+<li>click Add Computer (don't worry about the fact that the computer you just
+added isn't listed after clicking Submit)</li>
+</ol>
+<p><a name="FurtherstepsifusingonlyVMWare-AddingIndividualVirtualMachines"></a></p>
+<h3 id="adding-individual-virtual-machines">Adding Individual Virtual Machines</h3>
+<p>VM computers cannot be added individually at the current time because some
+required database properties such as the&nbsp;MAC address&nbsp;do not get
+populated.&nbsp; Instead, use the steps described below to add multiple
+virtual machines.</p>
+<p><a name="FurtherstepsifusingonlyVMWare-AddingMultipleVMWareServers"></a></p>
+<h3 id="adding-multiple-vmware-servers">Adding Multiple VMWare Servers</h3>
+<ol>
+<li>click "Manage Computers"</li>
+<li>select the "Add Multiple Computers" radio button</li>
+<li>click Submit</li>
+<li>fill in</li>
+<li>
+<ul>
+<li>Hostname - the hostnames of all the computers must have a numerical part
+that is sequential, use a % as a placeholder where that part would be</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start value - the first number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End value - the last number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start IP Address - if using static public addresses, the IP addresses
+must be sequential; enter the first address here; if using DHCP, just enter
+something like 1.1.1.1</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End IP address - the last IP address of the sequence; if using DHCP,
+you'll need to enter something that would work out to the last address
+relative to Start IP Address (i.e. if adding 3 computers, use 1.1.1.1 for
+start and 1.1.1.3 for end)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>State - vmhostinuse - double check this because you will not be able to
+change it later</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Owner - owner of the computer</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>RAM</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Processor Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Network Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Type - blade</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Provisioning Engine - xCAT 2.x</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>check allComputers</li>
+</ul>
+</li>
+<li>click Confirm Computers</li>
+<li>click Submit</li>
+<li>select a VM Host Profile to use with these hosts - you can edit the VM
+Host Profile later if needed</li>
+<li>click Add Computers</li>
+</ol>
+<p><a name="FurtherstepsifusingonlyVMWare-AddingMultipleVirtualMachines"></a></p>
+<h3 id="adding-multiple-virtual-machines">Adding Multiple Virtual Machines</h3>
+<ol>
+<li>click "Manage Computers"</li>
+<li>select the "Add Multiple Computers" radio button</li>
+<li>click Submit</li>
+<li>fill in</li>
+<li>
+<ul>
+<li>Hostname - the hostnames of all the computers must have a numerical part
+that is sequential, use a % as a placeholder where that part would be</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start value - the first number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End value - the last number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start IP Address - if using static public addresses, the IP addresses
+must be sequential; enter the first address here; if using DHCP, just enter
+something like 1.1.1.1</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End IP address - the last IP address of the sequence; if using DHCP,
+you'll need to enter something that would work out to the last address
+relative to Start IP Address (i.e. if adding 3 computers, use 1.1.1.1 for
+start and 1.1.1.3 for end)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start private IP Address - similar to Start IP Address, but for the
+private side</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End private IP Address - similar to the End IP Address but for the
+private side</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start MAC Address - if mac addresses are sequential, with the first one
+being the private MAC address for the first computer, the second one being
+the public MAC address for the first computer, the third one being the
+private MAC address of the second computer, etc, you can enter the first
+one here and then have the option of generating data to add to your
+dhcpd.conf file later in the process.
+{color:#ff0000}{<em>}Important{</em>}{color}: for VMware VMs, the MAC addresses
+you choose must be in the range&nbsp;00:50:56:00:00:00 - 00:50:56:3F:FF:FF</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>State - maintenance</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Owner - owner of the computer</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>RAM</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Processor Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Network Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Type - virtualmachine</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Provisioning Engine - VMware</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>check "All VM Computers" and newvmimages</li>
+</ul>
+</li>
+<li>click Confirm Computers</li>
+<li>click Submit</li>
+<li>If you filled in the private address fields and the Start MAC Address,
+you can now enter the private IP address of the management node that will
+be handling these virtual machines to generate information to add to your
+dhcpd.conf file.</li>
+</ol>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-xcat.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-xcat.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/further-steps-if-using-xcat.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,193 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Further steps if using xCAT</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Further steps if using xCAT</h1>
+    <p>You can initially add individual computers or multiple computers all
+together. After you have added at least one computer, you will need to go
+to Manage Computers -&gt; Edit Computer Information to additional ones.</p>
+<p><a name="FurtherstepsifusingxCAT-AddingIndividualComputers"></a></p>
+<h3 id="adding-individual-computers">Adding Individual Computers</h3>
+<ol>
+<li>click "Manage Computers"</li>
+<li>select the "Add Single Computer" radio button</li>
+<li>click Submit</li>
+<li>fill in Hostname, IP Address, owner (admin@Local), RAM, Proc Speed, 
+Network Speed, select "blade" for Type, select "xCAT 2.x Provisioning"  for
+"Provisioning Engine", and click the checkbox under "allcomputers",  and
+"newimages"</li>
+<li>click Confirm Computer</li>
+<li>click Submit (don't worry about the fact that the computer you just added
+isn't listed after clicking Submit)</li>
+<li>after you've configured your image library and your management node  has
+started checking in, you should be able to make a reservation</li>
+</ol>
+<p><a name="FurtherstepsifusingxCAT-AddingMultipleComputers"></a></p>
+<h3 id="adding-multiple-computers">Adding Multiple Computers</h3>
+<ol>
+<li>click "Manage Computers"</li>
+<li>select the "Add Multiple Computers" radio button</li>
+<li>click Submit</li>
+<li>fill in</li>
+<li>
+<ul>
+<li>Hostname - the hostnames of all the computers must have a numerical part
+that is sequential, use a % as a placeholder where that part would be</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start value - the first number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End value - the last number of the numerical part of the hostname</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Start IP Address - if using static public addresses, the IP addresses
+must be sequential; enter the first address here; if using DHCP, just enter
+something like 1.1.1.1</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>End IP address - the last IP address of the sequence; if using DHCP,
+you'll need to enter something that would work out to the last address
+relative to Start IP Address (i.e. if adding 3 computers, use 1.1.1.1 for
+start and 1.1.1.3 for end)</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Owner - owner of the computer</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>RAM</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Processor Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Network Speed</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Type - blade</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>Provisioning Engine - xCAT 2.x</li>
+</ul>
+</li>
+<li>
+<ul>
+<li>check allComputers and newimages</li>
+</ul>
+</li>
+<li>click Confirm Computer</li>
+<li>click Submit (don't worry about the fact that the computers you just
+added aren't listed after clicking Submit)</li>
+<li>after you've configured your image library and your management node has
+started checking in, you should be able to make a reservation</li>
+</ol>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/graduation-board-resolution.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/graduation-board-resolution.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/graduation-board-resolution.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Graduation Board Resolution</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Graduation Board Resolution</h1>
+    <p>X. Establish the Apache VCL Project</p>
+<p>WHEREAS, the Board of Directors deems it to be in the best
+interests of the Foundation and consistent with the
+Foundation's purpose to establish a Project Management
+Committee charged with the creation and maintenance of
+open-source software related to a modular cloud computing platform
+which dynamically provisions and brokers remote access to compute
+resources for distribution at no charge to the public.</p>
+<p>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
+Committee (PMC), to be known as "The Apache VCL Project", be
+and hereby is established pursuant to Bylaws of the
+Foundation; and be it further</p>
+<p>RESOLVED, that the Apache VCL Project be and hereby is
+responsible for the creation and maintenance of software
+related to a modular cloud computing platform which dynamically
+provisions and brokers remote access to compute resources;
+and be it further</p>
+<p>RESOLVED, that the office of "Vice President, Apache VCL" be
+and hereby is created, the person holding such office to serve
+at the direction of the Board of Directors as the chair of the
+Apache VCL Project, and to have primary responsibility for
+management of the projects within the scope of responsibility
+of the Apache VCL Project; and be it further</p>
+<p>RESOLVED, that the persons listed immediately below be and
+hereby are appointed to serve as the initial members of the
+Apache VCL Project:</p>
+<ul>
+<li>Alan Cabrera          <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#97;&#100;&#99;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#97;&#100;&#99;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Dmitri Chebotarov     <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#100;&#105;&#109;&#97;&#99;&#104;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#100;&#105;&#109;&#97;&#99;&#104;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Aaron Coburn          <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#97;&#99;&#111;&#98;&#117;&#114;&#110;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#97;&#99;&#111;&#98;&#117;&#114;&#110;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>David Hutchins        <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#100;&#110;&#104;&#117;&#116;&#99;&#104;&#105;&#110;&#115;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#100;&#110;&#104;&#117;&#116;&#99;&#104;&#105;&#110;&#115;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Andy Kurth            <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#97;&#114;&#107;&#117;&#114;&#116;&#104;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#97;&#114;&#107;&#117;&#114;&#116;&#104;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Kevan Miller          <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#107;&#101;&#118;&#97;&#110;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#107;&#101;&#118;&#97;&#110;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>James O'Dell          <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#106;&#111;&#100;&#101;&#108;&#108;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#106;&#111;&#100;&#101;&#108;&#108;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Aaron Peeler          <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#102;&#97;&#112;&#101;&#101;&#108;&#101;&#114;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#102;&#97;&#112;&#101;&#101;&#108;&#101;&#114;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+<li>Josh Thompson         <a href="&#109;&#97;&#105;&#108;&#116;&#111;&#58;&#106;&#102;&#116;&#104;&#111;&#109;&#112;&#115;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;">&#106;&#102;&#116;&#104;&#111;&#109;&#112;&#115;&#64;&#97;&#112;&#97;&#99;&#104;&#101;&#46;&#111;&#114;&#103;</a></li>
+</ul>
+<p>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Kurth
+be appointed to the office of Vice President, Apache VCL, to
+serve in accordance with and subject to the direction of the
+Board of Directors and the Bylaws of the Foundation until
+death, resignation, retirement, removal or disqualification,
+or until a successor is appointed; and be it further</p>
+<p>RESOLVED, that the initial Apache VCL PMC be and hereby is
+tasked with the creation of a set of bylaws intended to
+encourage open development and increased participation in the
+Apache VCL Project; and be it further</p>
+<p>RESOLVED, that the Apache VCL Project be and hereby
+is tasked with the migration and rationalization of the Apache
+Incubator VCL podling; and be it further</p>
+<p>RESOLVED, that all responsibilities pertaining to the Apache
+Incubator VCL podling encumbered upon the Apache Incubator
+Project are hereafter discharged.</p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/graduation-migration-todo.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/graduation-migration-todo.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/graduation-migration-todo.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,222 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Graduation Migration ToDo</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Graduation Migration ToDo</h1>
+    <p>This page is to track all the things that need to happen for migrating out
+of the incubator. Put your name next to any you are working on. Strike them
+out when completed.</p>
+<p><a name="GraduationMigrationToDo-TasksforPMCChair(AndyKurth)"></a></p>
+<h2 id="tasks-for-pmc-chair-andy-kurth">Tasks for PMC Chair (Andy Kurth)</h2>
+<ul>
+<li>-Subscribe to the board mailing list-
+{color:#008000}<em>(subscribed)</em>{color}</li>
+<li>-Subscribe to the infrastructure mailing list- {color:#008000}<em>(was
+already subscribed)</em>{color}</li>
+<li>-Ensure that they have been added to the- -<a href="http://people.apache.org/committers-by-project.html#pmc-chairs">PMC chairs group (pmc-chairs) in LDAP</a>
+--. The pmc-chairs group is maintained by infrastructure. If they don't add
+you, give them a nudge...- {color:#008000}<em>(confirmed)</em>{color}</li>
+<li>-Check out the foundation/officers folder from the private repository.
+Users with member or pmc-chairs karma can do this.-
+{color:#008000}<em>(done)</em>{color}</li>
+<li>-Add yourself to the foundation/officers/affiliations.txt and the
+foundation/officers/irs-disclosures.txt files with the appropriate
+information.- {color:#008000}<em>(done)</em>{color}</li>
+<li>
+<p>Review appropriate documentation:
+<strong> <a href="http://www.apache.org/dev/pmc.html#chair">PMC Chair Duties</a>
+</strong> PMC <a href="http://www.apache.org/dev/#pmc">documentation</a>
+<strong> Jakarta <a href="http://wiki.apache.org/jakarta/RoleOfChair">Chair guide</a>
+</strong> Incubator <a href="http://incubator.apache.org/guides/chair.html">Chair guide</a>
+<em><em> -Reporting- -<a href="http://www.apache.org/foundation/board/calendar.html">calendar </a>
+--- Work out a reporting schedule with the Board. For the first three
+months after graduation this will be monthly. After that, the project
+should slot into a quarterly reporting schedule. Now is a good time to
+remove the project from the Incubator reporting schedule.-
+{color:#008000}</em>(March, June, September, December)</em>{color}</p>
+</li>
+<li>
+<p>-Add the PMC chair details to the foundation web site Officer list at- -<a href="http://www.apache.org/foundation/index.html">http://www.apache.org/foundation/index.html</a></p>
+</li>
+<li>{color:#008000}<em>(done)</em>{color}</li>
+<li>-Add the new project's PMC chair to the
+foundation/officers/irs-disclosures.txt file. You will need a member to
+help with this task.- {color:#008000}<em>(done)</em>{color}</li>
+<li>-Ensure the PMC is added to the committee-info.txt file at- -<a href="https://svn.apache.org/repos/private/committers/board/committee-info.txt">https://svn.apache.org/repos/private/committers/board/committee-info.txt </a>
+-[{color:#008000}<em>(done)</em>{color}|https://svn.apache.org/repos/private/committers/board/committee-info.txt]
+** -There are 3 sections which need to be updated; see instructions in the
+file. You may need to get a member to help with this.-</li>
+<li>-Establish PMC-
+<strong> -Create private list- {color:#008000}<em>(existing list was
+transferred)</em>{color}</strong> -Subscribe initial members to private list-</li>
+</ul>
+<p><a name="GraduationMigrationToDo-GeneralTasks"></a></p>
+<h2 id="general-tasks">General Tasks</h2>
+<p>Work with the Apache Infrastructure team to set up the top level project
+infrastructure. The various infrastructure tasks that are required (see
+check list) should be consolidated into a single issue (see this for
+example). This should be created in the category TLP Admin.</p>
+<p>h3. JIRA issue to track tasks:&nbsp; {color:#008000}<a href="https://issues.apache.org/jira/browse/INFRA-4977">https://issues.apache.org/jira/browse/INFRA-4977</a>
+{color}</p>
+<p>Transfer resources from incubator to TLP
+<em> Source
+<strong> -Post an announcement to the development list telling everyone that the
+repository is about to be moved-
+</strong> -svn move the podling source tree-
+<strong> -Post an announcement containing instructions for developers describing
+how to svn switch their workspaces-
+</strong> Update site, wikis, pom.xml and other resources to point to the new
+repository location.
+</em> Websites
+<strong> Transfer the podling website (request svnsubpub site)
+</strong> Load the website into its new home. See infra notes.
+<strong> Update the incubator/site-publish/.htaccess entry to redirect traffic
+from the old URLs to the new. (svn location is at <a href="http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess">http://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess</a>
+)
+</strong> Delete the podling website from /www/incubator.apache.org/content/vcl on
+people.apache.org. If you do not have the necessary privileges, file a
+ticket with Infra.
+<strong> Post an announcement to user and development lists
+* Update the Incubator site
+</strong> Update the Incubator status page
+<strong> Update the podling status page. All sections should now be filled in
+including EXIT. Take some time to read carefully since this page forms the
+final public record for graduation.
+</strong> Edit the Incubator website to remove the podling from the list in
+project.xml. Here explains how.
+<em> Add Project To  www.apache.org
+<strong> Check out <a href="https://svn.apache.org/repos/asf/infrastructure/site/trunk">https://svn.apache.org/repos/asf/infrastructure/site/trunk</a>
+</strong> Patch  xdocs/stylesheets/project.xml
+<strong> If you have karma, regenerated and apply patch
+</strong> If you do not have karma, submit patch to  infrastructure JIRA
+</em> Mailing lists
+<strong> -Request that podlings lists be transferred to their new home. Any new
+mailing lists should be requested at the same time.-
+</strong> When this has been executed by infrastructure, post an announcement to
+user and development lists.
+<strong> Send notice to nabble.com (if they archive your incubator mailing list)
+that the address has changed, and possibly the location of your project (if
+it is listed as being part of the incubator). Repeat for other known
+mailing list archivers.
+</strong> Update website: replace links to old archives with links to new ones and
+add new links to historic archives from incubation.
+<strong> -Check project-private mailing list membership. Mentors should be
+allowed to remain if they wish to do so. The subscriber list should
+otherwise match that on the resolution. See  this and the EZMLM
+"Moderator's and Administrator's Manual".-
+</strong> Update mail addresses including (The chair should have karma to perform
+these tasks):
+<strong><em> svn commit messages (see
+infrastructure/trunk/subversion/authorization/asf-mailer.conf )
+</em></strong> confluence commit messages (see adminstration documentation)
+<strong><em> issue tracking messages (see administration documentation)
+</em> Issue Tracking</strong> Check that the issue tracking system used by the podling reflects the
+project's new status.
+<em> Distribution mirrors
+</em>* After you have a release at your new home (/dist/vcl/ area), remove any
+distribution artifacts from your old /dist/incubator/vcl/ area. Remember
+from the mirror guidelines that everything is automatically added to
+archive.apache.org anyway.</p>
+<ul>
+<li>Final Revision of Podling Incubation Records - When a project graduates,
+then the incubator resources need to be updated to indicate that the
+project is no longer incubating. Here are a few of the items that need to
+be done:
+<strong> Update the svn incubator/trunk/content/projects/vcl.xml file to show the
+project's status.
+</strong> Change the podling status to "graduated" in the podling summary file,
+i.e update the incubator/trunk/content/podlings.xml svn file. Also add the
+"enddate" attribute to document when the project graduated.
+** Ensure that other svn resources for your project have moved to your new
+home.</li>
+</ul>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/granting-access-to-a-new-image.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/granting-access-to-a-new-image.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/granting-access-to-a-new-image.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,171 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Granting Access to a New Image</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Granting Access to a New Image</h1>
+    <p><a name="GrantingAccesstoaNewImage-Overview"></a></p>
+<h2 id="overview">Overview</h2>
+<p>Once you have created a new image, there are a few things you have to do to
+allow other people to use it.&nbsp; If you don't have access to do any of
+the following steps, you will need to get a VCL administrator to do them
+for you.</p>
+<p>When you create a new image, it is only available to you, and it is only
+allowed to be run on a few computers that have been set aside for the
+testing of new images.</p>
+<p><em>NOTE</em>: After you have been through these steps one time, if you are
+granting the same set of users access to a new image, you may only have to
+perform step 1.1 for subsequent images.</p>
+<p><a name="GrantingAccesstoaNewImage-Step1:ImageMapping"></a></p>
+<h2 id="step-1-image-mapping">Step 1: Image Mapping</h2>
+<p>Images are mapped to be run on a set of computers. See the documentation on <a href="for-vcl-users#resourcemapping.html">Resource Mapping</a>
+ to learn more about why this is done. For your new image to be able to run
+on more computers than just those designated for testing, you need to map
+it to a set of computers. There are a few steps to this process:
+1. You need to make your image a member of an image group
+1. * Select {color:#0000ff}Manage Images{color}-&gt;{color:#0000ff}Edit Image
+Grouping{color}
+1. * Select your image from the drop down box and click {color:#0000ff}Get
+Groups{color}
+1. * Choose one or more image groups to which you would like to add the image
+from the box on the right
+1. * Click {color:#0000ff}&lt;-Add{color} to make the image a member of the
+group(s)
+1. You need to map the image group(s) you selected in #1 to one or more
+computer groups (if they are not already mapped)
+1. * Select {color:#0000ff}Manage Images{color}-&gt;{color:#0000ff}Edit Image
+Mapping{color}
+1. * Do the following for each group from #1:
+1. <strong> Select the image group from the drop down box and click
+{color:#0000ff}Get Computer Groups{color}
+1. </strong> Choose one or more computer groups to which you would like to map the
+image group from the box on the right
+1. <em><em> click {color:#0000ff}&lt;-Add{color} to map the image group to the
+computer group(s)
+1. * </em>Note</em>: there is an assumption here that the computer groups you
+selected already have computers that are in those groups</p>
+<p><a name="GrantingAccesstoaNewImage-Step2:Privileges"></a></p>
+<h2 id="step-2-privileges">Step 2: Privileges</h2>
+<p>Now, you need to grant access to use the image to a user or group of users
+under the Privileges section of the site.&nbsp; Here are the steps
+involved:
+1. Select {color:#0000ff}Privileges{color}
+1. Choose an existing node or create a new node in the tree structure in the
+upper portion of the page where you would like to assign the user(s) access
+1. Now, you need to grant the user {color:#0000ff}imageCheckOut{color} at
+the node.&nbsp; You can do this for an individual user or a group of users.
+1. * Individual User:
+1. <strong> Click {color:#0000ff}Add User{color}
+1. </strong> Enter the user's id (you may need to include the user's affiliation) in
+the text box and select the {color:#0000ff}imageCheckOut{color} checkbox
+1. <strong> Click {color:#0000ff}Submit New User{color}
+1. * User Group:
+1. </strong> Click {color:#0000ff}Add Group{color}
+1. <strong> Select the user group from the drop-down box and select the
+{color:#0000ff}imageCheckOut{color} checkbox
+1. </strong> Click {color:#0000ff}Submit New User Group{color}
+1. Next, you need to make sure the image group in which you placed the image
+in #1 of <em>Image Mapping</em> is available at this node. If it is, go on to the
+next step, if not:
+1. * Click {color:#0000ff}Add Resource Group{color}
+1. * Select the image group from the drop-down box and select the
+{color:#0000ff}available{color} checkbox
+1. * Click {color:#0000ff}Submit New Resource Group{color}
+1. Finally, you need to make sure the computer group(s) selected in #2 of
+<em>Image Mapping</em> are also available here. If so, you are finished.&nbsp; If
+not:
+1. * Click {color:#0000ff}Add Resource Group{color}
+1. * Select the computer group from the drop-down box and select the
+{color:#0000ff}available{color} checkbox
+1. * Click {color:#0000ff}Submit New Resource Group{color}</p>
+<p>Now, the user or user groups you have added to this node will be able to
+make reservations for the new image.</p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/guidelines-for-large-contributions.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/guidelines-for-large-contributions.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/guidelines-for-large-contributions.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,122 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - Guidelines for Large Contributions</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">Guidelines for Large Contributions</h1>
+    <p>These are some guidelines for making a large contribution to Apache VCL for
+people who are not currently committers.</p>
+<ol>
+<li>State on the vcl-dev list what modification you'd like to make.  Some
+background on why the existing codebase doesn't work in your situation
+would
+be useful.  Remember, when you modify existing code, it affects work being
+done by other contributors, which can result in imposing additional work on
+them.</li>
+<li>Propose a plan on the vcl-dev list for making the modification.  There
+may
+be others that want the same modification or something similar that can be
+incorporated at the same time.  Those people can help develop the
+modification.  On the other hand, the modification may have a very negative
+affect on some other part of the project.  Also, this provides an
+opportunity
+for existing contributors (those who know the codebase well) to provide
+input
+on your plan.  The plan needs to include how the modification will be
+maintained in the future - will you continue to maintain it; will existing
+contributors have to pick it up and maintain it?</li>
+<li>Create a JIRA issue to track implementation of the plan and start
+developing.  This provides a way for others to track work being done on the
+modification and ensures information about the modification will be added
+to
+the CHANGELOG when the next release is cut.</li>
+</ol>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>

Added: websites/staging/vcl/trunk/content/confluence_export/how-do-i-grant-a-user-access-to-an-image?.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/how-do-i-grant-a-user-access-to-an-image?.html (added)
+++ websites/staging/vcl/trunk/content/confluence_export/how-do-i-grant-a-user-access-to-an-image?.html Tue Jan  8 16:38:15 2013
@@ -0,0 +1,136 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+
+  <link href="/css/vcl.css" rel="stylesheet" type="text/css">
+  <link href="/css/code.css" rel="stylesheet" type="text/css">
+  <title>Apache VCL - How do I grant a user access to an image?</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="sitetitle">
+    <table width="100%" border="0" cellspacing="0" cellpadding="5">
+      <tr>
+         <td><a href="/index.html"><img src="/img/vcl-logo.png" height="100" align="left" alt="Apache VCL logo"></a></td>
+         <td><a href="http://www.apache.org"><img src="/img/asf-logo.png" align="right" alt="Apache Software Foundation logo"></a></td>
+      </tr>
+    </table>
+  </div>
+
+  <div id="navigation"> 
+  <ul>
+<li>Information<ul>
+<li><a href="/info/about.html">What is VCL?</a></li>
+<li><a href="/info/features.html">Features</a></li>
+<li><a href="/info/architecture.html">Architecture</a></li>
+<li><a href="/info/use-cases.html">Use Cases</a></li>
+<li><a href="/downloads/download.cgi">Download</a></li>
+<li><a href="http://www.apache.org/licenses/LICENSE-2.0.html">License</a></li>
+<li><a href="/info/faq.html">FAQ</a></li>
+</ul>
+</li>
+<li><a href="/docs/index.html">Documentation</a><ul>
+<li><a href="/docs/using-vcl.html">Using VCL</a></li>
+<li><a href="/docs/image-creation.html">Image Creation</a></li>
+<li><a href="/docs/administration.html">Administration</a></li>
+<li><a href="/docs/installation.html">Installation</a></li>
+<li><a href="/docs/deployment-planning.html">Deployment Planning</a></li>
+</ul>
+</li>
+<li><a href="/comm/index.html">Community</a><ul>
+<li><a href="/comm/index.html#getInvolved">Getting Involved</a></li>
+<li><a href="/comm/index.html#mail-list">Mailing Lists</a></li>
+<li><a href="/comm/index.html#how-do-i-join-the-project">How can I Join</a></li>
+<li><a href="/comm/wiki.html">Wiki</a></li>
+<li><a href="/dev/index.html">Development</a><ul>
+<li><a href="/dev/jira.html">Issue Tracking</a></li>
+<li><a href="/dev/code-documentation.html">Code Documentation</a></li>
+<li><a href="/dev/roadmap.html">Roadmap</a></li>
+</ul>
+</li>
+</ul>
+</li>
+<li><a href="http://www.apache.org">Apache Software Foundation</a><ul>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+</ul>
+</li>
+</ul>
+  </div>
+  
+  <div id="content">
+    <h1 class="title">How do I grant a user access to an image?</h1>
+    <p>How Do I grant a user access to an Image?
+The 1st step would to make sure that you have an image that you want to
+access.
+I would 1st go into the Mage Group and add a Resource Group Called Math.
+This would be a Image Type and the Name would be Math, the owning User
+group will be my AdminTeam@mycampus. A group has now been created called
+Math. 
+Then in your Manage Images Under Edit Image grouping.  I prefer the Check
+box Grid
+To the Left in the Image table these are the Images that you have created
+you can either create a new Image Group or check off an image to a group.
+You can also add all of your images to the same group. For example, I
+created a group called Math. I am going to group my Mathmatica 7 and Maple
+13 images in this Math Group. (I have already created both of these images)
+Both are Math software and I will check them in the same group. You then
+scroll down and hit Submit Changes.
+Now will go to the Privilege Tree
+I have our Privilege Tree by Department
+I have my Tree Setup by Campus. I will check on my campus then Math
+Department
+Once I am here I can then manually add to either Users (One person at a
+time) Or I can add to the User Group. We have used people soft to import
+users for our Classes. For example Math_2301 has 30 users. I am going to
+group the User Group Math_2301 and give them access to ImageCheckout. I
+will only click on Image checkout. I just want to give them that access
+only.
+Move down to the Resources in the Privileges Tree
+I’m going to now give it access to my VMware Vmguest Pool. I have called
+our pool my campus VMguest, I am going to check on Available. This will now
+make the selected Vmguest available to check out an image of my choice. The
+VMguest should be in the group type computer.
+I am now going to add a group type Image. This will give an image that is
+available to this pool. I will then add my group name Math with the group
+type Image. I will then check on available.</p>
+<p>Once this is done. I have made my Math Image under the Math Group available
+for my Math_2301 class.</p>
+<p>Let’s say there is a student who isn’t listed in the class or a TA that
+also needs access to this image.
+Go to the User in the Privileges at the Selected Node, you can manually add
+a user, don’t forget it needs to be there NET ID or ID @ their correct
+affliction.  For example AD3421@Mycampus</p>
+  </div>
+  
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2012 The Apache Software Foundation, Licensed under 
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logo are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+  
+</body>
+</html>



Mime
View raw message