FAQ

Frequently Asked Questions (FAQ)

Table of Contents

• So what happens when i rerun the ansible? it doesn’t like make two versions of everything?

So what happens when i rerun the ansible? it doesn’t like make two versions of everything?

It's quite common to rerun ansible with ala-install from time to time, for instance to upgrade some LA service, etc.

In general you repeat the same tasks. If you changed some variable in your inventories, it will reconfigure your service using it. If you update ala-install you will use new versions and/or configuration variables.

The only exception are probably solr, cassandra and nameindex:

• solr: because ala-install tries to create the cores and fails. Use --skip (see below)
• cassandra: because removes the cassandra data so it's better to skip if you already ingested data (this is done because if you have a cluster, you have to start from zero in new cassandra nodes).
• nameindex: you repeat the same task (download, unzip, backup previous namedindex) and at the end you are out of disk because /data/lucene is full of nameindex copies.

So better --skip nameindex,solr7_create_cores,cassandra if you are using ansible-playbook or --skip=nameindex,solr7_create_cores,cassandra if you are using the LA generator ansiblew wrapper.

Also you can use --tags properties with ansible-playbook (or -p with ansiblew wrapper) if you only want to propagate new properties variable changes [1]

[1] This will not work with CAS and Spatial because the way these playbooks are written including roles.