Install AEN Compute (AEN 4.1.2)
===============================

.. raw:: html

    <p>This is where projects are stored and run. Adding multiple AEN
    Compute Nodes allows you to scale-out horizontally to increase
    capacity. Projects can be created on individual Compute Nodes to spread
    the load.</p>
    <p>These procedures assume that you have already performed the <a class="reference internal" href="install-prep.html"><span class="doc">Installation preparation</span></a>,
    <a class="reference internal" href="install-server.html"><span class="doc">Install AEN Server</span></a> and <a class="reference internal" href="install-gateway.html"><span class="doc">Install AEN Gateway</span></a> procedures.</p>
    <div class="section" id="set-variables-and-change-permissions">
    <h2>Set variables and change permissions<a class="headerlink" href="#set-variables-and-change-permissions" title="Permalink to this headline">¶</a></h2>
    <p>In the script below, change <code class="docutils literal"><span class="pre">&lt;FQDN</span> <span class="pre">HOSTNAME</span> <span class="pre">OR</span> <span class="pre">IP</span> <span class="pre">ADDRESS&gt;</span></code> to the actual
    fully qualified domain hostname or IP address.</p>
    <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">export</span> <span class="n">AEN_SERVER</span><span class="o">=&lt;</span><span class="n">FQDN</span> <span class="n">HOSTNAME</span> <span class="n">OR</span> <span class="n">IP</span> <span class="n">ADDRESS</span><span class="o">&gt;</span> <span class="c1"># Use the real FQDN</span>
    <span class="n">chmod</span> <span class="n">a</span><span class="o">+</span><span class="n">x</span> <span class="n">aen</span><span class="o">-*.</span><span class="n">sh</span>                 <span class="c1"># Set installer to be executable</span>
    </pre></div>
    </div>
    <p>NOTE: You must perform the entire procedure before closing the terminal
    to ensure the variable export persists.</p>
    </div>
    <div class="section" id="run-aen-compute-installer">
    <h2>Run AEN Compute installer<a class="headerlink" href="#run-aen-compute-installer" title="Permalink to this headline">¶</a></h2>
    <div class="highlight-default"><div class="highlight"><pre><span></span>sudo -E ./aen-compute-4.1.2-Linux-x86_64.sh -w $AEN_SERVER
    ...
    ...
    PREFIX=/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 ? [yes|no]
    [no] &gt;&gt;&gt; yes
    </pre></div>
    </div>
    </div>
    <div class="section" id="configure-aen-compute">
    <h2>Configure AEN Compute<a class="headerlink" href="#configure-aen-compute" title="Permalink to this headline">¶</a></h2>
    <p>Once installed, you need to configure the Compute Launcher on AEN Server.</p>
    <ol class="arabic simple">
    <li>Point your browser at the AEN Server</li>
    <li>Login as the <code class="docutils literal"><span class="pre">AEN_SRVC_ACCT</span></code> user</li>
    <li>Click the Admin link in the top navbar</li>
    <li>Click Enterprise Resources in the left navbar</li>
    <li>Click Add Resource</li>
    <li>Select the correct (probably the only) Data Center to associate with this
    Compute Node</li>
    <li>Enter the fully-qualified domain name here.</li>
    </ol>
    <p>Note: If the Compute Launcher is located on the same box as the Gateway,
    we recommend using <code class="docutils literal"><span class="pre">http://localhost:5002</span></code> for the URL value.</p>
    <ol class="arabic simple" start="8">
    <li>Add a Name and Description for the Compute Node</li>
    <li>Click the Add Resource button to save the changes.</li>
    </ol>
    </div>
    <div class="section" id="configure-conda-to-use-local-on-site-anaconda-repo">
    <h2>Configure conda to use local on-site Anaconda repo<a class="headerlink" href="#configure-conda-to-use-local-on-site-anaconda-repo" title="Permalink to this headline">¶</a></h2>
    <p>This integrates Anaconda Enterprise Notebooks to use a local on-site Anaconda
    Enterprise Repository server instead of Anaconda.org.</p>
    <div class="section" id="edit-the-condarc-on-the-compute-node">
    <h3>Edit the condarc on the Compute Node<a class="headerlink" href="#edit-the-condarc-on-the-compute-node" title="Permalink to this headline">¶</a></h3>
    <p>The <code class="docutils literal"><span class="pre">condarc</span></code> is the conda runtime configuration file.</p>
    <p>NOTE: If there are some channels below that you haven&#8217;t mirrored,
    you should remove them from the configuration.</p>
    <p>NOTE: Change <code class="docutils literal"><span class="pre">&lt;your</span> <span class="pre">Anaconda</span> <span class="pre">Repository</span> <span class="pre">name&gt;</span></code> in the following script
    to the actual name of your repository before running.</p>
    <div class="highlight-default"><div class="highlight"><pre><span></span><span class="c1">#/opt/wakari/anaconda/.condarc</span>
    <span class="n">channels</span><span class="p">:</span>
        <span class="o">-</span> <span class="n">defaults</span>

    <span class="n">create_default_packages</span><span class="p">:</span>
        <span class="o">-</span> <span class="n">anaconda</span><span class="o">-</span><span class="n">client</span>
        <span class="o">-</span> <span class="n">ipykernel</span>

    <span class="c1"># Default channels are needed for when users override the system .condarc</span>
    <span class="c1"># with ~/.condarc. This ensures that &quot;defaults&quot; map to your Anaconda Repository and not</span>
    <span class="c1"># repo.continuum.io</span>
    <span class="n">default_channels</span><span class="p">:</span>
        <span class="o">-</span> <span class="n">http</span><span class="p">:</span><span class="o">//&lt;</span><span class="n">your</span> <span class="n">Anaconda</span> <span class="n">Repository</span> <span class="n">name</span><span class="o">&gt;</span><span class="p">:</span><span class="mi">8080</span><span class="o">/</span><span class="n">conda</span><span class="o">/</span><span class="n">anaconda</span>
        <span class="o">-</span> <span class="n">http</span><span class="p">:</span><span class="o">//&lt;</span><span class="n">your</span> <span class="n">Anaconda</span> <span class="n">Repository</span> <span class="n">name</span><span class="o">&gt;</span><span class="p">:</span><span class="mi">8080</span><span class="o">/</span><span class="n">conda</span><span class="o">/</span><span class="n">wakari</span>
        <span class="o">-</span> <span class="n">http</span><span class="p">:</span><span class="o">//&lt;</span><span class="n">your</span> <span class="n">Anaconda</span> <span class="n">Repository</span> <span class="n">name</span><span class="o">&gt;</span><span class="p">:</span><span class="mi">8080</span><span class="o">/</span><span class="n">conda</span><span class="o">/</span><span class="n">r</span><span class="o">-</span><span class="n">channel</span>

    <span class="c1"># Note:  You must add the &quot;conda&quot; subdirectory to the end</span>
    <span class="n">channel_alias</span><span class="p">:</span> <span class="n">http</span><span class="p">:</span><span class="o">//&lt;</span><span class="n">your</span> <span class="n">Anaconda</span> <span class="n">Repository</span> <span class="n">name</span><span class="o">&gt;</span><span class="p">:</span><span class="mi">8080</span><span class="o">/</span><span class="n">conda</span>
    </pre></div>
    </div>
    </div>
    <div class="section" id="configure-anaconda-client">
    <h3>Configure Anaconda client<a class="headerlink" href="#configure-anaconda-client" title="Permalink to this headline">¶</a></h3>
    <p>Anaconda client lets users work with the Anaconda Repository from the command-line,
    to search for packages, login, upload packages, etc.  The
    command below sets this value globally for all users.</p>
    <p>Run the following command filling in the proper repository URL.
    This command requires <code class="docutils literal"><span class="pre">sudo</span></code> as the config file is written to the root file system:
    <code class="docutils literal"><span class="pre">/etc/xdg/binstar/config.yaml</span></code>. This sets the default config for <code class="docutils literal"><span class="pre">anaconda-client</span></code>
    for all users on compute node.</p>
    <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">sudo</span> <span class="o">/</span><span class="n">opt</span><span class="o">/</span><span class="n">wakari</span><span class="o">/</span><span class="n">anaconda</span><span class="o">/</span><span class="nb">bin</span><span class="o">/</span><span class="n">anaconda</span> <span class="n">config</span> <span class="o">--</span><span class="nb">set</span> <span class="n">url</span> <span class="n">http</span><span class="p">:</span><span class="o">//&lt;</span><span class="n">your</span> <span class="n">Anaconda</span> <span class="n">Repository</span><span class="o">&gt;</span><span class="p">:</span><span class="mi">8080</span><span class="o">/</span><span class="n">api</span> <span class="o">-</span><span class="n">s</span>
    </pre></div>
    </div>
    </div>
    </div>
    <div class="section" id="repeat-compute-node-install-procedure-with-additional-nodes-as-necessary">
    <h2>Repeat compute node install procedure with additional nodes as necessary<a class="headerlink" href="#repeat-compute-node-install-procedure-with-additional-nodes-as-necessary" title="Permalink to this headline">¶</a></h2>
    <p>One Data Center can support numerous nodes. If you need to configure
    additional Compute Nodes, run through this procedure for each Compute
    Node you wish to stand up.</p>
    </div>
    <div class="section" id="finish">
    <h2>Finish<a class="headerlink" href="#finish" title="Permalink to this headline">¶</a></h2>
    <p><strong>Congratulations! You&#8217;ve successfully installed and configured
    Anaconda Enterprise Notebooks.</strong></p>
    </div>
    <div class="section" id="next-steps">
    <h2>Next steps<a class="headerlink" href="#next-steps" title="Permalink to this headline">¶</a></h2>
    <p>The following optional install procedures may need to be performed,
    depending on how you set up your Data Center:</p>
    <ul class="simple">
    <li><a class="reference internal" href="option-config.html"><span class="doc">Optional configuration</span></a></li>
    <li><a class="reference internal" href="customization.html"><span class="doc">Sudo configuration</span></a></li>
    <li><a class="reference internal" href="ldap.html"><span class="doc">LDAP configuration</span></a></li>
    <li><a class="reference internal" href="ssl.html"><span class="doc">SSL</span></a></li>
    <li><a class="reference internal" href="sso.html"><span class="doc">Single sign on</span></a></li>
    </ul>
    <p>Additional post-install information:</p>
    <ul class="simple">
    <li><a class="reference internal" href="installation_update.html"><span class="doc">Upgrading Anaconda Enterprise Notebooks</span></a></li>
    <li><a class="reference internal" href="uninstall.html"><span class="doc">Uninstall</span></a></li>
    <li><a class="reference internal" href="release.html"><span class="doc">Release notes</span></a></li>
    </ul>
    </div>
