🚀 Pre-release master -> staging_KobayashiMaru6

[matusdrobuliak66]

What kind of pre-release?

master branch

Sprint Name

KobayashiMaru

Pre-release version

6

Commit SHA

f60e02aec57b8b11ac5ff0aa0ce587c21acfc257

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

n/a

What Changed

• ♻️ servicelib.fastapi tools and rabbitmq.rpc errors interface #5157 by @pcrespov
• ✨Monitoring tools: CLI to monitor what is going on #5162 by @sanderegg
• 🐛Computational backend: ensure log level is set properly + increased tracing #5164 by @sanderegg
• ✨Computational backend: timeout pipeline if WAITING_FOR_CLUSTER state takes more than 10 minutes #5163 by @sanderegg
• ✨Monitoring tools: show more information about computational clusters #5165 by @sanderegg
• 👋 remove codeclimate #5166 by @sanderegg
• ♻️ Put less noise to RUT logging #5170 by @matusdrobuliak66
• ✨ Extending logging while starting new style dynamic services #5171 by @GitHK
• ⬆️ tools repo-wide upgrade #5173 by @sanderegg
• ✨ dynamic services with pricing plans add labels for autoscaling #5089 by @GitHK
• ✨Adds reserved disk space to dynamic-sidecar #5161 by @GitHK
• 🐛 fix dynamic-sidecar inactivity response when user service reply is not formatted correctly #5174 by @GitHK
• ♻️ disable noisy logger for background tasks form dynamic sidecar #5175 by @GitHK
• ♻️ do not send heartbeat as soon as the service is started #5168 by @GitHK
• 🎨 Add retries to storage client inside nodeports #5176 by @GitHK
• 🐛e2e testing: replacement of sleepers using Playwright (preparation for upscaling of ext clusters) #5167 by @sanderegg
• ♻️track via dynamic-scheduler ⚠️ #5136 by @GitHK
• ✨ Inactivity (front-end part) #5130 by @ignapas
• 🐛 Add install-ci Make recipe in playwrigt e2e tests #5182 by @bisgaard-itis
• Bump github/codeql-action from 2 to 3 #5186 by @dependabot
• Bump actions/setup-node from 4.0.0 to 4.0.1 #5183 by @dependabot

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-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>

[YuryHrytsuk]

aws staging have huge problems with resources. Up to 10 different services from misc. stacks could not start. I had to set resource reservations to 0 for them to start