@ABran-WMF Yes, I have no strong feeling about the database name, so what ever fits policy and naming conventions is absolutely fine.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Thu, Apr 18
Tue, Apr 16
Mon, Apr 15
Thu, Apr 11
Old Bullseye servers have been decommissioned.
Just to ensure that everyone agrees on what we need. This will be one Ganeti VM, running Bitu, and an LDAP instance.
Wed, Apr 10
Logs from idp1002 / idp2002 from 2023 and 2024 have been copied to idp1003 and idp2003 respectively, and are stored in /srv/logs
Mon, Apr 8
Wed, Apr 3
Bitu is currently installed as a .deb package on two Ganeti hosts.
Tue, Apr 2
For somethings I believe it should be fine, the AMD64 "emulation" is pretty good. We did see it struggle on the Puppet CLI container, to the point of it being somewhat painful to use. It boils down to whether or not the thing it runs is somewhat predictable or not. Interpreters aren't fast, but anything that's compiled is mostly workable.
Wed, Mar 27
Tue, Mar 26
Ranty is good :-)
Enabling of two-factor authentication is planed for after CAS 7 upgrade.
Update be deployed to production with next release.
Will be deployed with the update next Tuesday.
Mon, Mar 25
The latest Bookworm tzdata package already have the updated timezone for Kazakhstan as well, maybe we can just backport that one.
Fri, Mar 22
That fixed the synchronization with other services, but makes it slightly trigger to actually delete keys.
Thu, Mar 21
Okay, I see the issue. In order to not hit LDAP to much, keys are cached, but that's honestly no good as that gives the users a false impression of what keys are active.
@taavi patch has been rolled out on idm-test.wikimedia.org
VM creation: