1. Move hosts that currently have A02s and MotoG4 attached from prod to staging.
   1. Send PSA about reduced capacity.
   2. Move half from prod to staging.
   3. Edit .ci.yaml to add bringup: true.
   4. Move the other half from prod to staging.
2. Replace A02s's and MotoG4's on those hosts with Mokeys
   1. Ask Kent to do it by filing GitHub issues and emailing.
3. Switch tests from running on A02s's and MotoG4s to running on Mokey's.
   1. All in one go.
4. Move hosts with Mokey's from staging to prod.
   1. Move half of hosts with Mokeys from staging to prod
   2. Edit the .ci.yaml to remove bringup: true from the tests on Mokey
   3. Move the rest of the hosts with Mokeys from staging to prod
   4. Send PSA that migration is complete.

Yusuf wrote up this doc to describe where we'd like to get to for how devices are allocated in the lab across pools and devices: go/flutter-devicelab-testbed-matrix

Current allocation between try, staging, and prod pools can be queried in https://chromium-swarm.appspot.com/botlist.

We can move hosts between staging and prod by editing:
https://chrome-internal.googlesource.com/infradata/config/+/refs/heads/main/configs/chromium-swarm/starlark/bots/flutter.star. There are extra steps that I don't know to check in extra files that are generated from the .star files.

Kent: nguyenkent@