🚀 Pre-release master -> staging_TheAwakening6

[YuryHrytsuk]

What kind of pre-release?

master branch

Sprint Name

TheAwakening

Pre-release version

6

Commit SHA

TBD

Planned date

March 27m 2025

Did the commit CI suceeded?

• The commit CI succeeded.

Motivation

• Weekly staging release

What Changed

OPS

• Remove override storage replicas for master (Remove override storage replicas for master osparc-ops-environments#1001)
• [simcore] add storage replicas ([simcore] add storage replicas osparc-ops-environments#1000)
• Registry: run on ops nodes only (Registry: run on OPS nodes osparc-ops-environments#997)
• Fix: grafana terraform import (Fix: grafana terraform import osparc-ops-environments#998)
• [PR Template] Service is monitored and testing URL ([PR Template] Service is monitored and testing URL osparc-ops-environments#994)
• Try to fix grafana state CD test: Add CEPH skips for tf
• Try to fix grafana state CD test: Refactor
• Fix redis exporter environment (Fix redis exporter environment osparc-ops-environments#988)
• Make monitoring/grafana/terraform/main.tf .PHONY
• Fix ceph VS AWS S3 grafana terraform state handling
• ✨ Add: Manage grafana content/assets via terraform (✨ Add: Manage grafana content/assets via terraform osparc-ops-environments#913)

Devops check ⚠️ devops

• Add Grafana Dashboard for Docker Registries (from internal master: registry is occasionally unresponsive osparc-ops-environments#995)
  • dalco stag
  • nih stag
  • not done due to [BUG] CI Pipelines do not add new Grafana dashboards osparc-ops-environments#1002

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>