[booth] pcs booth create ip IP shall not be allowed by the time config (/etc/booth/booth.conf) exists

[jnpkrn]

If pcs is supposed to be a tool of user's convenience, it cannot be told
about an enforcement of booth configuring steps.

For a starter (this issue), pcs booth create ip IP command shall fail unless there
is a configuration already present (presumably in sync) across in-cluster systems.

Currently, it allows that, and booth IP is happily up and running, while
booth-booth-service cannot start ... for a missing configuration file.

Instead, user shall be redirected to where the initial configuration can be
prepared (and in dreams, it would interactively start start such a process
in a wizard-like manner right away).

[tomjelinek]

The summary you wrote contradicts your comment. In the comment, you say the pcs booth create command should work only if the booth config file exists. The summary says otherwise.

[jnpkrn]

Seems like misinterpretation of what I wrote. Understanding of the
comment itself seems correct, however, and that's of merit here.

[tomjelinek]

Due to time constraints and other priorities, we haven't been able to implement these planned higher level booth commands which would be aware of the whole booth formation and which would be able to operate at a cluster level and booth formation level. For the users to be able to set booth at least somehow, only the node-level commands have been implemented. Those, even if not as comfortable as one may desire, provide a complete set of operations needed for configuring and managing booth.

The plans for the more comfortable booth management are still there. Unfortunately given current developer resources and backlog, it is a "blue-sky" project for now.