User talk:Sebastian Berlin (WMSE)
Shell access
When a Labs project's administrator adds you to his project, you will automatically be given shell access. To do that, please contact the administrator of the Labs project you want to work on. --Tim Landscheidt (talk) 01:38, 22 April 2016 (UTC)
- @Tim Landscheidt: I just tried adding Sebastian to tools.fikarummet but his name doesn't even appear when I try to manage members. Is there another step which is missing? /Lokal_Profil (talk) 08:42, 7 June 2016 (UTC)
- Yes, Sebastian was not a member of the Tools project. I have just added him, and you should now be able to add him as a maintainer for a tool. --Tim Landscheidt (talk) 17:49, 7 June 2016 (UTC)
- Perfect. Many thanks! /Lokal_Profil (talk) 08:39, 8 June 2016 (UTC)
- Yes, Sebastian was not a member of the Tools project. I have just added him, and you should now be able to add him as a maintainer for a tool. --Tim Landscheidt (talk) 17:49, 7 June 2016 (UTC)
Welcome to Tool Labs
Hello Sebastian Berlin (WMSE), welcome to the Tool Labs project! Your request for access was processed and you should be able to log in now with ssh at login.tools.wmflabs.org. To get started, check the help page. You can also ask in our IRC channel at #wikimedia-labs connect or send an e-mail to our mailing list labs-l@lists.wikimedia.org – thank you, and have fun using Tools! --Tim Landscheidt (talk) 17:49, 7 June 2016 (UTC)
Wiki Replica c1.labsdb to be rebooted Monday 2017-10-30 14:30 UTC
A tool you maintain is hosting data on labsdb1001.eqiad.wmnet (aka c1.labsdb). This server will be rebooted Monday 2017-10-30 at 14:30 UTC.
Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the labsdb1003.eqiad.wmnet (aka c3.labsdb). The c1.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until the reboot is complete.
There is a possibility of catastrophic hardware failure in this reboot. There will be no way to recover the server or the data it currently hosts if that happens. Tools that are hosting self-created data on c1.labsdb will lose that data if there is hardware failure. If you are unsure why your tool is hosting data on c1.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/.
This reboot is an intermediate step before the complete shutdown of the server on Wednesday 2017-12-13. See Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 00:22, 28 October 2017 (UTC)
Wiki Replica c3.labsdb to be shutdown Wednesday 2017-12-13
A tool you maintain is hosting data on labsdb1003.eqiad.wmnet (aka c3.labsdb). This server will be taken out of service on Wednesday 2017-12-13.
Normal usage of the *.labsdb databases should experience only limited interruption as DNS is changed to point to the new Wiki Replica cluster. The c3.labsdb service name will not be updated however, so tools hardcoded to that service name will be interrupted until they are updated to use a new service name.
Tools that are hosting self-created data on c3.labsdb will lose that data if it is not migrated to tools.db.svc.eqiad.wmflabs (also known as tools.labsdb). If you are unsure why your tool is hosting data on c3.labsdb, you can check the database and table names at https://tools.wmflabs.org/tool-db-usage/ or phab:P6313.
Please see Wiki Replica c1 and c3 shutdown for more information. --BryanDavis 20:37, 15 November 2017 (UTC)