-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labs engine playbook #2339
base: master
Are you sure you want to change the base?
Labs engine playbook #2339
Conversation
- group_vars/VAULT | ||
- group_vars/labs_engine.yml | ||
- host_vars/labs.usegalaxy.org.au.yml | ||
roles: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll also need to run the common
and insspb.hostname
roles. Probably also dj-wasabi.telegraf
.
@@ -0,0 +1 @@ | |||
labs_engine_branch: main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also need to define some ssh-specific variables such as extra_keys
and ssh_config_*
see host_vars/galaxy-queue.usegalaxy.org.au.yml
for example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be named consistently with other Galaxy playbooks. Ie labs-engine_playbook.yml
. Same goes for the dev version of the playbook.
Add a playbook for deploying the labs engine to dev and prod servers:
ansible-playbook -i hosts --key-file ~/.ssh/galaxy-au labs_engine_prod.yml
ansible-playbook -i hosts --key-file ~/.ssh/galaxy-au labs_engine_dev.yml
This can't be run until a new Labs Engine VM has been created in AARNet.
Introduces the following vars to the VAULT: