Page MenuHomeSoftware Heritage
Create Task
Maniphest T3918

Deploy swh-vault workers v1.4.2 on prod and staging
Closed, MigratedEdits Locked
Actions

Description

you just need to make sure the swh-storage api the workers query have version >=v0.43.0

plan (staging then prod):

  • check the python3-swh.storage version (of the api used by the workers)
  • Upgrade storage module on storage server (if required)
  • Upgrade python3-swh.vault on vault workers (bump swh.model as welll if required)
  • Restart swh-worker@vault_cooker
  • Upgrade workers to latest python3-swh.vault version
  • Check cooking is still ok

Related Objects

Event Timeline

vlorentz triaged this task as Normal priority.Feb 8 2022, 11:53 AM
vlorentz created this task.
vlorentz mentioned this in D7120: Allow vault cooking from the UI.Feb 8 2022, 11:56 AM
ardumont moved this task from Backlog to Weekly backlog on the System administration board.Feb 8 2022, 12:25 PM
ardumont changed the task status from Open to Work in Progress.Feb 8 2022, 1:53 PM
ardumont updated the task description. (Show Details)
ardumont moved this task from Weekly backlog to in-progress on the System administration board.
ardumont added a comment.Feb 8 2022, 2:02 PM
  • Check storage server api version:
ardumont@vault:~% hostname -f
vault.internal.staging.swh.network
ardumont@vault:~% sudo grep 5003 /etc/softwareheritage/vault/server.yml
    url: http://storage1.internal.staging.swh.network:5003/
ssh storage1.internal.staging.swh.network dpkg -l python3-swh.storage | grep ii
ii  python3-swh.storage 0.43.0-1~swh1~bpo10+1 all          Software Heritage storage utilities
  • Might as well upgrade the storage to the latest version
root@storage1:~# dpkg -l python3-swh.storage | grep ii
ii  python3-swh.storage 0.43.1-1~swh1~bpo10+1 all          Software Heritage storage utilities
root@storage1:~# systemctl reload-or-restart gunicorn-swh-storage.service
  • Check vault version:
ardumont@vault:~% dpkg -l python3-swh.vault | grep ii
ii  python3-swh.vault 1.3.0-1~swh1~bpo10+1 all          Software Heritage Vault
root@vault:~# apt upgrade -y
...
Setting up python3-swh.vault (1.4.2-1~swh1~bpo10+1) ...
...
root@vault:~# dpkg -l python3-swh.vault | grep ii
ii  python3-swh.vault 1.4.2-1~swh1~bpo10+1 all          Software Heritage Vault
root@vault:~# systemctl reload-or-restart gunicorn-swh-vault.service
root@vault:~#
ardumont updated the task description. (Show Details)Feb 8 2022, 2:32 PM
ardumont renamed this task from Deploy swh-vault v1.4.2 on prod and staging to Deploy swh-vault workers v1.4.2 on prod and staging.Feb 8 2022, 2:36 PM
ardumont updated the task description. (Show Details)
ardumont added a comment.Feb 8 2022, 2:50 PM

In the end, the plan is more simple

14:44 <+ardumont> so only (cooker) workers need an upgrade of the vault package (and the storage api they use need at least v0.43) right?
14:45 <+vlorentz> yes
ardumont updated the task description. (Show Details)Feb 8 2022, 2:51 PM
ardumont added a comment.Feb 8 2022, 2:53 PM

ongoing upgrade for production workers.

ardumont moved this task from in-progress to deployed/landed/monitoring on the System administration board.Feb 8 2022, 5:08 PM
ardumont closed this task as Resolved.Feb 8 2022, 5:19 PM
ardumont moved this task from deployed/landed/monitoring to done on the System administration board.
gitlab-migration changed the task status from Resolved to Migrated.Oct 19 2022, 6:05 PM
gitlab-migration claimed this task.
gitlab-migration added subscribers: ardumont, gitlab-migration.

This task has been migrated to GitLab.

About · Developer information · Legal