Spatial Ansible Update

[sat01a]

Issue Raised by Vicente (@vjrj) & @djtfmartin

Slack note from Dave:
I’ve had this message from Vicente
We have issues with recent versions of spatial for many months. After discovering the ala-install spatial not merged branch, and merged it, the problems persist. I notice that ALA is using in production, for instance, a different up-to-date version of geoserver than the one in ala-install or previous versions of ala-install. So I can imagine that someone in ALA is maintaining your service with a different fork or a local ala-install or ... I don’t know.
Can anyone comment on the state geoserver/ala-install ? Is what is in production merged into master for ala-install ?
cc
(https://atlaslivingaustralia.slack.com/team/UCW5JU5J8)

Note from adamcollins:
(https://atlaslivingaustralia.slack.com/archives/C03EJ7ARZQW/p1686884086144969?thread_ts=1686815866.296319&cid=C03EJ7ARZQW)
ansible for spatial has been broken for a while (years)
ALA is managing spatial test and prod manually. e.g. dropping in a new geoserver war and plugins.
Fixing ala-install for spatial is on the list of activities but not much progress has been made recently.

[vjrj]

If I can help here somehow...

[vjrj]

Any update on this?

[qifeng-bai]

@vjrj I think The ansible script for Spatial has been merged into master branch.

Pleas check if those vars are in your inventory:

db_remote=false
pg_service=postgresql-12
pg_version=12
postgis_version=3
postgis_scripts_version=3.4

layers_db_host=
layers_db_port=
layers_db_name=
layers_db_username=
layers_db_password=

[vjrj]

Thanks indeed @qifeng-bai I'll test in a new server.

[vjrj]

Hi again. I recently set up a spatial instance using the upstream ala-install script and noticed that still there seems to be a discrepancy in the versions of GeoServer being used. According to the ala-install defaults, GeoServer version is set to 2.19.2 (source). However, I observed that the ALA production environment is currently utilizing 2.21.1.

This issue has tangible impacts; for instance, in our last test, we faced difficulties even creating a layer due to such discrepancies.

This variation raises a concern regarding the reproducibility of the ALA spatial service setup, especially for other LA portals looking to upgrade their spatial services. If there are any additional or alternative steps, possibly manual or undocumented, being employed to achieve the production setup, it would be immensely helpful for the community to have access to this information.

I appreciate your attention to this matter and look forward to any guidance you can provide to help ensure consistent and reproducible deployments across the LA community.

Thank you in advance.

[qifeng-bai]

@vjrj Ansible uses GeoServer 2.19.2 as default. It has been deployed on spatial-dev and spatial-test, the layers function works well. Spatial prod was managed manually, so the GeoServer is updated to 2.21.1.

You mentioned that the creation of layer failed may related to Postgres setup. We can have a quick check on the GeoServer to identify issue

Meanwhile, can you please check if the folder '/data/geoserver_data_dir/gwc' exists?

[vjrj]

Thanks for your help as usual. I was expecting the same deployment result as in ALA production. Are you expecting to upgrade or downgrade the geoserver in future updates of your spatial.

[qifeng-bai]

@vjrj I would say 'upgrade'. I would update ansible on Monday