galaxyproject/ansible-cloudlaunch

Name: ansible-cloudlaunch

Owner: Galaxy Project

Description: Ansible playbook for deploying CloudLaunch

Created: 2016-06-25 18:07:00.0

Updated: 2016-06-25 18:07:00.0

Pushed: 2018-01-05 21:42:42.0

Homepage: null

Size: 106

Language: null

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Ansible playbook for deploying CloudLaunch.

Install

To install, just clone this repository:

clone https://github.com/galaxyproject/ansible-cloudlaunch.git

Use

This playbook is intended to run on Ubuntu 16.04, using Ansible 2.2.1.0 or higher.

Create the inventory file called inventory to point to the server you want to configure with the following content, adjusting for variables:

udlaunch-webserver]
165.157.111 ansible_ssh_user="ubuntu" ansible_ssh_private_key_file="key.pem" ansible_ssh_common_args='-o StrictHostKeyChecking=no -o CheckHostIP=no -o "UserKnownHostsFile /dev/null"'

Edit the configuration values. In particular, the cloudlaunch admin password (for django admin, the database password and the server name should be changed. You will also need to provide your own SSL cert files. The default values are stored in roles/cloudlaunch/defaults.yml but you should use local_vars.yml file in the repo root directory (as defined in playbook.yml) to change the most frequently edited values. Note that this file must exist for the playbook to run. Here is an example of that file's content:

dlaunch_admin_password: "CHANGEMEONINSTALL"
ssword: "CHANGEMEONINSTALL"
er_name: beta.launch.usegalaxy.org
ese files need to be placed into roles/cloudlaunch/files/secret and vaulted
cert_files:
beta.launch.usegalaxy.org_certchain.pem
cl.crt
cl.key

Store the vault password to .vault_pass in the repo root dir and run the playbook with the following command:

sible-playbook -i inventory playbook.yml

Restoring default application data

Once installed, you can populate the server with default data, such as the list of public clouds. The default data is stored in cloudlaunch_clouds_and_apps.json in the playbook folder. To restore default data, run:

sible-playbook -i inventory restoredb.yml

Copying the database from server1 to server2

Run these commands after you have run the playbook. On server1, create a dump of the cloudlaunch database:

do su postgres
_dump -Fc -f cl.dump cloudlaunch

Copy cl.dump file from server1 to server2 and run the following commands to import the database:

op the CloudLaunch server so the empty database can be deleted
do supervisorctl stop cloudlaunch celeryd
come the postgres system user
do su postgres
lete the (empty) database
opdb cloudlaunch
eate the database, using an empty template
eatedb -T template0 cloudlaunch
store the database from the file copyied from server1
_restore -d cloudlaunch cl.dump
turn to the default user
it
art the CloudLaunch server
do supervisorctl start cloudlaunch celeryd