User talk:Baku
Your shell access was granted
Hello, welcome to Wikimedia Labs! I would like to inform you that your shell request was processed and you should be able to login to Bastion host now at bastion.wmflabs.org. In case you get into troubles, please read this page which contains useful information about accessing instances. 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 labs! Tim Landscheidt (talk) 16:46, 1 August 2014 (UTC)
Welcome to Tool Labs
Hello Baku, welcome to the Tool Labs project! Your request for access was processed and you should be able to login now via ssh at tools-login.wmflabs.org. To get started, check the help page and the migrating from the Toolserver 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) 16:50, 1 August 2014 (UTC)
Your tools access request problem
I saw your access request that says you are having a problem logging into tools. The problem you are receiving is because you are not using the SSH key that you (should) have uploaded to the OpenStack section of Special:Preferences and Gerrit. You should listen to the advice of the shell console and read Help:Access#Accessing_public_and_private_instances and Nova Resource:Tools/Help. In the future you should ask one of the administrators listed at Nova Resource:Tools (in the side bar) if you are having problems. Cheers, -24Talk 22:01, 4 August 2014 (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:21, 28 October 2017 (UTC)