🚀 Pre-release master -> staging_KobayashiMaru2

[mrnicegyu11]

What kind of pre-release?

master branch

Sprint Name

KobayashiMaru

Pre-release version

2

Commit SHA

5175164

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

propagate some fixes to sim4life-io

What Changed

🐛 Fix log streaming issues (#5104)
✨payments service: notification of payments to the front-end via socketio (#5057)
🐛Correctly handle file type of on-demand clusters (#5101)
🐛 PO center should be visible in all products #5052 (#5107)
🐛 Avoids credit transaction on unsuccesful payment (⚠️ devops) (#5106)
🎨 Only show “credits” col in usage table if wallets (#5105)
✨🎨 Preferences: Inactivity and Concurrency (#5024)
🔨 Adding playwright framework with first test (#5072)
♻️ Remove WSL-related Makefile integration (#5097)
♻️✨Comp backend: refactor progress + allow internal progress bar to use weights (#5084)
♻️ sim4life.io release monitor - moved to staging (#5095)
♻️ Add debug logs for unknown issue (#5098)
🐛Dask-Sidecar: improper detection of GPUs on multi-GPU machines if log-driver is improperly set (#5093)
✨services can now be shut down when the credits limits are reached ⚠️ (#5058)
🐛 Puppeteer fix: Card selection by title (#5092)

Devops check ⚠️ devops

• Add changes (if any) and release tags in https://github.com/ITISFoundation/osparc-ops-environments/tags
• Add changes (if any) and release tags in osparc-ops-deployment-configuration (staging.osparc.io & osparc-staging.speag.com)
• ...

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-12-01T07:00:00.000Z", "end": "2023-12-01T08:30:00.000Z", "reason": "Planned Maintenance"}

- [ ] Announce release in Mattermost

🔊  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://https://staging.s4l-lite.io/

and on premises:

• https://osparc-staging.speag.com
• https://tip-staging.speag.com
• https://s4l-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
``` md
https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_<sprint_name><version>

[mrnicegyu11]

Does #5106 really have to be propagates to production?

Failed attempts:

Wrong env-var name: SIMCORE_IMAGE_TAG

Dalco-Staging: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/pipelines/622062
Aws-Staging: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/pipelines/622065

Success

dalco-staging https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/pipelines/622071

Notes

• Dont run grafana automatically
• Dont make deploy_ops mandatory
• In release tempalte dont make the ci run necessary