User talk:Andrew Bogott
- 1 Bots project
- 2 Shell access
- 3 Project clean-up/Checkwiki
- 4 Migrated SVN account renaming/clean-up
- 5 A barnstar for you!
- 6 Legitimate edit?
- 7 NonFreeWiki
- 8 Deployment-prep
- 9 Shell request
- 10 A cookie for you!
- 11 Query
- 12 Wiki Replica c1.labsdb to be rebooted Monday 2017-10-30 14:30 UTC
- 13 Wiki Replica c3.labsdb to be shutdown Wednesday 2017-12-13
Hello! May I join the Bots project? I have a bot which does not work in zh.wikipedia.org and I want to learn more about how to run and write an bot. Thanks! Chihonglee ◎Talk page 00:48, 18 December 2012 (UTC)
- Your best bet for joining Bots is to connect with someone on the wikimedia-labs channel. At the moment that project is largely run by volunteers many of whom lurk in that channel.
I believe you want to clean up some bitrot before the datacenter move: The project Checkwiki has moved to Tools and could therefore be removed if that is useful for you. --Tim Landscheidt (talk) 02:38, 11 December 2013 (UTC)
Migrated SVN account renaming/clean-up
Could you please reply here if/how User:Grafzahl could a) get the wikitech username "GrafZahl" and b) connect this account to his migrated SVN account? Thanks. --Tim Landscheidt (talk) 23:45, 24 May 2014 (UTC)
A barnstar for you!
|The Admin's Barnstar|
|For plugging away at getting Wikitech hooked up to the train. BryanDavis (talk) 17:25, 11 September 2014 (UTC)|
- I can't tell. If it is vandalism it is very subtle.
Thanks for creating this project (T108167) but I'm a little confused. I read the help page you pointed to but I can't work out where to find the project. I've seen the Nova resource but that has left me equally mystified. Thanks in advance. Green Giant (talk) 17:40, 9 August 2015 (UTC)
Hi Andrew, I'd like to join the Deployment-prep project. I'm an ops enthusiast and would love to help contribute to wikipedia.
- I don't have much connection with that project; best to check in with other admins or else pay a visit to #wikimedia-releng on IRC. andrew (talk) 03:59, 3 June 2016 (UTC)
|Thanks for repairing my account so I can be here :) MABot (talk) 19:33, 20 July 2017 (UTC)|
Hi Andrew. I hope that you're doing well. It's been some time that this happened and I wonder if it is still needed to have that log entry hidden :) I'm sure that there was some reason for this but if it's going to stay, for transparency I'd unhide it. I'll leave that to your decision though. Also, thanks again for fixing MABot, it's now working fine. Best regards, --MarcoAurelio (talk) 11:48, 5 August 2017 (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:20, 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.