Yes, you should be able to create your own volume and sub it into pd.yaml.
Since you want to share this across several instances, and you can't mount
an EBS volume to multiple instances, you'll definitely want to use the
snapshot method (and so, snap_id is required).
On Tue, May 14, 2013 at 10:39 AM, Rob Leclerc <robert.lecl...@gmail.com>wrote:
> We'd like to trim the the galaxyIndicies/genome directory to human and
> blastdb. As we may have several CM instances, we would like to share this
> filesystem across all instances.
> I would like to simply copy these data to a new volume and mount this
> filesystem with all our CM instances. Do I just need to rename specified
> filesystem in pd.yaml to ourGalaxyIndicies and then mount our CMs to
> /mnt/ourGalaxyIndicies/, or are their other locations I need to modify as
> well? Are the size and snap_id required?
> Rob Leclerc, PhD
> P: (US) +1-(917)-873-3037
> P: (Shanghai) +86-1-(861)-612-5469
> Personal Email: rob.lecl...@aya.yale.edu
> 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:
> To search Galaxy mailing lists use the unified search at:
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:
To search Galaxy mailing lists use the unified search at: