Should leader software be installed on _all_ pioreactors? But only a single pioreactor is still leader

[CamDavidsonPilon]

I'm thinking the use case is:

I have 10 pioreactors. I want to use 5 of them for one experiment (call this cluster A), and 5 for another experiment (cluster B). The existing leader can be used for cluster A - called leader A -, and inventory for cluster A can be assigned in the config. I choose another pioreactor for leader of cluster B - call this leader B -, edit the config to change the leader AND the (inverse) inventory (this needs to be done at the same time, as the config is only shipped to active workers in the inventory).

So when I go to http://leaderA.local I should see 5 pioreactors available, and 5 inactive. However, does http://leaderB.local work? No. There's no expectation that any of the leader software has been installed. The user would need to SSH in, and run make install-leader, and then reboot (however, I don't know if this messes with the config in an unpredictable way).

Should we install leader software, by default?

• If we did install leader software by default, we would need conditionals to avoid starting some systemd jobs, like avahi-alias, and pioreactorui.