what about chaning cm.tar.gz in S3 ?
Zeeshan
On Thu, May 31, 2012 at 9:34 AM, Jorrit Boekel jorrit.boekel@scilifelab.sewrote:
Hej Zeeshan
Rebooting leads to upstart running /opt/cloudman/pkg/ec2autorun.py. This downloads a boot script, which downloads a cloudman package (cm.tar.gz), unpacks it and starts cloudman from there. This will mean a new /mnt/cm/universe.wsgi will be in place.
When cloudman starts, it attaches EBS volumes to /mnt/galaxyTools and other mount points from snapshots. The snapshots will include /mnt/galaxyTools/galaxy-central/universe_wsgi.ini.
Restarting the node will thus eradicate changes. You will have to use the persist changes-functionality to create a file persistent_data.yaml in an S3 bucket and saved snapshots. AFAIK, it saves when you terminate the session in cloudman. When instantiating a new cluster with the *same name* (important) as the old one, it will pick the persistent data from the bucket and mount your saved snapshots.
good luck, jorrit
On 05/30/2012 04:34 PM, Zeeshan Ali Shah wrote:
I tried changing both files /mnt/galaxyTools/galaxy-central/universe_wsgi.ini
and
/mnt/cm/universe_wsgi.ini.cloud
but after reboot of headnode the changes are gone .
any hint ?
Zeeshan
On Thu, May 24, 2012 at 10:30 AM, Roman Valls Guimera < brainstorm@nopcode.org> wrote:
Zeeshan, AFAIK the only settings you can set regarding this are in universe_wsgi.ini through the directives:
# Allow unregistered users to create new accounts (otherwise, they will have to # be created by an admin). allow_user_creation = True
# Email administrators when a new user account is created # You also need to have smtp_server set for this to work. new_user_email_admin = False
I have not seen a moderation system in place, but maybe you can use PDC's Plone forms for this moderation ?
Hope that helps ! Roman
24 maj 2012 kl. 10:18 skrev Zeeshan Ali Shah:
Hi, Is there any way to moderate Registration on Galaxy portal ? We are
setting up a cluster for internal users but it seems that by default registration is open for all.
Can any way we disable the registration and Moderator create users
separately ? OR Moderate the registration process ?
Zeeshan ___________________________________________________________ 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:
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:
The default cm.tar.gz is in a public bucket (https://s3.amazonaws.com/cloudman). I'm not sure whether saving persistent data would lead to a new cm.tar.gz package in your own bucket.
You could create your own bucket and put the cm.tar.gz it there. Then I think you can set in your userdata where cm.tar.gz is downloaded from. I'm not sure, but it is defined in the boot script which is also downloaded from the bucket on instance-boot.
http://wiki.g2.bx.psu.edu/CloudMan/UserData is down currently though.
cheers, jorrit
On 05/31/2012 10:39 AM, Zeeshan Ali Shah wrote:
what about chaning cm.tar.gz in S3 ?
Zeeshan
On Thu, May 31, 2012 at 9:34 AM, Jorrit Boekel <jorrit.boekel@scilifelab.se mailto:jorrit.boekel@scilifelab.se> wrote:
Hej Zeeshan Rebooting leads to upstart running /opt/cloudman/pkg/ec2autorun.py. This downloads a boot script, which downloads a cloudman package (cm.tar.gz), unpacks it and starts cloudman from there. This will mean a new /mnt/cm/universe.wsgi will be in place. When cloudman starts, it attaches EBS volumes to /mnt/galaxyTools and other mount points from snapshots. The snapshots will include /mnt/galaxyTools/galaxy-central/universe_wsgi.ini. Restarting the node will thus eradicate changes. You will have to use the persist changes-functionality to create a file persistent_data.yaml in an S3 bucket and saved snapshots. AFAIK, it saves when you terminate the session in cloudman. When instantiating a new cluster with the *same name* (important) as the old one, it will pick the persistent data from the bucket and mount your saved snapshots. good luck, jorrit On 05/30/2012 04:34 PM, Zeeshan Ali Shah wrote:I tried changing both files /mnt/galaxyTools/galaxy-central/universe_wsgi.ini and /mnt/cm/universe_wsgi.ini.cloud but after reboot of headnode the changes are gone . any hint ? Zeeshan On Thu, May 24, 2012 at 10:30 AM, Roman Valls Guimera <brainstorm@nopcode.org <mailto:brainstorm@nopcode.org>> wrote: Zeeshan, AFAIK the only settings you can set regarding this are in universe_wsgi.ini through the directives: # Allow unregistered users to create new accounts (otherwise, they will have to # be created by an admin). allow_user_creation = True # Email administrators when a new user account is created # You also need to have smtp_server set for this to work. new_user_email_admin = False I have not seen a moderation system in place, but maybe you can use PDC's Plone forms for this moderation ? Hope that helps ! Roman 24 maj 2012 kl. 10:18 skrev Zeeshan Ali Shah: > Hi, Is there any way to moderate Registration on Galaxy portal ? We are setting up a cluster for internal users but it seems that by default registration is open for all. > > Can any way we disable the registration and Moderator create users separately ? OR Moderate the registration process ? > > > Zeeshan > ___________________________________________________________ > The Galaxy User list should be used for the discussion of > Galaxy analysis and other features on the public server > at usegalaxy.org <http://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: > > http://lists.bx.psu.edu/ ___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server atusegalaxy.org <http://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: http://lists.bx.psu.edu/
Thanks Jorrit,
Zeeshan
On Thu, May 31, 2012 at 11:46 AM, Jorrit Boekel <jorrit.boekel@scilifelab.se
wrote:
The default cm.tar.gz is in a public bucket ( https://s3.amazonaws.com/cloudman). I'm not sure whether saving persistent data would lead to a new cm.tar.gz package in your own bucket.
You could create your own bucket and put the cm.tar.gz it there. Then I think you can set in your userdata where cm.tar.gz is downloaded from. I'm not sure, but it is defined in the boot script which is also downloaded from the bucket on instance-boot.
http://wiki.g2.bx.psu.edu/CloudMan/UserData is down currently though.
cheers, jorrit
On 05/31/2012 10:39 AM, Zeeshan Ali Shah wrote:
what about chaning cm.tar.gz in S3 ?
Zeeshan
On Thu, May 31, 2012 at 9:34 AM, Jorrit Boekel < jorrit.boekel@scilifelab.se> wrote:
Hej Zeeshan
Rebooting leads to upstart running /opt/cloudman/pkg/ec2autorun.py. This downloads a boot script, which downloads a cloudman package (cm.tar.gz), unpacks it and starts cloudman from there. This will mean a new /mnt/cm/universe.wsgi will be in place.
When cloudman starts, it attaches EBS volumes to /mnt/galaxyTools and other mount points from snapshots. The snapshots will include /mnt/galaxyTools/galaxy-central/universe_wsgi.ini.
Restarting the node will thus eradicate changes. You will have to use the persist changes-functionality to create a file persistent_data.yaml in an S3 bucket and saved snapshots. AFAIK, it saves when you terminate the session in cloudman. When instantiating a new cluster with the *same name* (important) as the old one, it will pick the persistent data from the bucket and mount your saved snapshots.
good luck, jorrit
On 05/30/2012 04:34 PM, Zeeshan Ali Shah wrote:
I tried changing both files /mnt/galaxyTools/galaxy-central/universe_wsgi.ini
and
/mnt/cm/universe_wsgi.ini.cloud
but after reboot of headnode the changes are gone .
any hint ?
Zeeshan
On Thu, May 24, 2012 at 10:30 AM, Roman Valls Guimera < brainstorm@nopcode.org> wrote:
Zeeshan, AFAIK the only settings you can set regarding this are in universe_wsgi.ini through the directives:
# Allow unregistered users to create new accounts (otherwise, they will have to # be created by an admin). allow_user_creation = True
# Email administrators when a new user account is created # You also need to have smtp_server set for this to work. new_user_email_admin = False
I have not seen a moderation system in place, but maybe you can use PDC's Plone forms for this moderation ?
Hope that helps ! Roman
24 maj 2012 kl. 10:18 skrev Zeeshan Ali Shah:
Hi, Is there any way to moderate Registration on Galaxy portal ? We
are setting up a cluster for internal users but it seems that by default registration is open for all.
Can any way we disable the registration and Moderator create users
separately ? OR Moderate the registration process ?
Zeeshan ___________________________________________________________ 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:
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:
galaxy-user@lists.galaxyproject.org
-
Jorrit Boekel -
Zeeshan Ali Shah