CloudMan's features and uses
This page talks about CloudMan, its features, and potential uses. CloudMan is a cloud manager that orchestrates and manages a cloud infrastructure allowing one to simply use the underlying infrastructure. It is primarily being used in the context of Galaxy Cloud and CloudBioLinux but it can be used for any purpose where a cluster in a cloud is desired. Read on about descriptions of specific features.

Behind the accessible and functional web interface, CloudMan allows you to access your cluster from the command line as well. You can find the exact command needed to ssh (including the current IP) on the Admin interface:

ssh command on the Admin page

(Note that CloudMan images created after 2012 allow you to also log in using the same password as you use for accessing the CloudMan web interface; simply log in as ubuntu user).

To ssh to the instance, simply start the Terminal application (or Putty on Windows) and provide the command:

ssh command

Once logged in, the cluster behaves just like any other SGE-managed cluster: submit a job using qsub <job script>:

Submit a job via qsub

Check the status of a job or the queue, use qstat -f:

 Check queue status

For ubuntu user, CloudMan stores all of the persistent data in /export/data. This directory is also shared over NFS with worker nodes and should thus be used for submitting jobs from and having the output stored there.

And there you go - a scaleable and functional compute cluster ready for anything you throw at it.

 

Tags: CLI, cluster

By default, CloudMan will configure your cloud cluster to run jobs on the head node (i.e., the master instance). This allows you to have only a single cloud instance and start using it instantly, thus minimizing the cost associated with using a cloud. However, such behavior may not always be desirable. If, for example, you have a substantial number of users or jobs being submitted, the head node may be busy running jobs and lead to poor responsiveness of user services. Alternatively, you may choose to keep a small (i.e., cheap) master instance alive at all times so users can use it whenever needed. Such instance may not have enough power to also handle user jobs though.


CloudMan enables you to toggle the master instance from running jobs. Simply go to the Admin page and click on Switch master not to run jobs and no jobs will run on the master instance:

Switch master not to run jobs

You can revert this decision at any point by clicking Switch master to run jobs. Note that if you chose to have the master instance not run any jobs, it will be necessary to have at least one worker instance to handle any jobs. Fortunately, this is also simple and automated via CloudMan's auto-scaling feature.

Tags: admin, cluster