Table of Contents


Back

Cloud Or Not?

There is a lot of buzz about cloud computing. Recently, this has spilled over into the HPC world. There are private and public clouds. And private clouds at external organization or internal to your own organization. I do not have the gist of it down yet, but this page explores the option: can or should we consider HPC cloud for spending our $298K NSF award on or stay the course buying new hardware?

About Us

First we need to assess our usage of our clusters and if the cloud can support that. We also need to stress that we are a small liberal arts college, primarily undergraduate, with less than 3,000 students and perhaps 450 active faculty. We do not need to do cloud computing because we're going to scale upwards to 10,000 nodes. We also have a relatively small cluster user base (50 accounts), representing many different interests groups as opposed to one large community using a small set of tools.

As I like to tell vendors whom quote me impressive statistics like “1,500 HPC users across 17 buildings mostly doing the same thing, all tied together with their HPC solution” … we have 50 users in 2 buildings all doing different things.

Usage #1

Usage #2

If you follow this Queue Usage link you can observe how we use the compute nodes by queue. Notice that we do have jobs in pending stages while resources are available. So the question becomes, how do we leverage those resources better?

Clusters

The current problems we encounter are:

Our expectations are that if we buy new hardware we expect to obtain somewhere between 300-512 job slots with say $250K, with 3 year support build in and then we do-it-ourselves during next 3 years, and at the end of 6 years consider the hardware “used up”.

Cloud

My understanding of a private cloud at another, remote facility and the [dis]advantages of it are:

Qs


Back