How do you connect existing EBS volumes to a fresh EC2 instance?
Hello, How do you connect existing EBS volumes to a fresh EC2 instance on Amazon? I have been starting the EC2 instance and choosing "test cluster" where the option to use EBS volume space is given (when the Galaxy cloud console starts up), since there is no place to insert my EBS volume address. This leads to Galaxy starting one 15 GB EBS volume (the other two, 10 Gb and 700 Gb, EBS volumes are not started) and I then manually tell my desired EBS volume to connect to the fresh EC2 instance. The EBS volume says it is attached to the EC2 instance, but the Galaxy cloud console shows no linkage to any "data" (in the service status row) and the disk status is "0 \ 0 (0%)". Help would greatly be appreciated. Cheers, Mo Heydarian PhD candidate The Johns Hopkins School of Medicine Department of Biological Chemistry 725 Wolfe Street 414 Hunterian Baltimore, MD 21205
Galaxy Cloudman doesn't support automatic addition of EBS volumes yet, though it is something we're looking at long term. If the volume is already in the same Availability Zone as your cloud instance, the following steps should work: • With the volume checked, click More... -> Attach Volume, select your instance and set the device (the default device name filled in to the dialog once you select your instance is acceptable). • Log in to your instance using SSH: ssh -i /path/to/your/ecs_ssh_private_key ubuntu@ec2-1-2-3-4.compute-1.amazonaws.com • Become root: sudo -i • Mount the volume: mkdir /mnt/yourVolumeName; mnt /dev/sdf /mnt/myVolumeName The volume is now mounted and should be accessible via the regular filesystem. Note that by default, this mount point won't be monitored by the cloudman admin interface. And, lastly, I haven't tried it but if you mounted it as /mnt/galaxyData (assuming based on your description that you're not using the built in galaxyData volume at all), it would probably show up as expected. -Dannon On Apr 17, 2012, at 3:51 PM, Mohammad Heydarian wrote:
Hello, How do you connect existing EBS volumes to a fresh EC2 instance on Amazon?
I have been starting the EC2 instance and choosing "test cluster" where the option to use EBS volume space is given (when the Galaxy cloud console starts up), since there is no place to insert my EBS volume address. This leads to Galaxy starting one 15 GB EBS volume (the other two, 10 Gb and 700 Gb, EBS volumes are not started) and I then manually tell my desired EBS volume to connect to the fresh EC2 instance. The EBS volume says it is attached to the EC2 instance, but the Galaxy cloud console shows no linkage to any "data" (in the service status row) and the disk status is "0 \ 0 (0%)".
Help would greatly be appreciated.
Cheers, Mo Heydarian
PhD candidate The Johns Hopkins School of Medicine Department of Biological Chemistry 725 Wolfe Street 414 Hunterian Baltimore, MD 21205
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
participants (2)
-
Dannon Baker -
Mohammad Heydarian