Jump to content

User talk:Samwilson

Rendered with Parsoid
From Wikitech
Latest comment: 5 months ago by Komla Sapaty in topic Tool Migration from the Grid

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! petrb (talk) 11:33, 16 May 2013 (UTC)Reply

Welcome to Tool Labs

Hello Samwilson, 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) 15:47, 8 February 2015 (UTC)Reply

Thanks! Samwilson (talk) 22:47, 8 February 2015 (UTC)Reply

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)Reply

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)Reply

wsexport-test tool review

Hi, we're doing a review to make sure as many tools meet a minimum standard. I noticed wsexport-test tool doesn't have a published repo. Could you add this information to this tool? Thanks! Komla Sapaty (talk) 05:10, 7 April 2023 (UTC)Reply

@Komla Sapaty: Done. Thanks for the prompt! Although, I notice that the main tool account for that tool doesn't have any toolinfo; does that matter? My understanding was that Toolhub is now the canonical place for tool metadata (and WS Export is there). I'm also updating toolinfo.json for the tool (although I think perhaps there's a problem there with wsexport vs wsexport-test). Sam Wilson 07:05, 7 April 2023 (UTC)Reply
Thanks! Yes, Toolhub is now the canonical place for tool metadata. For now, we are checking both Toolhub and tools admin portal to check a set of information can be found in at least one of these two places. Komla Sapaty (talk) 17:29, 8 April 2023 (UTC)Reply
@Komla Sapaty: Should the toolinfo.json be deleted then? Because it probably doesn't make sense for it to be the same for both the prod and test instances anyway. Sam Wilson 03:09, 11 April 2023 (UTC)Reply

Tool Migration from the Grid

Hi samwilson, your tool is still running on the grid engine. According to the grid deprecation timeline that was shared, the grid will be stopped on the 14th of February. If you need assistance with the migration, kindly reach out on the phabricator ticket.

Please find the relevant ticket on Phabricator here T319746 Komla Sapaty (talk) 22:55, 1 February 2024 (UTC)Reply

@Komla Sapaty: Thank you! Done now. Sorry that it took me so long, I thought I'd done this ages ago. Sam Wilson 04:16, 2 February 2024 (UTC)Reply
Thank you for working on this! Komla Sapaty (talk) 20:50, 15 February 2024 (UTC)Reply