Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[booth] pcs booth sync does not synchronize configuration to other clusters #226

Open
jnpkrn opened this issue Dec 9, 2019 · 4 comments

Comments

@jnpkrn
Copy link
Contributor

jnpkrn commented Dec 9, 2019

This especially makes that command useless when degenerate
single node clusters are considered, but nonetheless, the point of
the management tool is to make the typical workflows easy, and
"sync across the clusters" is one such typical use case for multisite
nonetheless -- that's exactly what you want to do with booth sync,
don't you?!

Relevant issue here: #224
Note that the motivation example there already works with the
mechanism of "virtual (booth) IP to cluster mapping", which is
exactly what fits into this picture. Good news is that pcsd listening
on [::]:* by default and, as tested, will gladly serve the requests
coming via a virtual IP introduced even once pcsd got started.

@tomjelinek
Copy link
Member

To sync booth configs across cluster, you do pcs booth pull and pcs booth sync, as documented. The documentation clearly says pcs booth sync works just in the local cluster.

The improvement you are proposing is reasonable and we will consider it once pcs has awareness of multiple sites.

@jnpkrn
Copy link
Contributor Author

jnpkrn commented Dec 10, 2019

Why do you close this issue then?

Also, that composition is borderline impractical & inconvenient,
and for said single node cluster, downright betraying since the
limited (and hence not applicable) usability vs. the expectations
attached to the verb sync as used here (it would be another
story if it was marked sync-within-site right away, apparently).

Certainly, there is a lot to left to be desired, hence this issue,
please keep it open, satisfactory resolution remains to be seen.

@jnpkrn
Copy link
Contributor Author

jnpkrn commented Jan 9, 2020

Regarding sync misnomer: #239

@tomjelinek
Copy link
Member

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.

@tomjelinek tomjelinek reopened this Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants