Locked History Actions

Diff for "CloudMan/GettingStarted"

Differences between revisions 4 and 5
Revision 4 as of 2015-08-10 15:28:59
Size: 4007
Editor: EnisAfgan
Comment:
Revision 5 as of 2015-08-10 15:41:29
Size: 4053
Editor: EnisAfgan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
0.1 For the case of Amazon, you need to [[http://aws.amazon.com/|register here]] for an Amazon Web Services (AWS) account.  1. For the case of Amazon, you need to [[http://aws.amazon.com/|register here]] for an Amazon Web Services (AWS) account.
Line 14: Line 14:
0.2 Once your account has been approved by Amazon (note that this may take up to one business day), log into [[https://console.aws.amazon.com/console|AWS Management Console]].  1. Once your account has been approved by Amazon (note that this may take up to one business day), log into [[https://console.aws.amazon.com/console|AWS Management Console]].
Line 16: Line 16:
0.3 Next, it's necessary to create the API access credentials. Do this by creating an IAM user: click on ''Services'' → ''IAM'' → ''Users'' → ''Create New Users''. Give the user a name (e.g., ''galaxy_cloudman'') and click ''Create''. Once created, make a note of and download the API access credentials. Keep these credentials safe because they are all that is required to use your cloud account.  1. Next, it's necessary to create the API access credentials. Do this by creating an IAM user: click on ''Services'' → ''IAM'' → ''Users'' → ''Create New Users''. Give the user a name (e.g., ''galaxy_cloudman'') and click ''Create''. Once created, make a note of and download the API access credentials. Keep these credentials safe because they are all that is required to use your cloud account.
Line 25: Line 25:
0.4 Attach permissions to the created IAM user by selecting the newly created user, clicking on ''Permissions'' in the user properties pane followed by a click on ''Attach User Policy'' button. Select the ''!AdministratorAccess'' policy and ''Attach'' it.  1.#4 Attach permissions to the created IAM user by selecting the newly created user, clicking on ''Permissions'' in the user properties pane followed by a click on ''Attach User Policy'' button. Select the ''!AdministratorAccess'' policy and ''Attach'' it.
Line 35: Line 35:
1.1 Head to the Cloud Launch application at [[https://launch.usegalaxy.org/launch|launch.usegalaxy.org/launch]] and fill the form with the required information. Here, use the access credentials created in the previous step (i.e., for the ''access'' and ''secret key'' fields). Give the cluster a name and protect access to it via a self-chosen password. You can also choose the type of cluster to configure here - see [[CloudMan/ClusterTypes|this page]] for a description of the available options.  1. Head to the Cloud Launch application at [[https://launch.usegalaxy.org/launch|launch.usegalaxy.org/launch]] and fill the form with the required information. Here, use the access credentials created in the previous step (i.e., for the ''access'' and ''secret key'' fields). Give the cluster a name and protect access to it via a self-chosen password. You can also choose the type of cluster to configure here - see [[CloudMan/ClusterTypes|this page]] for a description of the available options.
Line 41: Line 41:
1.2 Download the ssh key from the resulting page. This key allows you to ''ssh'' into the instance via the command prompt without a password. Note that this key is available for download only the very first time you use a given cloud account. If you have missed to download the key, delete the key from within the cloud's console (by default, called ''cloudman_keypair'') and it will be automatically recreated the next time you start a cluster.  1.#2 Download the ssh key from the resulting page. This key allows you to ''ssh'' into the instance via the command prompt without a password. Note that this key is available for download only the very first time you use a given cloud account. If you have missed to download the key, delete the key from within the cloud's management console (by default, called ''cloudman_keypair'') and it will be automatically recreated the next time you start a cluster.
Line 43: Line 43:
1.3 Wait for the cluster to start - it will take a couple of minutes. Once it has started, a link to the !CloudMan console will be shown.  1. Wait for the cluster to start - it will take a couple of minutes. Once it has started, a link to the !CloudMan console will be shown.
Line 47: Line 47:
After the cluster has started, it will take a few more minutes for all the applications to start. A popup message window will be shown when the cluster is ready for use. At that point, click ''Access Galaxy'' and start using Galaxy. You will probably want to register a new account first - after all, this is your own cluster. After the cluster has started, it will take a few more minutes for all the applications to start. A popup message window will be shown when the cluster is ready for use. At that point, click ''Access Galaxy'' and start using Galaxy. You will probably want to [[https://vimeo.com/75925027|register a new account]] first - after all, this is your own cluster.

CloudMan

Getting Started with Galaxy on the Cloud

This getting started is for non-technical users who are interested in creating their own Galaxy on the Cloud. By following this getting started, you’ll learn fundamental process of starting your own cloud cluster with Galaxy. It takes about 10 minutes to complete.

Step 0: Get your cloud credentials

Before you can start using cloud resources, you need to get your API access credentials for the given cloud. This step needs to be done only once.

  1. For the case of Amazon, you need to register here for an Amazon Web Services (AWS) account.

  2. Once your account has been approved by Amazon (note that this may take up to one business day), log into AWS Management Console.

  3. Next, it's necessary to create the API access credentials. Do this by creating an IAM user: click on ServicesIAMUsersCreate New Users. Give the user a name (e.g., galaxy_cloudman) and click Create. Once created, make a note of and download the API access credentials. Keep these credentials safe because they are all that is required to use your cloud account.

  http://i.imgur.com/PKLI8Gh.png http://i.imgur.com/IxMqWkl.png http://i.imgur.com/yFL6QRA.png http://i.imgur.com/G81G4Cq.png
  1. Attach permissions to the created IAM user by selecting the newly created user, clicking on Permissions in the user properties pane followed by a click on Attach User Policy button. Select the AdministratorAccess policy and Attach it.

http://i.imgur.com/xSMM43X.png http://i.imgur.com/2G2UXf6.png

Step 1: Start your cluster

In this step, we will create a new cluster by launching a virtual server in the cloud.

  1. Head to the Cloud Launch application at launch.usegalaxy.org/launch and fill the form with the required information. Here, use the access credentials created in the previous step (i.e., for the access and secret key fields). Give the cluster a name and protect access to it via a self-chosen password. You can also choose the type of cluster to configure here - see this page for a description of the available options.

http://i.imgur.com/zf9mzXf.png
  1. Download the ssh key from the resulting page. This key allows you to ssh into the instance via the command prompt without a password. Note that this key is available for download only the very first time you use a given cloud account. If you have missed to download the key, delete the key from within the cloud's management console (by default, called cloudman_keypair) and it will be automatically recreated the next time you start a cluster.

  2. Wait for the cluster to start - it will take a couple of minutes. Once it has started, a link to the CloudMan console will be shown.

Step 2: Access Galaxy (and other services)

After the cluster has started, it will take a few more minutes for all the applications to start. A popup message window will be shown when the cluster is ready for use. At that point, click Access Galaxy and start using Galaxy. You will probably want to register a new account first - after all, this is your own cluster.


Depending on your interest, the documentation contains a wealth of information. Here are some places that might interest you: