Feed Advanced Search
Jan 8 2023
Jan 8 2023
gitlab-migration changed the status of T2817: Enable the swh-search environment in staging from Resolved to Migrated.
gitlab-migration changed the status of T2816: Enable the journal-writer for the swh-idx-storage in staging from Resolved to Migrated.
gitlab-migration changed the status of T2428: Unstuck failing loaders in staging from Resolved to Migrated.
Oct 19 2022
Oct 19 2022
gitlab-migration changed the status of T3915: Deploy Bzr loader to the staging environment from Resolved to Migrated.
gitlab-migration closed T3772: Fix default collation configuration on staging databases as Migrated.
gitlab-migration changed the status of T3380: staging - Disk errors on storage1 from Resolved to Migrated.
gitlab-migration changed the status of T3243: Replace /dev/sdb and /dev/sdc on storage1.staging from Resolved to Migrated.
gitlab-migration changed the status of T3243: Replace /dev/sdb and /dev/sdc on storage1.staging, a subtask of T3236: staging: Disk error on storage1, from Resolved to Migrated.
gitlab-migration changed the status of T3236: staging: Disk error on storage1 from Resolved to Migrated.
gitlab-migration changed the status of T3159: Deploy swh-counters:v0.1.0 in staging from Resolved to Migrated.
gitlab-migration changed the status of T2920: Document staging infrastructure from Resolved to Migrated.
gitlab-migration changed the status of T2897: [staging] kafka data dir over 80% from Resolved to Migrated.
gitlab-migration changed the status of T2897: [staging] kafka data dir over 80%, a subtask of T2790: [staging] deploy the journal infrastructure, from Resolved to Migrated.
gitlab-migration changed the status of T2877: Investigate spurious deposit logs from Resolved to Migrated.
gitlab-migration changed the status of T2790: [staging] deploy the journal infrastructure from Resolved to Migrated.
gitlab-migration changed the status of T2790: [staging] deploy the journal infrastructure, a subtask of T2682: Deploy a small publicly available kafka server (with some content) on a staging (+ the related objstorage), from Resolved to Migrated.
gitlab-migration changed the status of T2770: Fix all icinga checks on staging webapp from Resolved to Migrated.
gitlab-migration changed the status of T2682: Deploy a small publicly available kafka server (with some content) on a staging (+ the related objstorage) from Resolved to Migrated.
gitlab-migration changed the status of T2628: Recycle ceph-osd2 as objstorage/storage backend for staging from Resolved to Migrated.
gitlab-migration changed the status of T2627: Recycle ceph-osd1 as staging database host from Resolved to Migrated.
gitlab-migration changed the status of T1995: swh-lister: Unstuck debian build failures, a subtask of T1875: staging infra: Reproduce existing production setup in a compact way, from Resolved to Migrated.
gitlab-migration changed the status of T1876: staging infra: Configure DNS zones, a subtask of T1785: Setup staging infrastructure, from Resolved to Migrated.
gitlab-migration changed the status of T1875: staging infra: Reproduce existing production setup in a compact way, a subtask of T1785: Setup staging infrastructure, from Resolved to Migrated.
gitlab-migration changed the status of T1874: staging infra: Setup gateway vm, a subtask of T1872: staging infra: New vlan, from Resolved to Migrated.
gitlab-migration changed the status of T1875: staging infra: Reproduce existing production setup in a compact way from Resolved to Migrated.
gitlab-migration changed the status of T1874: staging infra: Setup gateway vm from Resolved to Migrated.
gitlab-migration changed the status of T1872: staging infra: New vlan, a subtask of T2627: Recycle ceph-osd1 as staging database host, from Resolved to Migrated.
gitlab-migration changed the status of T1872: staging infra: New vlan, a subtask of T2628: Recycle ceph-osd2 as objstorage/storage backend for staging, from Resolved to Migrated.
gitlab-migration changed the status of T1872: staging infra: New vlan, a subtask of T1785: Setup staging infrastructure, from Resolved to Migrated.
gitlab-migration changed the status of T1785: Setup staging infrastructure from Resolved to Migrated.
gitlab-migration changed the status of T1711: Create a testing environment, a subtask of T1785: Setup staging infrastructure, from Resolved to Migrated.
Sep 9 2022
Sep 9 2022
Mar 25 2022
Mar 25 2022
Mar 23 2022
Mar 23 2022
Feb 18 2022
Feb 18 2022
douardda updated the task description for T2231: Continuous deployment.
douardda updated the task description for T2231: Continuous deployment.
douardda updated the task description for T2231: Continuous deployment.
Feb 16 2022
Feb 16 2022
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
Feb 15 2022
Feb 15 2022
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
New lister did its work, 74 new origins got seen [1] [2].
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
Feb 14 2022
Feb 14 2022
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
@Alphare fixed the sourceforge lister to list correctly bzr origins.
Tagged a v2.6.4 with that fix in the intent to deploy this on staging.
Feb 11 2022
Feb 11 2022
ardumont moved T3915: Deploy Bzr loader to the staging environment from in-progress to deployed/landed/monitoring on the System administration board.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
And deployed.
Next step: Actually feeding them some bzr origins.
We'll need to discuss some more with @Alphare.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
Of course, the build was ok, but not the actual install [1]
Another build release ongoing to fix that... [2]
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
After some more fight and backporting dependencies [1] [2]. The build is now happy on
stable as well [3].
Feb 10 2022
Feb 10 2022
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
Previous one fixed.
pypi-upload job failed for some reason.
Fixed.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
Yes, thanks for the heads up.
Alphare added a comment to T3915: Deploy Bzr loader to the staging environment.
D7130 has been committed, so a new version of the loader for faster ingestion will need to be released.
Feb 9 2022
Feb 9 2022
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
- Prepare the necessary debian metadata files to allow CI package build [1]
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
Here we go, first release is up. [1]
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
Repository configured correctly regarding the ci.
But the hook was missing on the repository.
Fixed [1].
Let's do the first release.
Feb 8 2022
Feb 8 2022
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
loader-bzr run in docker \o/:
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont changed the status of T3915: Deploy Bzr loader to the staging environment from Open to Work in Progress.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
- Make it run within docker
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
Feb 7 2022
Feb 7 2022
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont updated the task description for T3915: Deploy Bzr loader to the staging environment.
ardumont moved T3915: Deploy Bzr loader to the staging environment from Backlog to Weekly backlog on the System administration board.
ardumont added a comment to T3915: Deploy Bzr loader to the staging environment.
We got those bzr origins currently listed in staging (and prod) infra [1].
Do they sound good enough as dataset?
ardumont added a project to T3915: Deploy Bzr loader to the staging environment: System administration.
Alphare added a parent task for T3915: Deploy Bzr loader to the staging environment: T3610: Bazaar/Breezy loader.
Dec 6 2021
Dec 6 2021
Jul 29 2021
Jul 29 2021
ardumont moved T3159: Deploy swh-counters:v0.1.0 in staging from in-progress to done on the System administration board.
ardumont moved T2877: Investigate spurious deposit logs from deployed/landed/monitoring to done on the System administration board.
Jul 7 2021
Jul 7 2021
vsellier added a comment to T3380: staging - Disk errors on storage1.
This is the disk position according to a picture of the server taken by Christophe :
Jun 14 2021
Jun 14 2021
ardumont moved T3380: staging - Disk errors on storage1 from in-progress to deployed/landed/monitoring on the System administration board.
ardumont changed the status of T3380: staging - Disk errors on storage1 from Open to Work in Progress.
ardumont added a comment to T3380: staging - Disk errors on storage1.
A priori, zfs did itself the replace action, selecting one spare disk in the disks spare pool.
We needed only to detach the failing one, it's done. [1]
ardumont added a comment to T3380: staging - Disk errors on storage1.
Serial number:
root@storage1:~# smartctl -a /dev/disk/by-id/wwn-0x5000c500a23e4511 | grep -B1 "Serial Number" Device Model: ST6000NM0115-1YZ110 Serial Number: ZAD0SDDK
May 6 2021
May 6 2021
Actions performed:
- wwn-0x5000c500d5de652a(sdb) : new -> spare
- wwn-0x5000c500a22eed6f(sdh) : spare -> mirror
- wwn-0x5000c500d5dda886(sdc) : new -> mirror
vsellier closed T3243: Replace /dev/sdb and /dev/sdc on storage1.staging, a subtask of T3236: staging: Disk error on storage1, as Resolved.
vsellier added a comment to T3243: Replace /dev/sdb and /dev/sdc on storage1.staging.
The checks ran without detecting any bad block on the disk.
They can be added on the zfs pool again.
May 5 2021
May 5 2021
vsellier added a comment to T3243: Replace /dev/sdb and /dev/sdc on storage1.staging.
A full badblock test is launched on both disks:
root@storage1:~# badblocks -v -w -B -s -b 4096 /dev/sdb
root@storage1:~# badblocks -v -w -B -s -b 4096 /dev/sdc
vsellier added a comment to T3243: Replace /dev/sdb and /dev/sdc on storage1.staging.
The disk were replaced by Christophe.
Apparently, the led of one of the disk is still on, so they need to be switched off:
root@storage1:~# ls /dev/sd* | grep -e "[a-z]$" | xargs -n1 -t -i{} ledctl normal={}
ledctl normal=/dev/sda
ledctl normal=/dev/sdb
ledctl normal=/dev/sdc
ledctl normal=/dev/sdd
ledctl normal=/dev/sde
ledctl normal=/dev/sdf
ledctl normal=/dev/sdg
ledctl normal=/dev/sdh
ledctl normal=/dev/sdi
ledctl normal=/dev/sdj
ledctl normal=/dev/sdk
ledctl normal=/dev/sdl
ledctl normal=/dev/sdm
ledctl normal=/dev/sdnMay 3 2021
May 3 2021
vsellier added a comment to T3243: Replace /dev/sdb and /dev/sdc on storage1.staging.
The replacement disks were delivered at rocquencourt :
