The root size for the worker nodes doesn't matter. The only thing relevant to Galaxy here are the available compute units and memory. The only storage and working space used is actually attached to the master node (the EBS volume you configure at initial launch) and shared over NFS with the workers. If you find yourself needing more space, you can expand this volume through the cloudman UI if you want.
-Dannon
Sun, Wenping [USA] wrote:
.sanitized-message p.MsoNormal, .sanitized-message li.MsoNormal, .sanitized-message div.MsoNormal { margin : 0in; margin-bottom : .0001pt; font-size : 11.0pt; font-family : "Calibri","sans-serif"; } .sanitized-message a:link, .sanitized-message span.MsoHyperlink { color : blue; text-decoration : underline; } .sanitized-message a:visited, .sanitized-message span.MsoHyperlinkFollowed { color : purple; text-decoration : underline; } .sanitized-message span.EmailStyle17 { font-family : "Calibri","sans-serif"; color : windowtext; } .sanitized-message .MsoChpDefault { font-family : "Calibri","sans-serif"; } .sanitized-message div.WordSection1 { }
Dear Galaxy users,
I created galaxy instance using galaxy ami the first time. When I re- launch via cloudlaunch site the 2nd time, I have question on adding cluster nodes. There are several pull-down options for the nodes type, no matter which type I choose, they always generate nodes with only 15gb. Is there other option I can have option to define the root space for the nodes?
Thank you, Kathryn ___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at: