sudo apt install ansible
or see http://docs.ansible.com/ansible/latest/installation_guide
If you've installed a minimal version of Ansible (eg, python3 -m pip install ansible-core), you should add our required Ansible modules thusly:
ansible-galaxy install -r requirements.yml
Ansible connects and runs using the ansibleuser set in
group_vars/all.yml. All playbooks assume this user exists, you can
log into the server with this user using ssh keys, and that the user has
sudo privileges.
AWS image with deploy uesr, keys, and patsh for certs are set up.
Not all of the playbooks have been tested recently. Below are the commands that have been used recently.
ansible-playbook -v --limit=ot38 playbk-build-synth-pipeline.yml
ansible-playbook -v --limit=ot38 playbk-build-otc-ws.yml
The first time you do it, you need to start with:
ansible-playbook -v --limit=ot38 playbk-add-user.yml
to create an opentree user. Then anytime you want to refresh the webapp code:
ansible-playbook -v --limit=ot38 playbk-install-curatorless-frontend.yml
You need the custom-synth ID. It'll prompt you for it, but
you can also use the --extra-vars "custom_synth_id= syntax to pass
the ID in from the command line. So, if you wanted to deploy snacktavish_aves_81461_tmp520utw8e, you could use:
ansible-playbook -v --limit=ot38 --extra-vars "custom_synth_id=snacktavish_aves_81461_tmp520utw8e" playbk-deploy-custom-synth.yml
You might need to run:
ansible-playbook -v --limit=ot38 playbk-install-curatorless-frontend.yml
to refresh the web app cache.
ansible-playbook playbk-install-webapp.yml -i hosts --limit devtree
Some links that were helpful:
- Previous Open Tree deployment system: https://github.com/OpenTreeOfLife/germinator/tree/master/deploy
- Previous Open Tree component with ansible installation: https://github.com/OpenTreeOfLife/otindex_ansible
- https://andidog.de/blog/2017-04-24-ansible-best-practices
Variables for roles are set in role/defaults, not role/vars. This makes
it easy to override role defaults either in group_vars (when the
setting is specific for a host) or with include_role (when a setting is
specific for a playbook / another role). See the
ansible docs on variable priority for the gory details on how
variable priority works.
You can test any of the playbooks locally using Vagrant and VirtualBox (or other provider like VMWare, Hyper-V). Once you have vagrant and virtualbox installed, running vagrant up will start the virtual host and run the playbook opentree.yml. To run a different playbook, edit the ansible.playbook option in the Vagrantfile.
See the Ansible documentation on using Vagrant for more info.
$ ssh ot58 'sudo tail /var/log/apache2/error.log'
$ ssh ot58 'sudo tail /var/log/apache2/access.log'
$ ssh ot58 'sudo tail /var/log/apache2/ssl_error.log'
or, alternately
$ ssh ot58 'sudo tail -f /var/log/apache2/*.log'
If you see the dreaded web2py Internal error, or a 500 server error, look in /home/deploy/ws_dir/repos/opentree/webapp/errors for logs.