Per our announcement on 2019-01-11 [0], the Ubuntu Trusty job grid is deprecated and jobs running there need to be manually moved to either the replacement Debian Stretch job grid or the Toolforge Kubernetes cluster.

Starting today (2019-02-07) the maintainers of tools that have been seen to run jobs on the Trusty grid will receive email notices with the subject "[Toolforge] Tools you maintain are running on Trusty job grid". These reminders will go out each Thursday through 2019-03-07. At that point we will increase the frequency of reminders to daily until we reach the Trusty job grid shutdown date in the last week of March.

Please see the Toolforge Trusty deprecation news page on wikitech [1] for more information on how to migrate your grid jobs and things to watch out for in the process.

== What is changing? == * New job grid running Son of Grid Engine on Debian Stretch instances * New limits on concurrent job execution and job submission by a single tool * New bastion hosts running Debian Stretch with connectivity to the new job grid * New versions of PHP, Python2, Python3, and other language runtimes * New versions of various support libraries

== What should I do? == The Cloud Services team has created the Toolforge Trusty deprecation[1] page on wikitech.wikimedia.org to document basic steps needed to move webservices, cron jobs, and continuous jobs from the old Trusty grid to the new Stretch grid. That page also provides more details on the language runtime and library version changes and will provide answers to common problems people encounter as we find them. If the answer to your problem isn't on the wiki, ask for help in the #wikimedia-cloud IRC channel or file a bug in Phabricator[2].

[0]: https://lists.wikimedia.org/pipermail/cloud-announce/2019-January/000122.htm... [1]: https://wikitech.wikimedia.org/wiki/News/Toolforge_Trusty_deprecation [2]: https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?title=Stretch+...

Thanks, Bryan (on behalf of the Toolforge administration team)