🚀 Pre-release master -> staging_Bazinga2

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

Bazinga

Pre-release version

2

Commit SHA

TBD

Planned date

TBD

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• Weekly staging release

What Changed

No response

Before release

• Shutdown all computational clusters ⬆️Upgrade dask-based services (dask-sidecar, autoscaling, clusters-keeper, director-v2) 🚨🚨🚨 (computational clusters must be down on release) #7701 @YuryHrytsuk @sanderegg

Devops check ⚠️ devops

• Mitigate graylog minor version upgrade bug @mrnicegyu11 :

0. This can be done entirely in portainer
1. Scale graylog-mongodb to 0 replica
2. Delete docker persistant volume of graylog-mongodb
3. Scale graylog-mongodb to 1 replica

• Disable api stopping / termination for EC2 Instances in PROD osparc-ops-environments#1047
• Add detailed rabbitmq monitoring osparc-ops-environments#1048
• make sure prometheus / grafana work without tracing enabled in simcore @YuryHrytsuk @bisgaard-itis
• verify simcore grafana dashboards work (with / without exemplars) @bisgaard-itis @YuryHrytsuk Simcore Exemplars do not work in Grafana Dashboard (staging) osparc-ops-environments#1059
• [verify new AMIs work](nih stag: new autoscaling AMI with NVIDIA)
• update persistent machines --> do later @YuryHrytsuk

e2e testing check 🧪

No response

Summary 📝

• make release-staging name=<sprint_name> version=<version> git_sha=<commit_sha>
  • https://github.com/ITISFoundation/osparc-simcore/releases/new?prerelease=1&target=<commit_sha>&tag=staging_<sprint_name><version>&title=Staging%20<sprint_name><version>
• Draft pre-release
• Announce (add redis key maintenance in every concerned deployment)

  {"start": "2023-02-01T12:30:00.000Z", "end": "2023-02-01T13:00:00.000Z", "reason": "Release ResistanceIsFutile9 "}

• Announce release in Mattermost

  :loud_sound:  Maintenance scheduled for **NAMED_DAY DD. MM from START_TIME - END_TIME**.
  =========================================================================
  
  @all Be aware that you will automatically be logged out and your projects stopped and saved during the maintenance time. Affected:
  *   [https://staging.osparc.io](https://staging.osparc.io/)
  *   [https://https://staging.s4l-lite.io/](https://https://staging.s4l-lite.io//)
  
  and on premises:
  *   [https://osparc-staging.speag.com](https://osparc-staging.speag.com/)
  *   [https://tip-staging.speag.com](https://tip-staging.speag.com/)
  *   [https://s4l-staging.speag.com](https://s4l-staging.speag.com/)
  *   [https://s4l-lite-staging.speag.com](https://s4l-lite-staging.speag.com/)
  
  
  Reason: Scheduled staging-release of STAGING_NAME_AND_VERSION.
  
  Thanks for your understanding and sorry for the inconveniences,
  
  Your friendly oSparc Team
  
  

Releasing

• Release (release draft)
• Check Release CI
• Check hanging sidecars. Helper command to run in director-v2 CLI simcore-service-director-v2 close-and-save-service <uuid>
• Check deployed
  • aws deploy
  • dalco deploy
• Delete announcement
• Check e2e runs
• Announce

https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_<sprint_name><version>

[matusdrobuliak66]

⚠️⚠️ Run DB script @matusdrobuliak66

After this commit #7677 is deployed, we should do this: https://github.com/ITISFoundation/private-issues/issues/85#issuecomment-2886608706

[YuryHrytsuk]

Done from my side. Once @matusdrobuliak66 runs db script, he should close the issue

[matusdrobuliak66]

DB changes done, closing the issue