The diagram below shows the result of a multi-machine installation.
Once you’ve prepared the target hosts (ensuring the Useful information are accessible) and configured the inventory_ssh.yaml file as described above, you’re ready to run the playbook.
To check that your inventory file is configured correctly, and that the control node is able to connect to the target hosts, run:
ansible all -m ping -i inventory_ssh.yml
Optional: To check if the required ports for the deployment are available on the target machine and you also have connectivity between nodes (ex. repository connecting to the db on 5432), the prerun-network-checks playbook can be executed before you deploy ACS. If there are any firewalls blocking connectivity this playbook discovers them.
pipenv run ansible-playbook playbooks/prerun-network-checks.yml -i inventory_ssh.yml [-e "acs_play_repository_acs_edition=Community"]
To deploy the latest ACS Enterprise on the target hosts, execute the playboook as the current user using the following command:
pipenv run ansible-playbook playbooks/acs.yml -i inventory_ssh.yml
If you see an error message during installation, then check for Troubleshooting.
Once the playbook is complete, Ansible displays a play recap to let you know that everything is done, similar to the following:
PLAY RECAP ******************************************************************************************************* acc_1 : ok=24 changed=6 unreachable=0 failed=0 skipped=6 rescued=0 ignored=0 activemq_1 : ok=24 changed=0 unreachable=0 failed=0 skipped=17 rescued=0 ignored=0 adw_1 : ok=24 changed=6 unreachable=0 failed=0 skipped=6 rescued=0 ignored=0 database_1 : ok=20 changed=0 unreachable=0 failed=0 skipped=11 rescued=0 ignored=0 nginx_1 : ok=21 changed=8 unreachable=0 failed=0 skipped=8 rescued=0 ignored=0 repository_1 : ok=92 changed=43 unreachable=0 failed=0 skipped=14 rescued=0 ignored=0 search_1 : ok=34 changed=13 unreachable=0 failed=0 skipped=11 rescued=0 ignored=0 syncservice_1 : ok=39 changed=18 unreachable=0 failed=0 skipped=13 rescued=0 ignored=0 transformers_1 : ok=81 changed=10 unreachable=0 failed=0 skipped=44 rescued=0 ignored=0
For details about the webapp URLs, location of logs, configuration, and more, see Useful information.
If you’re deploying a production system, ensure that you review the additional information provided in Securing your installation.