🚀 Pre-release master -> staging_KobayashiMaru5

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

KobayashiMaru

Pre-release version

5

Commit SHA

09dd712f6c66bf2336f6321a6bd1e0430c7de7eb

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

Weekly staging release

What Changed

• 🐛 Publishing as Tutorials - PO TESTER and ADMIN #5143 by @jsaq007
• ✨Clusters-keeper: allow for custom boot scripts (⚠️ devops) #5141 by @sanderegg
• 🐛 Billing center: Various fixes #5145 by @ignapas
• 🐛 Bugfix/instrumentation queue #5122 by @matusdrobuliak66
• 🔨 e2e/adding rut test #5135 by @matusdrobuliak66
• ✨Computational backend: allow to set custom ec2 tags (⚠️ devops) #5147 by @sanderegg
• ✨add preference to allow data collections form services #5112 by @GitHK
• 🐛 Bugfix/computation of credits #5151 by @matusdrobuliak66
• ♻️ Adding additional checks to RUT + 🐛 Setting RabbitMQ message TTL #5150 by @matusdrobuliak66
• Bump actions/setup-python from 4 to 5 #5153 by @dependabot
• 🐛 Less stringent regex for AWS tag value #5155 by @sanderegg
• 🐛 fix dynamic-sidecar preferences save and before shutdown event ordering #5156 by @GitHK
• 🐛 Collaborators can save the state of a project #5158 by @GitHK
• 🎨 UI updates - 🐛 bug fixes #5111 by @jsaq007

Devops check ⚠️ devops

• Deploy RabbitMQ to sim4life.io before starting to release (USE PROPER PASSWORD)
• Move NIH STAG Rabbit MQ to simcore rabbit container
• Introduce user-defined certificates --> Won't do this time.

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]

⚠️ for Matus ⚠️

Because of TTL change in rabbitmq queues, it might be needed to delete these queues manually:

• io.simcore.service.tracking
• io.simcore.service.wallets
• io.simcore.service.wallets-credit-limit-reached
• io.simcore.services.instrumentation

Either delete them preventively before releasing, or if some services have problem to start just delete the queues and restart the service!