debian11 + postgres13 + python39

added 1 commit

• 54537e75 - remove references to mariadb

Compare with previous version

added 1 commit

• db66019d - update to supported node.js

Compare with previous version

added 1 commit

• a26b7ef0 - update package list

Compare with previous version

Testing summary (so far) on gracedb-dev1:

• Make sure the django app installs from requirements.txt
• Make sure the overseer service launches and transmits igwn-alerts
• client-server integration tests
• kinit a keytab for ldap access
• update users from the ldap

So everything checks out on dev1. I was concerned this change would break shibboleth, but as far as I can tell the name of the package and its source just changed with different versions of debian. I uninstalled shibboleth and installed the two other support packages, restarted apache, restarted gracedb-dev1, and every appears to be working fine.

Testing to do on gracedb-dev tomorrow (2023/08/03):

There is the issue of the upgrade from postgres13-> postgres12. I think i safely showed that nothing breaks on gracedb-dev1, but the backend on the gracedb-postgres-dev RDS needs to be upgraded to 13.11. This may or may not require a new parameter group, i'll check that later. So it will work like this:

• docker service scale gracedb_gracedb=2 on playground, test, dev
• docker service update --env-add DJANGO_MAINTENANCE_MODE_ACTIVE=True gracedb_gracedb on playground, test, dev
• upgrade the backend on gracedb-postgres-dev to 13.11 (wait wait wait for it to restart)

And then on dev:

• docker service update --force --image containers.ligo.org/computing/gracedb/server:debian11 gracedb_gracedb
• docker service update --env-add DJANGO_MAINTENANCE_MODE_ACTIVE=False gracedb_gracedb
• Make sure the django app installs from requirements.txt (pipeline passed)
• Make sure the overseer service launches and transmits igwn-alerts
• client-server integration tests
• kinit a keytab for ldap access
• update users from the ldap

And then if the tests pass, flash the debian11 image to playground and test and then let it run over the weekend.

If something goes wrong: bring the services down into maintenance mode again, and then put the RDS back to postgres 12.15m and then deploy the old 2.21.8 container.

added 1 commit

• f4fcda19 - install libapache2-mod-shib

Compare with previous version

added 1 commit

• 9ba4307f - bulk deps update

Compare with previous version

added 1 commit

• 8a00ac4b - revert pyparsing upgrade

Compare with previous version

added 3 commits

• 3241eb36 - bump version number
• b15e410d - clean up ldap polling tool
• 69ff278a - filter xray segments warning noise

Compare with previous version

added 1 commit

• ff0a9094 - vaccum and analyze in cleanup maintenance

Compare with previous version

postgres (client) 13 is backwards compatible with a postgres12 server, so i'm going to punt the RDS upgrade until after this has been deployed and equilibrates. (reference).

Otherwise this upgrade looks stable so i'm going to merge it in and release it.

marked this merge request as ready

merged