Automated installation using Ansible¶
Installing from source using Ansible is the preferred method for new installations on Ubuntu.
It is assumed here that your host operating system is Ubuntu. This can be modified for a different Unix based operating system, such as Mac OS X or another Linux distribution such as CentOS.
The Ansible roles referenced here can be used in production deployments by creating your own Ansible playbook to run them. See the deploy-pub repo for more details.
On this page
These instructions assume that you have a Python package manager, such as pip, installed on your system. From pip, you should be able to install a released version of Ansible.
If you would like to install Archivematica without Elasticsearch or with limited Elasticsearch functionality, you
must first change the role variable
one of the available values. For more information about Archivematica’s
Ansible role, please see the ansible-archivematica-src repo.
Install VirtualBox, Vagrant, and Ansible.
sudo apt-get install virtualbox vagrant sudo pip install ansible==2.9.10 jmespath
Vagrant must be at least version 1.9. Check your version with:
If it is not up to date, you can download the newest version from the Vagrant website .
Checkout the deployment repo:
git clone https://github.com/artefactual/deploy-pub.git
Download the Ansible roles:
cd deploy-pub/playbooks/archivematica-bionic ansible-galaxy install -f -p roles/ -r requirements.yml
Create the virtual machine and provision it:
This will take a while. It depends on your computer, but it could take up to an hour. Your computer may be very slow while Archivematica is being provisioned - be sure to save any work and be prepared to step away from your computer while Archivematica is building.
If there are any errors, reprovisioning the VM often fixes the issue.
Once it’s done provisioning, you can log in to your virtual machine:
You can also access your Archivematica instance through the web browser:
The credentials can be found in the vars-singlenode-qa.yml.
Deploy development branches¶
The previous section described how to deploy the latest stable Archivematica release.
Our Ansible role can also be used to deploy development branches, e.g. if you want to help us QA our product.
Using deploy-pub, where we host our reference playbooks, please follow these steps:
Download the roles defined in
cd deploy-pub/playbooks/archivematica-bionic ansible-galaxy install -f -p roles/ -r requirements-qa.yml
vars-singlenode-qa.yml. Inside the
pre_taskssection, update the task
- include_vars: "vars-singlenode-qa.yml" tags: - "always"
Optionally, if you have a specific branch(es) that you want to deploy or other custom configuration needs, update
vars-singlenode-qa.ymlas needed. By default, we will deploy off branches
Deploy the new configuration. If you’re using Vagrant, please run: