svn commit: r849741 - in /websites/staging/vcl/trunk/content: ./ confluence_export/image-capture-sequence.html

[bu...@apache.org]

Author: buildbot
Date: Thu Feb  7 13:54:05 2013
New Revision: 849741

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/confluence_export/image-capture-sequence.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb  7 13:54:05 2013
@@ -1 +1 @@
-1443474
+1443476

Modified: websites/staging/vcl/trunk/content/confluence_export/image-capture-sequence.html
==============================================================================
--- websites/staging/vcl/trunk/content/confluence_export/image-capture-sequence.html (original)
+++ websites/staging/vcl/trunk/content/confluence_export/image-capture-sequence.html Thu Feb  7 13:54:05 2013
@@ -78,36 +78,35 @@
   
   <div id="content">
     <h1 class="title">Image Capture Sequence</h1>
-    <p><a name="ImageCaptureSequence-ModularizationExample"></a></p>
-<h2 id="modularization-example">Modularization Example</h2>
-<p>The following diagram&nbsp;shows how the image capture sequence
-differs&nbsp;if different provisioning modules are used --&nbsp;xCAT and
-VMWare.&nbsp;</p>
-<p>Take note of the following:
-<em> The calls made by image.pm to the&nbsp;xCAT and VMWare capture()
-subroutines&nbsp;are </em>identical<em>.&nbsp; The image.pm state module does not
-care which provisioning engine is being used.&nbsp; All it knows is that a
+    <h2 id="modularization-example">Modularization Example</h2>
+<p>The following diagram shows how the image capture sequence
+differs if different provisioning modules are used -- xCAT and
+VMWare.</p>
+<p>Take note of the following:</p>
+<ul>
+<li>The calls made by image.pm to the xCAT and VMWare capture()
+subroutines are <strong>identical</strong>.  The image.pm state module does not
+care which provisioning engine is being used. All it knows is that a
 provisioning engine object has been created before image.pm::process() was
-called,&nbsp;the object can be accessed via $self-&gt;provisioner, and the
-name of the subroutine to call is capture().
-</em> The&nbsp;calls made by xCAT and VMWare's capture() subroutine&nbsp;to the
-Windows.pm pre_capture() subroutine are <em>identical</em>.&nbsp; All a
+called, the object can be accessed via $self-&gt;provisioner, and the
+name of the subroutine to call is capture().</li>
+<li>The calls made by xCAT and VMWare's capture() subroutine to the
+Windows.pm pre_capture() subroutine are <strong>identical</strong>. All a
 provisioning engine module needs to know is that an OS object has been
-created,&nbsp;the object can be accessed via $self-&gt;os, and the name of the
-subroutine to call is pre_capture().
-<em> Provisioning engine modules do not not need to know any of the operating
-system details.&nbsp;&nbsp;They assume the OS module's pre_capture()
+created, the object can be accessed via $self-&gt;os, and the name of the
+subroutine to call is pre_capture().</li>
+<li>Provisioning engine modules do not not need to know any of the operating
+system details. They assume the OS module's pre_capture()
 subroutine will perform all the steps necessary for the particular OS to be
 captured and that the computer will be shut down (or left in the state
-specified by the end_state argument) when pre_capture() returns.
-</em> The OS module's pre_capture() subroutine&nbsp;does not&nbsp;care which
-provisioning engine is being used.&nbsp; The steps it performs are
-identical.
-* A very similar example could be made using the same provisioning engine
-module and different OS modules.</p>
-<hr />
-<p>{gliffy:name=Image Capture Sequence - xCAT|space=VCL|page=Image Capture
-Sequence|align=left|size=L|version=13}</p>
+specified by the end_state argument) when pre_capture() returns.</li>
+<li>The OS module's pre_capture() subroutine does not care which
+provisioning engine is being used.  The steps it performs are
+identical.</li>
+<li>A very similar example could be made using the same provisioning engine
+module and different OS modules.</li>
+</ul>
+<p><img src="image_capture_sequence_xcat.png"></p>
   </div>
   
   <div id="footer">