Apparently the order was lost somewhere after it was sent to dell the 6th april 🤔
It was reissued yesterday...

The clearly-defined dump is backuped on /srv/storage/space/mirrors/clearly-defined/clearcode-dump-2021-01-05/clearcode_backup-20210105-2111.dump

changing the status to resolved as all the subtasks are done. feel free to reopen if it shouldn't.

just one question inline regarding the icinga test name.
Otherwise, looks good

lgtm

• he was not in the list of members of the swh-team (thanks @ardumont for adding me to the owners of the list)

• unix credentials disabled
• user tenma removed from the groups Staff and Reviewers in phabricator
• VPN credential revoked:

root@louvre:~# cd /etc/openvpn/keys
root@louvre:/etc/openvpn/keys# ls
dh1024.pem  dh2048.pem	easyrsa  old  pki  vars  x509-types
root@louvre:/etc/openvpn/keys# ./easyrsa revoke tenma

I'm not a big fan of the random pickup of repo because it adds entropy on the result, but otherwise it's great to be able to monitor this 👍

closing this issue as the quota of disks replacement will be over after T3243.
The disk on db1 looks stable for the moment. It will be removed from the zfs pool in case of problems.

The compression and the transfer of the dump from clearly-defined server to saam is in progress.

ssh clearly-defined.internal.staging.swh.network "pbzip2 -c -9 /srv/softwareheritage/clearlydefined/clearcode-dump-2021-01-05/clearcode_backup-20210105-2111.dump" | pv | cat > clearcode_backup-20210105-2111.dump.bz2

When it will be done, and if the compression ratio is good, the compressed archive will be added to the public annex in a dataset/clearly-defined directory

According to https://intranet.softwareheritage.org/wiki/Outboarding:

• tg19999 unix account disabled

*TG1999 removed from interns members in the forge, no tasks were assigned to the user

• He was not on the #swh-team channel
• He was not a member of the swh-team ml
• VPN certificated revoked

root@louvre:/etc/openvpn/keys# ./easyrsa revoke tg1999

thanks, I will move the dump in a secure place where it will be backuped.

Email sent to the dsi to launch the replacement.

In preparation of the disk replacement, their leds must be activated to make the emplacement identifiable:

• Ensure all the led are 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/sdn

• light on

root@storage1:~# ledctl locate=/dev/sdb
root@storage1:~# ledctl locate=/dev/sdc

I would really like to keep the author counter: how complex is it to add it?

Staging webapp[1] and webapp1 on production [2] are now configured to use swh-counters to display the historical values and the live object counts.

Deployment done on staging and production. The new counters are currently only activated on webapp1

fix a typo on the commit description

• version 0.1.296(swh2) released and deployed on all the webapp

lgtm

rename the object variable