In the bold new world of high availability, bin/phd start should do the right thing by default no matter where you launch it. In particular:
- The PullLocal daemon needs to become smart about making sure the repository is supposed to exist on the current host, and we should drop the --no-discovery and repository selection flags.
- This is probably not difficult, but needs some finesse/communication for existing installs.
- The bin/repository subcommands can still force action on a repository on the current host (although maybe they should prompt if the repository is not naturally local to the host).
- This runs into T4292 to some degree.
- The Trigger daemon is fine to launch everywhere, but its locking may need to be more fine-grained or forgiving. This won't scale up cleanly with the number of instances, but no install should ever be pushing the trigger daemon to its limits.
- The Taskmaster daemons seems reasonable to boot up as an autoscale group of the default size.
- The documentation should be updated to reflect this state of the world.
We should also revisit the UI, particularly with an eye toward making it more useful for figuring out which host a daemon is running on (T6768) and improving usability (T7307). There are a handful of cheap adjacent tasks which make sense to pick up here since testing them is cheap (T9385, T7475, probably T6615 now that key changes are cheap).