You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@slider.apache.org by bu...@apache.org on 2014/11/11 21:31:14 UTC

svn commit: r928835 - in /websites/staging/slider/trunk/content: ./ docs/configuration/core.html

Author: buildbot
Date: Tue Nov 11 20:31:13 2014
New Revision: 928835

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/docs/configuration/core.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Nov 11 20:31:13 2014
@@ -1 +1 @@
-1638312
+1638368

Modified: websites/staging/slider/trunk/content/docs/configuration/core.html
==============================================================================
--- websites/staging/slider/trunk/content/docs/configuration/core.html (original)
+++ websites/staging/slider/trunk/content/docs/configuration/core.html Tue Nov 11 20:31:13 2014
@@ -549,6 +549,23 @@ of the author of the configuration file 
    &quot;<span class="n">container</span><span class="p">.</span><span class="n">launch</span><span class="p">.</span><span class="n">delay</span><span class="p">.</span><span class="nb">sec</span>&quot;<span class="p">:</span> &quot;30&quot;
 <span class="p">}</span>
 </pre></div>
+
+
+<h4 id="specifying-the-python-executable-path">Specifying the Python Executable Path</h4>
+<p>Currently the Slider containers leverage python for component scripts (the scripts responsible for component lifecycle operations).  When deploying applications on certain variations of linux or other operating systems (e.g. Centos 5) , the version of python on the system path may be incompatible with the component script (e.g. methods or imports utilized are not available).  In those circumstances the path to the python executable for container script execution can be specified by the "agent.python.exec.path" property:   </p>
+<div class="codehilite"><pre>  &quot;<span class="k">global</span>&quot;<span class="p">:</span> <span class="p">{</span>
+    &quot;<span class="n">agent</span><span class="p">.</span><span class="n">python</span><span class="p">.</span><span class="n">exec</span><span class="p">.</span><span class="n">path</span>&quot;<span class="p">:</span> &quot;<span class="o">/</span><span class="n">usr</span><span class="o">/</span><span class="n">bin</span><span class="o">/</span><span class="n">python</span>&quot;<span class="p">,</span>
+    <span class="p">.</span> <span class="p">.</span> <span class="p">.</span>
+    <span class="p">}</span>
+</pre></div>
+
+
+<p>This property may also be specified in the slider-client.xml file (typically in the "conf" directory of the slider installation) if the python version specified is to be utilized across multiple deployments:</p>
+<div class="codehilite"><pre><span class="nt">&lt;property&gt;</span>
+  <span class="nt">&lt;name&gt;</span>agent.python.exec.path<span class="nt">&lt;/name&gt;</span>
+  <span class="nt">&lt;value&gt;</span>/usr/bin/python<span class="nt">&lt;/value&gt;</span>
+<span class="nt">&lt;/property&gt;</span>
+</pre></div>
   </div>
 
   <div id="footer">