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: Making sure you're not a bot!
( addition of add-download2.yml is also an accident ? )
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
On Fri, Sep 26, 2025 at 01:15:54PM -0400, Regina Obe wrote:
> 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 ?
I've dropped ansible-dev-old. Leave ansible-dev alone as I'm using that one and wasn't built from Ansible.
How's ansible-dev supposed to be different from ansible-control ?
Could we just rename it to be in agreement with Ansible ?
On Fri, Sep 26, 2025 at 01:15:54PM -0400, Regina Obe wrote:
> > 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 ?
>
> I've dropped ansible-dev-old. Leave ansible-dev alone as I'm using that
one
and wasn't built from Ansible.
How's ansible-dev supposed to be different from ansible-control ?
Could we just rename it to be in agreement with Ansible ?
--strk;
I don't know what ansible-control is. Is that something you created?
I setup ansible-dev to work on ansible and it has my home account and
password key on it and configured just the way I want it.
On Thu, Oct 02, 2025 at 04:43:31AM -0400, Regina Obe wrote:
> On Fri, Sep 26, 2025 at 01:15:54PM -0400, Regina Obe wrote:
>
> How's ansible-dev supposed to be different from ansible-control ?
> Could we just rename it to be in agreement with Ansible ?
I don't know what ansible-control is. Is that something you created?
I setup ansible-dev to work on ansible and it has my home account and
password key on it and configured just the way I want it.
Check out deployment/roles/osgeo4/tasks/main.yml - how about we rename your ansible-dev to
ansible-control and check that deploying tag container_ansible of osgeo4 role doesn't introduce any change ?
Too difficult to do ansible work on my desktop.
Yes I remember this, it's probably the main reason why ansible-control was planned
