osgeo4 deployment mismatch with Ansible
Sandro Santilli
strk at kbt.io
Fri Sep 26 08:28:10 PDT 2025
Preparing to add the new mail server container to the set of backed up
containers I found out that the "osgeo4" state is not the one
requested by our Ansible based playbook.
This is how to check:
make check-osgeo4 ANSIBLE_CONFIG=ansible.osgeo.prod.cfg
The command above shows a few changes that would be made to the
running system and I wonder which of them are really wanted and
which are not, these are:
x. Backup scripts would change
The version of the backup scripts on osgeo4 is different
from the version in ansible. Weird enough, the version on
the machine contains a comment stating "Managed via ansible"
while the version in ansible does NOT have the comment.
Moreover, there's a git repository on the root dir of osgeo4
but only partially containing the /backup dir and having
local changes on that partially covered set.
Shall I update ansible to match production ?
x. An "ansible-control" container would be created
On the host we have both "ansible-dev" and "ansible-dev-old"
containers, and BOTH are in RUNNING state, shall I drop them
both and let the ansible playbook do its thing ?
x. The "osgeo4-nginx" container would get proxied 140.211.15.32:8081
The proxy name would be "proxyportacme", suggesting this was for
LetsEncrypt, but I don't think letsencrypt uses port 8081 and the
current server is NOT proxying it,
shall I drop that from the playbook ?
NOTE: this was probably added by accident in an unrelated commit:
http://gitea.osgeo.org/sac/ansible-deployment/commit/23dadaf4c
( addition of add-download2.yml is also an accident ? )
--strk;
Libre GIS consultant/developer 🎺
https://strk.kbt.io/services.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20250926/af308398/attachment.sig>
More information about the Sac
mailing list