Author: buildbot
Date: Fri Aug  3 19:27:01 2012
New Revision: 827897

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/docs/VCL23Installation.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug  3 19:27:01 2012
@@ -1 +1 @@
-1369170
+1369174

Modified: websites/staging/vcl/trunk/content/docs/VCL23Installation.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/VCL23Installation.html (original)
+++ websites/staging/vcl/trunk/content/docs/VCL23Installation.html Fri Aug  3 
19:27:01 2012
@@ -496,7 +496,42 @@ The following management node installati
 <p>The install_perl_libs.pl script included in the VCL distribution will 
attempt to download and install the required Linux packages and Perl modules. 
It uses the yum utility to install the required Linux packages. The required 
Perl modules are available from CPAN - The Comprehensive Perl Archive Network. 
The install_perl_libs.pl script attempts to download and install the required 
Perl modules by using the CPAN.pm module which is included with most Perl 
distributions. </p>
 <p>The yum utility should exist on any modern Red Hat-based Linux distribution 
(Red Hat, CentOS, Fedora, etc). If yum isn't available on your management node 
OS, you will need to download and install the required Linux packages manually 
or by using another package management utility. After installing the required 
Linux packages, attempt to run the install_perl_libs.pl script again.</p>
 </li>
+<li>
+<p><strong>Configure vcld.conf</strong></p>
+<ul>
+<li>
+<p>Create the /etc/vcl directory:</p>
+<div class="codehilite"><pre><span class="nb">mkdir</span> <span 
class="sr">/etc/</span><span class="n">vcl</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Copy the stock vcld.conf file to /etc/vcl:</p>
+<div class="codehilite"><pre><span class="n">cp</span> <span 
class="sr">/usr/</span><span class="nb">local</span><span 
class="sr">/vcl/</span><span class="n">etc</span><span 
class="sr">/vcl/</span><span class="n">vcld</span><span class="o">.</span><span 
class="n">conf</span> <span class="sr">/etc/</span><span class="n">vcl</span>
+</pre></div>
+
+
+</li>
+<li>
+<p>Edit /etc/vcl/vcld.conf:</p>
+<div class="codehilite"><pre><span class="n">vi</span> <span 
class="sr">/etc/</span><span class="n">vcl</span><span class="o">/</span><span 
class="n">vcld</span><span class="o">.</span><span class="n">conf</span>
+</pre></div>
+
+
+</li>
+</ul>
+</li>
 </ul>
+<p>The following lines must be configured in order to start the VCL daemon 
(vcld) and allow it to check in to the database:
+<em> FQDN - the fully qualified name of the management node, this should match 
the name that was configured for the management node in the database
+</em> server - the IP address or FQDN of the database server
+<em> LockerWrtUser - database user account with write privileges
+</em> wrtPass - database user password
+<em> xmlrpc_pass - password for xmlrpc api from vcld to the web interface(can 
be long). This will be used later to sync the database vclsystem user account
+</em> xmlrpc_url - URL for xmlrpc api 
https://my.server.org/vcl/index.php?mode=xmlrpccall</p>
+<div class="codehilite"><pre><span class="o">*</span> <span 
class="n">Save</span> <span class="n">the</span> <span 
class="n">vcld</span><span class="o">.</span><span class="n">conf</span> <span 
class="n">file</span>
+</pre></div>
   </div>
   
   <div id="footer">


Reply via email to