Comment 1 for bug 1885893

I think the request here is to add a --limit or --sequential or --slow flag to juju deploy, to reduce the number of machines it will try to spin up simultaneously.

Either that, or we'd want to be able to control the timeout or number of retries when allocating a machine. (Overall, though, I think it would be preferred to limit the number of retries we need in the first place, rather than soaking the connection and then trying to handle the consequences after the fact.)