Anaconda
This project installs Anaconda within an SGE environment
Pre-Requisites
This sample requires the following:
- CycleCloud must be installed and running.
- If this is not the case, see the CycleCloud QuickStart Guide for assistance.
- The CycleCloud CLI must be installed and configured for use.
- You must have access to log in to CycleCloud.
- You must have access to upload data and launch instances in your chosen Cloud Provider account.
- You must have access to a configured CycleCloud "Locker" for Project Storage (Cluster-Init and Chef).
- Optional: To use the cyclecloud project upload <locker> command, you must have a Pogo configuration file set up with write-access to your locker.
- You may use your preferred tool to interact with your storage "Locker" instead.
NOTE:
The instructions in this guide assume the use of Amazon Web Services for the Cloud Provider account.
Usage
A. Configuring the Project
The first step is to configure the project for use with your storage locker:
Open a terminal session with the CycleCloud CLI enabled.
Switch to the Anaconda sample directory.
Run
cyclecloud project add_target my_locker
(assuming the locker is named "my_locker"). The locker name will generally be the same as the cloud provider you created when configuring CycleCloud. The expected output looks like this::$ cyclecloud project add_target my_locker Name: anaconda Version: 1.0.0 Targets: my_locker: {'default': 'true', 'is_locker': 'true'}NOTE: You may call add_target as many times as needed to add additional target lockers.
B. Deploying the Project
To upload the project (including any local changes) to your target locker, run the cyclecloud project upload command from the project directory. The expected output looks like this::
$ cyclecloud project upload Sync completed!
IMPORTANT
For the upload to succeed, you must have a valid Pogo configuration for your target Locker.
C. Importing the Cluster Template
To import the cluster:
Open a terminal session with the CycleCloud CLI enabled.
Switch to the Anaconda directory.
Run
cyclecloud import_template SGE-Anaconda -f templates/sge-anaconda.txt
. The expected output looks like this::$ cyclecloud import_template SGE-Anaconda -f templates/sge-anaconda.txt Importing template SGE-Anaconda.... ---------------------- Anaconda : *template* ---------------------- Keypair: $keypair Cluster nodes: master: off Total nodes: 1
D. Creating a Anaconda Cluster
- Log in to your CycleCloud from your browser.
- Click the "Clusters" to navigate to the CycleCloud "Clusters" page, if you are not already there.
- Click the "+" button in the "Clusters" frame to create a new cluster.
- In the cluster creation page, click on the SGE-Anaconda cluster icon.
- At a minimum, select the Cloud Provider Credentials to use and enter a Name for the cluster.
- Click the "Start" button.
E. Starting and Stopping the Anaconda Cluster
- Select the newly created Anaconda cluster from the Clusters frame on the CycleCloud "Clusters" page
- To start the cluster, click the Start link in the cluster status frame.
- Later, to stop a started cluster, click the Terminate link in the cluster status frame.
F. Testing the Anaconda Cluster
1. Start the cluster and log in to master
.
$ cyclecloud connect master
2. Create an environment and install BioPython
$ cyclecloud connect -c anaconda-test master [cyclecloud@ip-10-142-234-201 ~]$ conda create --name snowflakes biopython [cyclecloud@ip-10-142-234-201 ~]$ activate snowflakes
# Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.