Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 Pre-release master -> staging_Eisbock3 #6289

Closed
1 of 14 tasks
pcrespov opened this issue Sep 2, 2024 · 1 comment
Closed
1 of 14 tasks

🚀 Pre-release master -> staging_Eisbock3 #6289

pcrespov opened this issue Sep 2, 2024 · 1 comment
Assignees
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Milestone

Comments

@pcrespov
Copy link
Member

pcrespov commented Sep 2, 2024

What kind of pre-release?

master branch

Sprint Name

staging_Eisbock

Pre-release version

3

Commit SHA

dc0d182a0b9328cfdd992b92b75943db9701f93e

Planned date

Tue. Sep 4, 2024

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

What Changed

Devops check ⚠️ devops

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": "2024-09-04T11:30:00.000Z", "end": "2024-09-04T15:00:00.000Z", "reason": "Release staging_Eisbock3 "}
  • 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>
@pcrespov pcrespov added t:maintenance Some planned maintenance work release Preparation for pre-release/release labels Sep 2, 2024
@pcrespov pcrespov changed the title 🚀 Pre-release master -> staging_<sprint_name><version> 🚀 Pre-release master -> staging_Eisbock3 Sep 2, 2024
@pcrespov pcrespov added this to the Eisbock milestone Sep 2, 2024
@YuryHrytsuk
Copy link
Contributor

YuryHrytsuk commented Sep 4, 2024

Issues encountered

Dalco staging:

  • simcore services: traefik, rabbit and dask-scheduler has wrong middleware names (@swarm instead of@docker)
    • The reason is we still use Traefik v2 on dalco stag. After renaming middlewares mentioned from swarm to docker) it works
    • ⚠️ action required until we release Traefik v3 to PROD
    • fyi @mrnicegyu11 @matusdrobuliak66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Projects
None yet
Development

No branches or pull requests

3 participants