<div dir="ltr">Hello, I believe I have found the error of my ways. It seems I need to attempt this initial mounting with a new cluster - before I was stopping, then changing the config, then starting, and the mount was never being made.<div><br></div><div>Best,</div><div><br></div><div>Don</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">---<div>Don Morton, Owner/Manager</div><div>Boreal Scientific Computing LLC</div><div>Fairbanks, Alaska USA</div><div><a href="http://www.borealscicomp.com/" target="_blank">http://www.borealscicomp.com/</a></div><div><a href="http://www.borealscicomp.com/Miscellaneous/MortonBio/" target="_blank">http://www.borealscicomp.com/Miscellaneous/MortonBio/</a></div></div></div></div>
<br><div class="gmail_quote">On Tue, Oct 20, 2015 at 3:10 PM, Don Morton <span dir="ltr"><<a href="mailto:don.morton@borealscicomp.com" target="_blank">don.morton@borealscicomp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>I'm new to Star Cluster, and it's not clear to me if this is the appropriate forum to post "new dummy" questions. If not, please accept my apologies.</div><div><br></div><div>First, let me thank you for the great effort that has gone into this project. Wow. I've built my own MPI clusters from scratch in EC2, and boy was that tedious. This is amazing. I also tried cfncluster, but so far that appears a bit too restrictive in terms of building a custom AMI that I can use over and over again (but I might be misreading the docs there).</div><div><br></div><div>My problem at hand - try as I may, I keep failing at mounting an EBS volume to my cluster. I have a few theories I can explore via the inefficient "trial and error" approach, but I feel like my issue is probably so fundamental that someone will easily be able to point me in the right direction.</div><div><br></div><div>The instance:</div><div><br></div><div><div>id: i-b6fdea70</div><div>dns_name: N/A</div><div>private_dns_name: ip-172-31-25-191.us-west-2.compute.internal</div><div>state: stopped (User initiated (2015-10-20 02:23:53 GMT))</div><div>public_ip: N/A</div><div>private_ip: 172.31.25.191</div><div>vpc: vpc-7f99af17</div><div>subnet: subnet-7199af19</div><div>zone: us-west-2a</div><div>ami: ami-80bedfb0</div><div>virtualization: hvm</div><div>type: m3.large</div><div>groups: @sc-wrfcluster</div><div>keypair: starclusterkey</div><div>uptime: N/A</div><div>tags: alias=node001, Name=node001</div><div><br></div><div><br></div><div>The volume (yes, same availability zone):</div><div><br></div><div><div>volume_id: vol-f1942530</div><div>size: 20GB</div><div>status: available</div><div>availability_zone: us-west-2a</div><div>create_time: 2015-10-20 02:07:20</div><div>tags: Name=WRFClusterPrograms</div></div><div><br></div><div><br></div><div>Relevant excerpts of ~/.starcluster/config:</div><div><br></div><div><div>AWS_REGION_NAME = us-west-2</div><div>AWS_REGION_HOST = <a href="http://ec2.us-west-2.amazonaws.com" target="_blank">ec2.us-west-2.amazonaws.com</a></div></div><div><br></div><div>[cluster smallcluster]<br></div><div><div># ami-80bedfb0 us-west-2 starcluster-base-ubuntu-13.04-x86_64-hvm (HVM-EBS)</div><div>NODE_IMAGE_ID = ami-80bedfb0</div></div><div>NODE_INSTANCE_TYPE = m3.large<br></div><div>VOLUMES = wrfprogs<br></div><div><br></div><div><div>[volume wrfprogs]</div><div>VOLUME_ID = vol-f1942530</div><div>MOUNT_PATH = /wrfprogs</div></div><div><br></div><div><br></div><div>---------------------------------------------------------------------</div><div><br></div><div>Right now, some things I will try by trial and error, but I don't "think" they will resolve issues</div><div><br></div><div>1) My AVAILABILITY_ZONE is commented out in config, maybe I should hard code in my us-west-2a, but both the instance and volume are already in there</div><div><br></div><div>2) Maybe I should manually create the mount point /wrfprogs in my master and try again. Doubtful - the examples you provide don't suggest this is necessary</div><div><br></div><div>3) In the config file, list the volume BEFORE listing the cluster specs. Again, doubtful it will make a difference.</div><div><br></div><div>Thank you for any insight.</div><div><br></div><div>Best,</div><div><br></div><div>Don</div><div><br></div><div><br></div><div><div><div dir="ltr">---<div>Don Morton, Owner/Manager</div><div>Boreal Scientific Computing LLC</div><div>Fairbanks, Alaska USA</div><div><a href="http://www.borealscicomp.com/" target="_blank">http://www.borealscicomp.com/</a></div><div><a href="http://www.borealscicomp.com/Miscellaneous/MortonBio/" target="_blank">http://www.borealscicomp.com/Miscellaneous/MortonBio/</a></div></div></div></div>
</div></div>
</blockquote></div><br></div>