WORK IN PROGRESS, next update after dagobah training

Galaxy 17.09 in production, virtual machine on cloud based on Openstack

This is an example and few scripts to configure an Galaxy server in production mod on a cloud based on Openstack. Many points are customizable, but there one configuration will be show.

Galaxy

Create galaxy user and install it

First connect as root user to your new machine, then create a new user galaxy and give root Privileges

ssh root@192.XXX.XXX.XX
#Change root password
passwd root
adduser galaxy
# Choose password

# edit the sudoers file, to give galaxy root privileges
# add galaxy ALL=(ALL:ALL) ALL
visudo

Now use the script galaxy_install.sh

cd $HOME
sudo bash galaxy_install.sh

This script install : galaxy, docker, npm, node and nginx.

You should downgrade node version , because galaxy work only with <0.11. We use Node Version Manager fromlien

	#Add this to your .bashrc
	export NVM_DIR="$HOME/.nvm"
	[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm

Then execute

	wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash
	source .bashrc
	nvm install 0.10
	nvm use 0.10
    cd $GALAXY_ROOT/lib/galaxy/web/proxy/js && npm install

You can check if it work with node -v should retourn

galaxy@65mo-galaxy-prod:~$ node -v
v0.10.48

Tolshed

Create Toolshed user and install it

It's recommanded to install your toolshed on another machine.

ssh root@192.XXX.XXX.XX
#Change root password
passwd root
adduser toolshed
# Choose password

# edit the sudoers file, to give galaxy root privileges
# add toolshed ALL=(ALL:ALL) ALL
visudo

You can use the script shell

bash toolshed.ini

it will download, and copy config files.

After that start the toolshed in daemon mod

PostgreSQL

Galaxy database

Start a new machine, connect ,change root password, add user, install postgreSql and create user and database galaxy *

ssh root@192.XXX.XXX.XX
#Change root password
passwd root
adduser galaxy
apt-get update

apt-get install -y postgresql postgresql-contrib
sudo -u postgres createuser --interactive
sudo -u galaxy createdb galaxy

Now you have to give database acces to your galaxy server. You have to add in /etc/postgresql/9.5/main/pg_hba.conf :

#Type of connection		#Database		#User			#Adress							#Option connection ( don't need password in this case)

host    				galaxy          galaxy          192.XXX.XXX.XX/32               trust

And after that you have to specifiy than postgresql should accepte request from your galaxy server.

Change in /etc/postgresql/9.5/main/postgresql.conf

listen_addresses = 'localhost' -> '192.XXX.XXX.XX'

listen_addresses = 'localhost' -> '*'

for all

and restart the server

  /etc/init.d/postgresql restart

After that you have to change in $GALAXY_ROOT/config/galaxy.ini

#database_connection = sqlite:///./database/universe.sqlite?isolation_level=IMMEDIATE

database_connection = postgresql://galaxy:password@192.XXX.XXX.XX:5432/galaxy

Please refer to this ::: postgresql://username:password@localhost/mydatabase

localhost is the adress of the machine where your postgresql server is runing

Toolshed database

adduser toolshed
sudo -u postgres createuser --interactive
sudo -u toolshed createdb toolshed

Now you have to give database acces to your toolsed server. You have too add in /etc/postgresql/9.5/main/pg_hba.conf : #Type of connection #Database #User #Adress #Option connection ( don't need password in this case) host toolshed toolshed 192.XXX.XXX.XX/32 trust

And after that you have to specifiy than postgresql should accepte request from your toolshed server machine.

Change in /etc/postgresql/9.5/main/postgresql.conf

listen_addresses = 'localhost' to '192.XXX.XXX.XX'

listen_addresses = 'localhost' to '*'

for all

and restart the server

/etc/init.d/postgresql restart

After that you have to change in tool_shed.ini on the machine's toolshed

#database_connection = sqlite:///./database/community.sqlite?isolation_level=IMMEDIATE

database_connection = postgresql://toolshed:pasword@192.XXX.XXX.XX:5432/toolshed

Please refer to this ::: postgresql://username:password@localhost/mydatabase

localhost is the adress of the machine where your postgresql server is runing

and in the galaxy/config/tool_sheds_conf.xml.sample <tool_shed name="Galaxy Main Tool Shed" url="https://toolshed.g2.bx.psu.edu/"/>

Galaxy interactive environnements : Docker

You can have your Docker server and the Galaxy server on the same machine. It could be interesting in one case to launch your container on the same machine. I will present 2 cases.

⚠️⚠️In any case you have to install docker on your Galaxy server's machine. The galaxy_install.sh already did it for you.

📌 : You should pull all the image before their used, because Galaxy launch the command and if the image doesn't exists, docker will pull it, but for somes images like Jupyter it could be really long, so do it before

📌📌 Wait for the part #Mount Volume, before pull any image, or you risk to run out space your machine.

Docker on the same machine.

So you don't have to do something...

Congratulations it's complete :clap: :clap:

Refer to this [page](https://docs.galaxyproject.org/en/master/admin/interactive_environments.html)

Docker an another host

ssh root@192.XXX.XXX.XX
passwd root

adduser docker
# Choose password

# edit the sudoers file, to give galaxy root privileges
# add docker ALL=(ALL:ALL) ALL
visudo

then install docker

apt-get install -y docker.io
usermod -a -G docker $(whoami)
dockerd -H 0.0.0.0:4243

Then you have to change the config.ini file of your GIE . For example with jupyter

[main]

[docker]
command = docker -H tcp://192.XXX.XXX.XX:4243 {docker_args}
image = bgruening/docker-ipython-notebook:dev
docker_hostname = 192.XXX.XXX.XX

Mount volumes (optionnal)

To add some space to your machines you can add volumes.

Please see lien

Docker

From this

Stop docker: service docker stop. Verify no docker process is running ps faux
Double check docker really isn't running. Take a look at the current docker directory: ls /var/lib/docker/

2b) Make a backup - tar -zcC /var/lib docker > /mnt/pd0/var_lib_docker-backup-$(date +%s).tar.gz

Move the /var/lib/docker directory to your new partition: mv /var/lib/docker /mnt/pd0/docker
Make a symlink: ln -s /mnt/pd0/docker /var/lib/docker
Take a peek at the directory structure to make sure it looks like it did before the mv: ls /var/lib/docker/ (note the trailing slash to resolve the symlink)
Start docker back up service docker start

Files

In case on many users one solution to storage all their data is to use volume Once your volume mount, you have to move the data and create a symlink

mv $GALAXY_ROOT/database/files/ /path/to/your/partition
ln -s /path/to/your/partition $GALAXY_ROOT/database/files/

Example

mkfs.ext4 /dev/vdb
mkdir home/galaxy/data_Galaxy/
mount /dev/vdb /home/galaxy/data_Galaxy/
mv $GALAXY_ROOT/database/files/ /home/galaxy/data_Galaxy/
ln -s /home/galaxy/data_Galaxy/files/ $GALAXY_ROOT/database/files/
ln -s /home/galaxy/data_Galaxy/files/ $GALAXY_ROOT/database/files/

#Slurm

The Controler machine

On your server-galaxy-machine use the script install_slurm.sh, it will install and configure slurm and munge. We give you an 'slurm.conf_example', based on the architecture of one big node host by an another machine dedicated to the cluster

To acces to your machine from the outside you need to open some port

ValentinChCloud/Galaxy_production