...
Code Block |
---|
## Login ssh devel@kb-prod-udv-001.kb.dk ## Activate virtualenv . csr_ansible/bin/activate ## Delete the existing conf dir to show what happens ssh netarkdv@sb-test-har-001.statsbiblioteket.dk rm AnsibleTest/conf/* ## Run ansible ansible-playbook nas_ansible_pb/site.yaml -i nas_ansible_pb/hosts ## ssh netarkdv@sb-test-har-001.statsbiblioteket.dk ls AnsibleTest/conf/* ssh netarkdv@sb-test-har-001.statsbiblioteket.dk cat AnsibleTest/conf/start_HarvestControllerApplication_sbhigh_h3.sh |
Other Things To Think About
- Server config (java, jms-broker, postgres)
- Windows
- Cloud deploy (for testing a distributed instance)
- Ansible Tower - fancy GUI
- Structuring an ansible project best practice - when and how to use groups and roles, for example
- Triggers/handlers (e.g. which parts of the system to restart and when)