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.

Sign up for GitHub

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

Jump to bottom

🚀 Release v1.52.0 #4140

Closed
23 of 26 tasks
matusdrobuliak66 opened this issue Apr 20, 2023 · 9 comments
Closed
23 of 26 tasks

🚀 Release v1.52.0 #4140

matusdrobuliak66 opened this issue Apr 20, 2023 · 9 comments
Assignees
@matusdrobuliak66
Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Milestone
Jelly Beans

Comments

@matusdrobuliak66
Copy link
Contributor

matusdrobuliak66 commented Apr 20, 2023 •
edited
Loading

Release version

1.52.0

Commit SHA

49ee3cdc8bacd6d557f0aff68b1da2c0b6eb947a

Previous pre-release

https://github.com/ITISFoundation/osparc-simcore/releases/tag/staging_JellyBeans2

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

  • Regular release

Changes

Staging Mithril5

Release Issue: #4054

Staging Mithril6

Release Issue: #4058

Staging JellyBeans1

Release Issue: #4115

Staging JellyBeans2

Release Issue: #4135

Devops check 👷

Tests assessment: e2e testing check 🧪

  • aws staging - good
  • dalco staging - good (tiplan failing)

Test assessment: targeted-testing 🔍️

No response

Test assessment: user-testing 🧐

No response

Summary 📝

  • Prepare release link
make release-prod version=1.52.0 git_sha=49ee3cdc8bacd6d557f0aff68b1da2c0b6eb947a
  • Draft release changelog
  • Announce maintenance ( ** ANNOUNCE AT LEAST 24 HOURS BEFORE ** )
  • redis {"start": "2023-04-24T06:00:00.000Z", "end": "2023-04-24T10:00:00.000Z", "reason": "Release <v1.52.0>"}
    • aws
    • dalco
    • tip
  • status page (https://manage.statuspage.io/)
    • osparc
    • s4l
  • mattermost channels
    • maintenance
    • power users

Releasing 🚀

  • Maintenance page up.
  • Release by publishing draft
  • Check release CI
  • Check deployed
    • aws deploy
    • dalco deploy
    • tip deploy
  • Delete announcement
  • Check e2e runs
  • Announce
:tada: https://github.com/ITISFoundation/osparc-simcore/releases/tag/v1.52.0
@matusdrobuliak66 matusdrobuliak66 added the t:maintenance Some planned maintenance work label Apr 20, 2023
@matusdrobuliak66 matusdrobuliak66 self-assigned this Apr 20, 2023
@matusdrobuliak66 matusdrobuliak66 changed the title 🚀 Release v<M.m.0> 🚀 Release v1.52.0 Apr 20, 2023
@matusdrobuliak66
Copy link
Contributor Author

@Surfict @mrnicegyu11 I would like to announce the maintenance for users. Please can we decide when and for how long the maintenance page should be up? For example, can we do it Monday morning 8 am? Thanks.

@mrnicegyu11
Copy link
Member

Timing is fine for me personally, this is pending approval from @Surfict .
We will reboot each node individually one at-a-time, which will likely take 2-4 hours across all 3 prod deployments. Potentially, we will do some tests with the maintenance page if @Surfict managed to create their setup.

@pcrespov
Copy link
Member

@matusdrobuliak66 would it make sense to release first only the work in Mithril and then the rest? Not a must but this way we keep the rule that we have at least one release per sprint .

@matusdrobuliak66
Copy link
Contributor Author

matusdrobuliak66 commented Apr 20, 2023 •
edited
Loading

Timing is fine for me personally, this is pending approval from @Surfict . We will reboot each node individually one at-a-time, which will likely take 2-4 hours across all 3 prod deployments. Potentially, we will do some tests with the maintenance page if @Surfict managed to create their setup.

Ok after discussion we agreed to do it exceptionally at Monday morning 8 am as we will announce the maintenance for 4 hours.

@matusdrobuliak66 matusdrobuliak66 added this to the Jelly Beans milestone Apr 20, 2023
@mrnicegyu11
Copy link
Member

In checked the devops warnings, all good.

Actionable items:

  • Set env var STUDIES_DEFAULT_SERVICE_THUMBNAIL="" (overwrite default with emptystring as agreed with @odeimaiz )

@pcrespov
Copy link
Member

pcrespov commented Apr 20, 2023 •
edited
Loading

Actionable items:

  • Set env var STUDIES_DEFAULT_SERVICE_THUMBNAIL="" (overwrite default with emptystring as agreed with @odeimaiz )

@mrnicegyu11 if you look carefully at the jsonscheam of STUDIES_DEFAULT_SERVICE_THUMBNAIL you will notice that if you setup that to an empty string, the validation will fail! Either write a proper URL or leave the code default. :-)

Typically the assets should go in https://github.com/ITISFoundation/osparc-assets/tree/main/assets

I see e.g. that @elisabettai added a default thumbnail there

STUDIES_DEFAULT_SERVICE_THUMBNAIL=https://raw.githubusercontent.com/ITISFoundation/osparc-assets/60701745000f61261705f8f54c390715797f69f8/assets/default-thumbnail-cookiecutter-osparc-service.png

@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Apr 21, 2023 •
edited
Loading

We need to set

AUTOSCALING_EC2_INSTANCES_CUSTOM_BOOT_SCRIPTS='["mkfs --type xfs -f -n ftype=1 /dev/nvme1n1","mkdir --parents /mnt/docker","mount /dev/nvme1n1 /mnt/docker","jq '\''.\"data-root\"=\"/mnt/docker/data\",.\"exec-root\"=\"/mnt/docker/exec\"'\'' /etc/docker/daemon.json  > /tmp/daemon.json","mv /tmp/daemon.json /etc/docker/daemon.json","jq '\''. += { \"data-root\": \"/docker\", \"log-driver\": \"gelf\", \"log-opts\": {\"gelf-address\": \"udp://0.0.0.0:12201\"}, \"default-address-pools\" : [{\"base\" : \"172.17.0.0/12\",\"size\" : 20},{\"base\" : \"192.168.0.0/16\",\"size\" : 24}] }'\'' /etc/docker/daemon.json > tmp.json && mv tmp.json /etc/docker/daemon.json","systemctl restart docker"]'

To make logging in autoscaled nodes work

@pcrespov pcrespov added the release Preparation for pre-release/release label Apr 21, 2023
@GitHK
Copy link
Contributor

GitHK commented Apr 24, 2023 •
edited
Loading

Logout seemed to work good on Dalco staging and prod, all services were closed.
On AWS production 4 sidecars were still running normally. They shut down via the director-v2's cli without any issue. Prior to the maintenance there were 8-10 sidecars running normally.

@Surfict
Copy link
Contributor

Surfict commented Apr 24, 2023

  • Maintenance page tested with success in aws production
  • Portainer cron jobs deployed on all stacks with ansible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matusdrobuliak66 matusdrobuliak66

Labels
release Preparation for pre-release/release t:maintenance Some planned maintenance work
Projects
None yet
Milestone
Jelly Beans
Development

No branches or pull requests
5 participants
@Surfict @GitHK @mrnicegyu11 @pcrespov @matusdrobuliak66