[heketi-devel] [heketi] Pre-existing GlusterFS cluster

Luis Pabon lpabon at gmail.com
Wed Jan 25 20:16:28 UTC 2017

Hi José,
  This has been asked for many many times.  Heketi was designed to "rule
them all".  Heketi was never designed for systems that have been setup
already because the permutations of possibilities of configurations could
be extensive to figure out how to manage.  It is like creating a Ceph Rados
system by yourself, then asking the pool manager to figure out what you
did.  If instead Ceph is viewed as a collection of the access+pool+storage
and not as individual parts, then it all works well and is predictable.  In
the same way, it should not be viewed as Heketi managing GlusterFS, but
Heketi/GlusterFS instead.  Once this view is accepted (which is what users
want, but old school gluster users have a hard time with), then what Heketi
currently does makes perfect sense.

So, back to the question, no, Heketi does not and will never manage such a
model.  Any software that manages such a configuration would be hard to
productize and guarantee.  Can you make a hack that does it? Maybe, but
reliability and simplicity is what Heketi is after.

Hope this answers your question.

- Luis

On Tue, Jan 24, 2017 at 12:24 PM, Jose A. Rivera <jarrpa at redhat.com> wrote:

> Hey Luis, et al.,
> I talked to Ashiq about $SUBJECT, and he raised some concerns.
> Apparently heketi can not load/import nodes that are already part of a
> Gluster cluster? E.g. if I have an existing cluster with all the nodes
> already peer probed, heketi will try to redo the probe and then fail
> when it comes back already in peer list? This seems odd to me, but if
> so sounds like a relatively easy thing to change. Thoughts?
> --Jose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/heketi-devel/attachments/20170125/6abcb96b/attachment.html>

More information about the heketi-devel mailing list