[heketi-devel] Question regarding heketi topology and clusterid/nodeid

Raghavendra Talur rtalur at redhat.com
Fri Apr 12 12:38:23 UTC 2019


On Thu, Apr 11, 2019 at 9:09 PM Grumboeck Johannes (POI - AT/Salzburg) <
johannes.grumboeck at porscheinformatik.at> wrote:
>
> Hi,
>
>
>
> I’m looking into the heketi topology and trying to find how this
information
>
> ties together with the actual “real” glusterfs installation.
>
> I can link brick ids to brick LV names, device ids to VG names
>
> but I’m stuck with the clusterid and nodeid.
>
>
>
> Are clusterid and nodeid something heketi uses only internally and are not
>
> directly connected to something within glusterfs?

Yes, in glusterd there is no concept of clusterid. It is an id that heketi
creates to refer to a particular cluster.

Nodeid: glusterd generates a node id for all peers in the cluster but the
nodeid in heketi topology info is "local" only to heketi as it has to
create the nodeid before the peer probe command.

>
>
>
> Thanks for your assistance.
>
> Johannes
>
>
>
> Mit freundlichen Grüßen / Best regards
>
>
>
> i.A. Dipl.-Ing.(FH) Johannes Grumböck
>
> Infrastructure Architect, Computing & Platform Services
>
> Infrastructure & Common Platforms
>
>
>
> Telefon +43 (0)662 4670-6323
>
> Telefax +43 (0)662 4670-16323
>
> johannes.grumboeck at porscheinformatik.at
>
>
>
> Porsche Informatik Gesellschaft m.b.H. | A – 5020 Salzburg |
Louise-Piëch-Straße 9
>
> Sitz: Salzburg | FN 72830 d / Landesgericht Salzburg | DVR 88439 | UID
ATU 36773309
>
> http://www.porscheinformatik.at/
>
>
>
>
> Internal
>
> _______________________________________________
> heketi-devel mailing list
> heketi-devel at gluster.org
> https://lists.gluster.org/mailman/listinfo/heketi-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/heketi-devel/attachments/20190412/762ebda3/attachment.html>


More information about the heketi-devel mailing list