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

🚀 Release v1.56.0 #4419

Closed
34 of 36 tasks
matusdrobuliak66 opened this issue Jun 26, 2023 · 10 comments
Closed
34 of 36 tasks

🚀 Release v1.56.0 #4419

matusdrobuliak66 opened this issue Jun 26, 2023 · 10 comments
Assignees
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Milestone

Comments

@matusdrobuliak66
Copy link
Contributor

matusdrobuliak66 commented Jun 26, 2023

Release version

1.56.0

Commit SHA

9e9e23417cc6a5df98f34761c52bf1023e55e667

Previous pre-release

#4482

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

Release to production

Changes

Staging Watermelon3

Release Issue: #4430

Staging Watermelon4

Release Issue: #4454

Staging Watermelon5

Release Issue: #4482

No response

Devops check 👷

Tests assessment: e2e testing check 🧪

No response

Test assessment: targeted-testing 🔍️

No response

Test assessment: user-testing 🧐

No response

Summary 📝

  • Prepare release link
make release-prod version=1.56.0  git_sha=9e9e23417cc6a5df98f34761c52bf1023e55e667
  • Draft release changelog
  • Announce maintenance ( ** ANNOUNCE AT LEAST 24 HOURS BEFORE ** )
  • redis {"start": "2023-07-13T12:00:00.000Z", "end": "2023-07-13T13:30:00.000Z", "reason": "Release 1.56.0"}
    • aws
    • dalco
    • tip
  • status page (https://manage.statuspage.io/)
    • osparc
    • s4l
  • mattermost channels
    • maintenance
    • power users

Releasing 🚀

  • Maintenance page up.
cd /deployment/production/osparc-ops-environments
make up-maintenance
make down-maintenance
  • Check hanging sidecars. Helper command to run in director-v2 CLI simcore-service-director-v2 close-and-save-service <uuid>
  • Release by publishing draft
  • Check release CI
  • Check deployed
    • aws deploy
    • dalco deploy
    • tip deploy
  • Check testing endpoint ex. https://testing.osparc.speag.com/
  • Delete announcement
  • Check e2e runs
  • Announce
:tada: https://github.com/ITISFoundation/osparc-simcore/releases/tag/v<M.m.0>
@matusdrobuliak66 matusdrobuliak66 added t:maintenance Some planned maintenance work release Preparation for pre-release/release labels Jun 26, 2023
@matusdrobuliak66 matusdrobuliak66 self-assigned this Jun 26, 2023
@matusdrobuliak66
Copy link
Contributor Author

matusdrobuliak66 commented Jun 26, 2023

(⚠️ DEV-OPS) Set auto-deployment agent on all production deployments to scale 0 as default value

@matusdrobuliak66
Copy link
Contributor Author

(⚠️ DEV-OPS) I have seen some pending maintenance on AWS Production RDS: New Operating System Update is available

@mrnicegyu11
Copy link
Member

(⚠️ DEV-OPS) dalco prometheus was running out of RAM and was constantly restarting. I have on machine daclo01 manually decreased the retention time to 90d, which will propagate upon the next prod release (see: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/commit/f842e70a36c7d289a4dd41e6fc39c1786dc43115 ). Also, I have manually increased prometheus RAM on all production deployments.

Tasks during the release:

  • The monitoring stacks should be re-created on all deployments
  • It needs to be made sure that prometheus starts and runs stably for some minutes on all deployments
  • It needs to be made sure that the change of retention time to 90d on dalco is in place and no data shorter than 90d is somehow lost

@mrnicegyu11
Copy link
Member

@YuryHrytsuk and me looked at it, looks good. All devops changes acknowledged.

  • The deployment agent is already scaled to 0 replica on all production deployments
  • Other devops tasks listed are clear and actionable

@GitHK
Copy link
Contributor

GitHK commented Jul 12, 2023

ask me tomorrow to have a look for #4453

@GitHK
Copy link
Contributor

GitHK commented Jul 13, 2023

No issues on all 3 deployments with #4453
I'm OK to release

@matusdrobuliak66
Copy link
Contributor Author

Prolonging the release by 1. hour

@matusdrobuliak66
Copy link
Contributor Author

Release Notes:

  • release CI was confused when the already hotfix branch was prepared before the release
  • DB migration needed to be restarted on Dalco Production (during migration the container restarted which caused confusion for the DB)
  • Invitation service password needed to be manually changed (still problem with the special characters)

@matusdrobuliak66
Copy link
Contributor Author

Right after the release, we needed to modify the invitation password (remove special characters) in the invitation service env vars. DevOps will look into it.

@matusdrobuliak66
Copy link
Contributor Author

AWS DB upgrade was not done, should be done next time.

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

5 participants