You’ll be renting a computer from Jetstream/XSEDE, an academic version of Cloud Computing (think, Amazon Web Services [AWS]). We have an “allocation” of compute resources from Jetstream for this workshop.
Most of the time, your instance will run Linux. Here we’ll use the Ubuntu Linux operating system.
Pros (big):
Cons (small):
wget to import files from a URL (e.g., Dropbox, box.com, web site).If adding SSH keys for secure copy (SCP) to get files off the server at the end of the run – need to add the keys before launching the instance.
Adding SSH keys to the Jetstream Atmosphere environment
To log in from your terminal into the Atmosphere instance, you need to create SSH key-pair and add them to your Jetstream account.
Open terminal and run cd ~/.ssh
In that directory, use ls to check if you have a file named “id_rsa.pub”
If you do, skip to Add SSH key to Atmosphere. Otherwise, run ssh-keygen -t rsa to generate key-pair.
Following prompt will show. If you wish to use the name id_rsa, press Enter. However, if you have multiple keys for different hosts, you may write a specific filename to store your new key.
Generating public/private rsa key pair.
Enter file in which to save the key pair(/Users/emanuelburgos/.ssh/id_rsa): When prompt for passphrase, press Enter to leave empty. Press again for second vaidation
Enter passphrase (empty for no passphrase):Once key is created, use cat id_rsa.pub (or whatever filename was used) to print the file’s contents to the terminal. Highlight and copy the key including the ssh-rsa header and client address at the bottom.
ssh-rsa AAAAB3NzaC1yc2EJBXEAADAQABAAABAQCnER7CFJ
+gGzC1atde5QNos5IdgbFZa6jILA5xTLgiHt8kpNo5w9JFwkHgY4/BDVCn0rubYP
KXw8NiJhg+/4pjcjenjc762TCtc7tye0QNonOY2ysd7YyI1S7Xhbrv
+s9Mq/QYZjkdtTOMbvSTQwvzTHgOPCIaAWtLT/0cn3AehksDfuFc0AjrxKHCUbtf
f9tZhJnKXpWZ0HC6GStgeahsY78PR7NlIoW6xoQAVxfccYflptY3KAHNs
+NLPJzYuD7JoqZvzG5k1TjlDGIDNhov+xF0aet
+A8hU41CWDvCWuRt3xYiwpsXv0dGDZbxvVQZ5C04S/Wj09FGsMw03LX33f9
client@address.something
Finally, read Adding SSH key to Atmosphere.
+ to add a new ssh key.Follow these instructions from the DIB Lab with the following changes:
s1.large (CPU: 10, Mem: 30 GB, Disk: 120 GB, Disk: 120 GB root), but an m1.medium instance will likely work too.Changes in the instance can take up to 15 minutes to fully take effect.
You must delete the instance to fully stop using resources.
“Your instance will be shut down and all data will be permanently lost!”
Can Suspend (think “Sleep” on your laptop) or Stop (think “Shutdown”) an instance if you want to save the data temporarily and return to it, but have to remember to return to it and then to Delete.
If you want to shutdown your instance and return to it much later, consider “Shelve” as an option.
More info on these instances and on troubleshooting deployment
Click on the instance and, once it is running, open the “Web Shell”. This provides a web interface to the instance’s command line.
CTL-ALT(CMD)-SHIFT opens or closes the sidebar.
Copy & Paste:
File Transfer: