Following a beta testing period [0] and a general use self-migration period [1], the Toolforge administration team is ready to begin the final phase of automatic migration of tools currently running on the legacy Kubernetes cluster to the 2020 Kubernetes cluster. The migration process will involve Toolforge administrators running `webservice migrate` for each tool in the same way that self-migration happens [2]. A small number of tools are using the legacy Kubernetes cluster outside of the `webservice` system. These tools will be moved using a more manual process after move all webservices. We are currently planning on doing these migrations in several batches so that we can monitor the load and capacity of the 2020 Kubernetes cluster as we move ~640 more tools over from the legacy cluster. Once the tools have all been moved to the 2020 cluster, we will continue with additional clean up and default configuration changes which will allow us to fully decommission the legacy cluster. We will also be updating various documentation on Wikitech during this final phase. We hope to complete this entire process by 2020-03-06 at the latest. [0]: https://lists.wikimedia.org/pipermail/cloud-announce/2020-January/000247.ht… [1]: https://lists.wikimedia.org/pipermail/cloud-announce/2020-January/000252.ht… [2]: https://wikitech.wikimedia.org/wiki/News/2020_Kubernetes_cluster_migration#… Bryan (on behalf of the Toolforge admins and the Cloud Services team) -- Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Wikimedia Cloud Services announce mailing list Cloud-announce(a)lists.wikimedia.org (formerly labs-announce(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud-announce _______________________________________________ Wikimedia Cloud Services mailing list Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/cloud

One question - I seem to be getting some more timeout-related 500 server errors. Was there a change in how that is handled somehow (i.e. reduced time limit for response from the server)? I realize it's good practice to respond quickly, just some of the existing cases don't at the moment and I'm hitting them occasionally.

On 2/23/20 8:51 PM, Arthur Smith wrote: memory Yes, you are right: https://wikitech.wikimedia.org/wiki/News/2020_Kubernetes_cluster_migration#… hope that helps. regards. -- Arturo Borrero Gonzalez SRE / Wikimedia Cloud Services Wikimedia Foundation