Comment 5 for bug 1423613

This is a first (untested) approach to maas-clusterd.service.

This doesn't do the ExecStartPre= with the "A shared secret has not been installed for this cluster...." bits, as that's quite ugly -- you don't see this anywhere if you aren't on a console of the machine, and eventually it will time out and not restart automatically any more. This job will start if a secret exists, and just silently not start if there isn't one (and show you that the condition for the secret is failing, in systemctl status maas-clusterd).

This can be modelled with two jobs, one which waits for a secret to appear, which then starts maas-clusterd.service. But before I write such a thing, I'd be interested in the precise semantics of this. I. e. what creates the secret? Does that happen automatically, or does the user have to do that manually? How long should we wait for it?