Perform CSIS Beta Release

[p-a-s-c-a-l]

In this issue we plan the CSIS BETA Release. We have to define a time frame when all people are available needed for release preparation so that we can minimise the downtime of csis.myclimateservice.eu

Release Preparation

Resolve remaining issues:

• @DanielRodera New geoserver (geoserver.myclimateservice.eu) uses different layer name
• @therter Update CLARITY GeoServer URIs in Data Packages
• @humerh Update CLARITY GeoServer URIs in EMIKAT

Perform Release

• @p-a-s-c-a-l Notify users about expected downtime
• @p-a-s-c-a-l shutdown containers on V3LS1809 and copy to csis.ait.ac.at and csis-dev.ait.ac.at, start containers
• @patrickkaleta / @fgeyer16 make sure that content on csis.ait.ac.at is read-only except for creating new studies
• @patrickkaleta / @fgeyer16 disable everything on the DEV system csis-dev.ait.ac.at that may interferes with the PROD system on csis.ait.ac.at (EMIKAT Trigger, Transport Application triggers, SSO?!, ...)
• @patrickkaleta / @fgeyer16 if possible check the synchronisation from DEV -> PROD. Be sure to sync from csis-dev.ait.ac.at (62.218.164.246) to csis.ait.ac.at (62.218.164.247).
• @p-a-s-c-a-l update reverse proxy config on V3LS1809 and forward csis.myclimateservice.eu to csis.ait.ac.at

Test Release with proxied csis.myclimateservice.eu

nginx on csis.myclimateservice.eu (V3LS1809) now redirects to csis.ait.ac.at (62.218.164.247) until DNS entries are updated. This should work with EMIKAT Triggers and Drupal API requests (e.g. performed by Map Component)

• @patrickkaleta Update Drupal on csis.ait.ac.at and change site domain to csis.myclimateservice.eu
• @patrickkaleta Create and test an automated screening study on csis.myclimateservice.eu
• @p-a-s-c-a-l Test external apps (Map, Table, Scenario Analysis)
• @DanielRodera change DNS entry of csis.myclimateservice.eu to 62.218.164.247. (Note: csis-dev.myclimateservice.eu is already on 62.218.164.246)

Test Release with csis.myclimateservice.eu

DNS changes may take some time, so this will be done the other day:

• @p-a-s-c-a-l shutdown reverse proxy on V3LS1809
• @p-a-s-c-a-l Update reverse proxy config on csis.ait.ac.at and renew certificates of csis.myclimateservice.eu
• @p-a-s-c-a-l Create and test an automated screening study on csis.myclimateservice.eu
• @p-a-s-c-a-l Notify users

For performing the release we need at least @p-a-s-c-a-l and @patrickkaleta / @fgeyer16. If we are able to resolve the remaining issues asap, we should be able to perform the release right after the next WPL telco on Tuesday 02.06. Otherwise we have to set-up another telco.

@DanielRodera Please talk to your IT department in advance so that they are prepared to change the DNS entry of csis.myclimateservice.eu. The actual change can be initiated when we've successfully tested the system with proxied csis.myclimateservice.eu.

[DanielRodera]

@DanielRodera Please talk to your IT department in advance so that they are prepared to change the DNS entry of csis.myclimateservice.eu. The actual change can be initiated when we've successfully tested the system with proxied csis.myclimateservice.eu.

Our IT people are already warned and prepared to do the change on your command.

[patrickkaleta]

@fgeyer16 and I will further talk about the open actions for this issue on Thursday. He'll look into the CAS/SSO before that if possible.

In the meantime it's still possible to login directly into either PROD or DEV instance if necessary (e.g. for admins) by directly visiting the individual login pages:
https://csis.ait.ac.at/user/login
https://csis-dev.ait.ac.at/user/login

[p-a-s-c-a-l]

https://csis.myclimateservice.eu/ and https://csis-dev.myclimateservice.eu/ are now available. Sites are put in maintenance mode until remaining steps have been resolved.

[ghilbrae]

Hi! To access the csis-dev can we use the same user/pass that we have been using up until now?

[patrickkaleta]

Hi! To access the csis-dev can we use the same user/pass that we have been using up until now?

Yes, usernames and passwords are still the same. If you have problems with your credentials, let me know.

[patrickkaleta]

[ ] @patrickkaleta / @fgeyer16 disable everything on the DEV system csis-dev.ait.ac.at that may interferes with the PROD system on csis.ait.ac.at (EMIKAT Trigger, Transport Application triggers, SSO?!, ...)

Configuration of the csis_helpers module for the DEV <-> PROD setup is now complete.

Emikat trigger, TM trigger and Emikat-Testing trigger are only active for https://csis.myclimateservice.eu/ as the Host URL. For the DEV environment or any local CSIS instances, those triggers will not fire and instead a log message will be written to the Drupal-intern Log report.

Besides the csis_helpers module I don't have anything (cronjobs, etc..) that could interfere with our DEV <-> PROD setup. Still pending is now the SSO, which will hopefully be done by @fgeyer16 today.