Thanks for the reply Enis,
I had some off-list discussion with Simon Gladman about this. Simon
indicated it seems that OpenStack security groups are not propagating to
worker nodes at startup. Manually configuring the worker node security
group and then rebooting the master appears to be a
Hi all, I'm new to CloudMan, and trying to launch a cluster via GVL (3
or 4) on NeCTAR.
I'm able to get a head node running without trouble via
launch.genome.edu.au, but launching worker nodes from the CloudMan
interface appears to fail. CloudMan reboots the worker repeatedly before
giving up. I
Hi Enis,
thank you. I will try it next time I recreate the cluster.
I have some more things:
A) I wanted to tell you that I did the update of the galaxyFS
with the playbook, by using the role cm.filesystem only.
It worked - thanks!
B) How could I mount another volume to the upstarting
A) I wanted to tell you that I did the update of the galaxyFS
with the playbook, by using the role cm.filesystem only.
It worked - thanks!
Excellent!
B) How could I mount another volume to the upstarting cluster?
- name: stuff
snap_id: snap-xyz
Would that work?
E.g when I
Hi Enis,
I am trying to launch my cloudman instance with this launcher again:
https://launch.usegalaxy.org/launch
You created the flavor for me because it wouldn't load my
galaxyIndices from the snaps.yaml in my default bucket.
I thought, this problem was fixed, but it still creates a
