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.55.0 #4371

Closed
29 of 34 tasks
Tracked by #682
matusdrobuliak66 opened this issue Jun 15, 2023 · 13 comments
Closed
29 of 34 tasks
Tracked by #682

🚀 Release v1.55.0 #4371

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

Comments

@matusdrobuliak66
Copy link
Contributor

matusdrobuliak66 commented Jun 15, 2023

Release version

1.55.0

Commit SHA

48d29cda9cb81c570fbd329ec560eb0c2167321a

Previous pre-release

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

Did the commit CI suceeded?

  • The commit CI succeeded.

Motivation

n/a

Changes

Release Issue: #4397

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.55.0  git_sha=48d29cda9cb81c570fbd329ec560eb0c2167321a
  • Draft release changelog
  • Announce maintenance ( ** ANNOUNCE AT LEAST 24 HOURS BEFORE ** )
  • redis {"start": "2023-06-23T07:00:00.000Z", "end": "2023-06-23T08:15:00.000Z", "reason": "Release v1.55.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/v1.55.0
@matusdrobuliak66 matusdrobuliak66 added t:maintenance Some planned maintenance work release Preparation for pre-release/release labels Jun 15, 2023
@matusdrobuliak66 matusdrobuliak66 self-assigned this Jun 15, 2023
@matusdrobuliak66 matusdrobuliak66 changed the title 🚀 Release v<1.55.0> 🚀 Release v1.55.0 Jun 15, 2023
@mrnicegyu11
Copy link
Member

The deployment agent on aws-prod is paused since there were faulty env-vars for the invitations service. The env-vars have been adjusted manually in portainer

@mrnicegyu11
Copy link
Member

We tried to put the fix in here, please double check upon releasing that especially the INVITATION_PASSWORD is correctly set on the service's env-vars, and not truncated after the dollar sign

https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/commit/e6828f94b150cad47034111675923fbbdc84be5f

@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Jun 22, 2023

The deployment agent is paused, the faulty variable of AUTOSCALING_EC2_INSTANCES_PRE_PULL_IMAGES on the autoscaling service was corrected and is now set to

["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.

@sanderegg
Copy link
Member

The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to

["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.

@mrnicegyu11
Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.

@mrnicegyu11
Copy link
Member

The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to

["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.

@mrnicegyu11 Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.

Sounds good I will put this in place on aws-prod now, we can then see how it looks/feels.

New env-var is: ["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

@mrnicegyu11
Copy link
Member

The deployment agent is paused, the faulty variable of `` on the autoscaling service was corrected and is now set to

["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","prom/node-exporter:v0.18.1","portainer/agent:2.13.1","docker:20.10.14-dind","caddy:2.4.5-alpine","gcr.io/cadvisor/cadvisor:v0.45.0","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

I just noticed that this is not necessarily in sync with the actually used ops-containers, for example the portainer version is for sure outdated. I will open an issue about this.

@mrnicegyu11 Maybe we should just remove those ops ones. the images are not so big I think so that should not make a huge difference.

Sounds good I will put this in place on aws-prod now, we can then see how it looks/feels.

New env-var is: ["itisfoundation/dynamic-sidecar:release-github-latest","itisfoundation/agent:release-github-latest","registry.osparc.io/simcore/services/dynamic/s4l-core-lite:2.0.106"]

Fixed in https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/commit/6412871d2dea6caf396574689babf97910e0e1ab

@matusdrobuliak66 matusdrobuliak66 added this to the Watermelon milestone Jun 22, 2023
@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Jun 22, 2023

Please restart the following ops-services and thus roll out the latest ops-code from osparc-ops-environments on prod:

  • filestash
  • jaeger
  • monitoring
  • registry
  • (ops) traefik
  • graylog
  • portainer

on aws-prod, dalco-prod and tip.itis.swiss.

Grafana and Graylog Alerts need to be re-provisioned.

@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Jun 22, 2023

In order for the grafana dashboard to work, the old proper hostnames (instance prometheus labels) need to be restored. Potentially a full teardown and recreation of the swarm is necessary for this.

See: ITISFoundation/osparc-ops-environments#182

@odeimaiz
Copy link
Member

Please include this commit as hotfix

@Surfict
Copy link
Contributor

Surfict commented Jun 23, 2023

  • Swarm was recreated
  • Some problems to start the deploy script in aws production, ticket will be created
  • The pwd for invitation service was not set correctly (keeping two $), I paused the deployemnt agent in aws production and set the good password manually in the service. An issue will be created
  • We need documentation about how to run the swarm recipes in Ansible for the different uses cases

@pcrespov
Copy link
Member

@matusdrobuliak66
Copy link
Contributor Author

Invitations:

  • INVITATIONS_OSPARC_URL
  • INVITATIONS_PASSWORD
    were manually modified in the Portainer

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

6 participants