Installing the AEN compute node(s) (AEN 4.1.3)
==============================================

.. raw:: html

    <div class="contents local topic" id="contents">
    <ul class="simple">
    <li><a class="reference internal" href="#setting-variables-and-changing-permissions" id="id1">Setting variables and changing permissions</a></li>
    <li><a class="reference internal" href="#running-the-aen-compute-installer" id="id2">Running the AEN compute installer</a></li>
    <li><a class="reference internal" href="#configuring-your-compute-node-s" id="id3">Configuring your compute node(s)</a></li>
    <li><a class="reference internal" href="#what-s-next" id="id4">What&#8217;s next</a></li>
    </ul>
    </div>
    <p>Compute nodes are where projects are stored and run.</p>
    <p>Adding multiple AEN compute machines allows you to scale-out horizontally to
    increase capacity. Projects can be created on individual compute nodes to
    spread the load.</p>
    <p>Repeat this procedure on each compute machine.</p>
    <div class="section" id="setting-variables-and-changing-permissions">
    <h2><a class="toc-backref" href="#id1">Setting variables and changing permissions</a><a class="headerlink" href="#setting-variables-and-changing-permissions" title="Permalink to this headline">¶</a></h2>
    <p>Run:</p>
    <div class="highlight-bash"><div class="highlight"><pre><span></span><span class="nb">export</span> <span class="nv">AEN_SERVER</span><span class="o">=</span>&lt;FQDN HOSTNAME OR IP ADDRESS&gt; <span class="c1"># Use the real FQDN</span>
    chmod a+x aen-*.sh                <span class="c1"># Set installer to be executable</span>
    </pre></div>
    </div>
    <p>NOTE: Change &lt;FQDN HOSTNAME OR IP ADDRESS&gt; to the actual fully qualified domain
    hostname or IP address.</p>
    <p>NOTE: You must perform the entire procedure before closing the terminal
    to ensure the variable export persists.</p>
    </div>
    <div class="section" id="running-the-aen-compute-installer">
    <h2><a class="toc-backref" href="#id2">Running the AEN compute installer</a><a class="headerlink" href="#running-the-aen-compute-installer" title="Permalink to this headline">¶</a></h2>
    <p>Run:</p>
    <div class="highlight-bash"><div class="highlight"><pre><span></span>sudo -E ./aen-compute-4.1.3-Linux-x86_64.sh -w <span class="nv">$AEN_SERVER</span>
    ...
    ...
    <span class="nv">PREFIX</span><span class="o">=</span>/opt/wakari/wakari-compute
    Logging to /tmp/wakari_compute.log
    Checking server name
    ...
    ...
    Initial clone of root environment...
    Starting Wakari daemons...
    installation finished.
    Do you wish the installer to prepend the wakari-compute install location
    to PATH in your /root/.bashrc ? <span class="o">[</span>yes<span class="p">|</span>no<span class="o">]</span>
    <span class="o">[</span>no<span class="o">]</span> &gt;&gt;&gt; yes
    </pre></div>
    </div>
    </div>
    <div class="section" id="configuring-your-compute-node-s">
    <h2><a class="toc-backref" href="#id3">Configuring your compute node(s)</a><a class="headerlink" href="#configuring-your-compute-node-s" title="Permalink to this headline">¶</a></h2>
    <p>Once installed, you must configure the compute launcher on your server:</p>
    <ol class="arabic">
    <li><p class="first">In your browser, go to your AEN server.</p>
    </li>
    <li><p class="first">Log in as the AEN_SRVC_ACCT user.</p>
    </li>
    <li><p class="first">In the AEN navigation bar, click Admin to open the Admin
    Settings page.</p>
    </li>
    <li><p class="first">In the <strong>Providers</strong> menu, select Enterprise Resources:</p>
    <div class="figure">
    <a class="reference internal image-reference" href="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_enterpriseresources.png"><img alt="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_enterpriseresources.png" src="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_enterpriseresources.png" style="width: 50%;" /></a>
    </div>
    <div class="line-block">
    <div class="line"><br /></div>
    </div>
    </li>
    <li><p class="first">Click the Add Resource button to open the new resource form.</p>
    </li>
    <li><p class="first">Select the data center to associate this compute node with.</p>
    <div class="figure">
    <a class="reference internal image-reference" href="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_er_addresource.png"><img alt="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_er_addresource.png" src="../../../../_images/ae-notebooks/4.1.3/aen-admin-admin_er_addresource.png" style="width: 50%;" /></a>
    </div>
    <div class="line-block">
    <div class="line"><br /></div>
    </div>
    </li>
    <li><p class="first">In the URL box, type: <code class="docutils literal"><span class="pre">http://$AEN_COMPUTE:5002</span></code>.</p>
    <p>NOTE: If the compute launcher is located on the same box as
    the gateway, we recommended that you type
    <code class="docutils literal"><span class="pre">http://localhost:5002</span></code> instead.</p>
    </li>
    <li><p class="first">Type a Name and Description for the compute node.</p>
    </li>
    <li><p class="first">Click the Add Resource button to save the changes.</p>
    </li>
    </ol>
    <p>Your AEN compute node is configured.</p>
    </div>
    <div class="section" id="what-s-next">
    <h2><a class="toc-backref" href="#id4">What&#8217;s next</a><a class="headerlink" href="#what-s-next" title="Permalink to this headline">¶</a></h2>
    <p><a class="reference internal" href="config-conda-use-local-repository.html"><span class="doc">Configure conda to use your local on-site AEN repository</span></a>.</p>
    </div>
