<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Dave,<BR>
We use crossmnt and simply modified the code where the mount options are hard coded to include crossmnt. That part works well.<BR>
We have a reserved instance as our master node started from a reserved instance as our headnode. You could avoid that part and startup/shutdown the master node.<BR>
Regarding spots etc. we encounter the same issues as you and our solution is to write data to the crossmounted volumes. If a spot goes down due to price, sge takes care of the rest, requeing the jobs. Then we start more nodes. This is ok for a an "embarrasingly parallel" architecture with 10,000s of short running jobs, less good for longer running job environments.<BR>
Anyhow, our setup works very well for what we do (bioinformatics) although I can see what you suggest would be even better.<BR>
Ed<BR>
<BR> <BR>
<DIV>
<HR id=stopSpelling>
Date: Tue, 27 May 2014 10:46:00 -0400<BR>From: dave31415@gmail.com<BR>To: StarCluster@mit.edu<BR>Subject: [StarCluster] Plugin for mounting disks properly and easily<BR><BR>
<DIV dir=ltr>Hi,
<DIV>I just started using star cluster. It's fantastic. </DIV>
<DIV><BR></DIV>
<DIV>One issue I am seeing though is that there is some difficulty getting disks up and mounted in a reasonable place. I was wondering if anyone has written a plugin for handling this. I have some work-arounds in terms of a quick and dirty plugin but I don't know how general purpose it would be. </DIV>
<DIV><BR></DIV>
<DIV>What I would like is the following:</DIV>
<DIV><BR></DIV>
<DIV>I want to use EBS volumes for everything except for scratch space as I want to be able to shutdown (to save money) and bring back up just as if it were non-virtual hardware even with spot instances. I want it to survive (no persisted data loss) having my spot instances being seized due to a spot price surge. I believe this is possible. I am wrong? </DIV>
<DIV><BR></DIV>
<DIV>I would like /home NFS cross-mounted EBS. </DIV>
<DIV><BR></DIV>
<DIV>I'd like a "restart" command to find the right EBS volumes and mount them in the usual places. In the case of a fresh "start", I'd like it to create new EBS volumes. I believe the current EBS volume attachment functionality (in config file), assumes that they already exists and that you know their id. </DIV>
<DIV><BR></DIV>
<DIV>I believe that when you change instance types from say r3.2xlarge to m3.xlarge, the storage devices (/dev/xdvv etc) change names so this requires some knowledge of what the devices will be names for each instance. </DIV>
<DIV><BR></DIV>
<DIV>Also, I want to avoid over-mounting a device on a directory with files and subdirectories inside. </DIV>
<DIV><BR></DIV>
<DIV>I can probably do all of this with a DIY solution but I figured everyone must be dealing with similar issues. Is anyone working on a general plugin for this?</DIV>
<DIV><BR></DIV>
<DIV>I can imagine a simple plugin (similar to an stab file) that looks like this in the config file</DIV>
<DIV>[volumesetup]</DIV>
<DIV>/home 100GB cross</DIV>
<DIV>/data 100GB cross</DIV>
<DIV>/hdfs1 200GB separate</DIV>
<DIV>/hdfs2 200GB separate</DIV>
<DIV><BR></DIV>
<DIV>with the remaining local storage being automatically assigned to /scratch1 /scratch2 etc depending on the number of partitions. </DIV>
<DIV><BR></DIV>
<DIV>Anyone have any ideas of suggestions?</DIV>
<DIV>Dave</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV> </DIV></DIV><BR>_______________________________________________ StarCluster mailing list StarCluster@mit.edu http://mailman.mit.edu/mailman/listinfo/starcluster</DIV> </div></body>
</html>