Closed matusdrobuliak66 closed 1 year ago
@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.
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.
@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 .
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.
In checked the devops warnings, all good.
Actionable items:
STUDIES_DEFAULT_SERVICE_THUMBNAIL=""
(overwrite default with emptystring as agreed with @odeimaiz )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
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
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.
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?
Motivation
Changes
Staging Mithril5
Release Issue: https://github.com/ITISFoundation/osparc-simcore/issues/4054
Staging Mithril6
Release Issue: https://github.com/ITISFoundation/osparc-simcore/issues/4058
Staging JellyBeans1
Release Issue: https://github.com/ITISFoundation/osparc-simcore/issues/4115
Staging JellyBeans2
Release Issue: #4135
Devops check ๐ท
Tests assessment: e2e testing check ๐งช
Test assessment: targeted-testing ๐๏ธ
No response
Test assessment: user-testing ๐ง
No response
Summary ๐
{"start": "2023-04-24T06:00:00.000Z", "end": "2023-04-24T10:00:00.000Z", "reason": "Release <v1.52.0>"}
Releasing ๐