- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with galaxy
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
This module sets up a Galaxy server according to the specific requirements of the University of Luxembourg's HPC group and the LCSB.
So far it only works on Debian wheezy.
This is not a generally applicable puppet module that can be used as is. It contains a lot of very specific settings for the ULHPC cluster environment. Please regard it rather as a documentation of the steps to set up a production Galaxy server.
The module sets up a Galaxy server with four load-balanced web servers and four job runners. It uses Apache2 as a proxy server and a PostGreSQL database.
- creates 'galaxy' user and group
- PostGreSQL: creates 'galaxy' and 'galaxytools' databases with user 'galaxy' as the owner
- Apache2: creates a virtual host
- /etc/init.d/galaxy
- packages: installs gcc, python, mercurial, tar and openssl
This module depends on
For a simple standard setup just set the postgresql_password to a secure password:
class { 'galaxy':
postgresql_password => 'securepassword',
}
It suffices to declare the galaxy
class, everything else is automatically included. The $postgresql_password
should definitely be changed for a production server, as well as the $id_secret
. The $directory
is fine with the default setting.
Does all the work.
This class sets the default parameters for the Galaxy puppet module.
This class sets up the directory structure for the project directories and mounts the galaxy project directory.
This defined resource type mounts a project directory read-only.
Only tested on Debian wheezy.