From container-build-reports at centos.org Mon Apr 1 20:51:09 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 01 Apr 2019 20:51:09 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca279bd.x592qiSDqLZBDjPZ%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 7a60644f7212a0c94f5ecaa999030c3a0eda4bce to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Mon Apr 1 20:53:41 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 01 Apr 2019 20:53:41 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca27a55.ofHGv2PXqgx4+SZC%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 7a60644f7212a0c94f5ecaa999030c3a0eda4bce to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Mon Apr 1 21:10:39 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 01 Apr 2019 21:10:39 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca27e4f.XjVqR7KxmBbKtZyX%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit dd0b3898f87811dbd36a24233a4c9578e07dadf0 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Mon Apr 1 21:13:41 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 01 Apr 2019 21:13:41 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca27f05.GkJqP2F4gPClBer9%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit dd0b3898f87811dbd36a24233a4c9578e07dadf0 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 2 02:00:50 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 02 Apr 2019 02:00:50 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca2c252.YvMDtKbNE6Ahtxs8%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit ed8ab190a87169b84192a2d9f2452865f85b9fed to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 2 02:03:40 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 02 Apr 2019 02:03:40 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca2c2fc.hdIKBfJWVkXifGsK%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit ed8ab190a87169b84192a2d9f2452865f85b9fed to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 2 12:03:47 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 02 Apr 2019 12:03:47 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca34fa3./wSruJG3Ec4CRtCn%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 8417f25f474b0b16e1936a66f9b63bcedfba6e4c to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 2 12:10:41 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 02 Apr 2019 12:10:41 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca35141.ETrrhYHeL++aEhBY%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Wed Apr 3 22:53:46 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 03 Apr 2019 22:53:46 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca5397a.CbB/R8E2j5ea61OU%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 0d18b86a61bafef488e22ebf18286a969fc5d31c to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Wed Apr 3 23:00:38 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 03 Apr 2019 23:00:38 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca53b16.nHsJ6L6KzrMTvH3L%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Thu Apr 4 04:03:47 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Thu, 04 Apr 2019 04:03:47 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca58223.NEN8X9A98o+lzYLa%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 68b9e094a7fa8f65af1dc1625383704a5c5fef84 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Thu Apr 4 04:10:37 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Thu, 04 Apr 2019 04:10:37 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca583bd.wHXml1S9N8LZQtKx%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 68b9e094a7fa8f65af1dc1625383704a5c5fef84 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Thu Apr 4 20:41:07 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Thu, 04 Apr 2019 20:41:07 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca66be3.UUxLLCTGcfzHV1I4%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 891a99667d82b04208dfe7d55567f17b05f0cc18 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Thu Apr 4 20:43:37 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Thu, 04 Apr 2019 20:43:37 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca66c79.jTXo254cA3Hb4TcY%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 891a99667d82b04208dfe7d55567f17b05f0cc18 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Fri Apr 5 18:50:53 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 05 Apr 2019 18:50:53 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5ca7a38d.Eyj+nRs+5SZwtXKj%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Fri Apr 5 18:53:39 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 05 Apr 2019 18:53:39 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5ca7a433.WgwRpNxEnhHdeFAD%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit a354187e751df5edc5ec6688108faa9cc463d7c3 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From phlogistonjohn at asynchrono.us Fri Apr 5 19:30:29 2019 From: phlogistonjohn at asynchrono.us (John Mulligan) Date: Fri, 05 Apr 2019 15:30:29 -0400 Subject: [heketi-devel] Heketi v9.0.0 available for download Message-ID: <2297373.DkY5oybNEL@abydos> Heketi v9.0.0 is now available [1]. This is the new stable version of Heketi. Major additions in this release: * Limit volumes per Gluster cluster * Prevent server from starting if db has unknown dbattributes * Support a default admin mode option * Add an option to enable strict zone checking on volume creation * Add automatic pending operation clean-up functionality * Configurable device formatting parameters * Add consistency check feature and state examiner debugging tools * The faulty and non-functional "db delete-pending-entries" command has been removed This release contains numerous stability and bug fixes. A more detailed changelog is available at the release page [1]. -- John M. on behalf of the Heketi team [1] https://github.com/heketi/heketi/releases/tag/v9.0.0 From container-build-reports at centos.org Sun Apr 7 06:45:17 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 07 Apr 2019 06:45:17 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5ca99c7d.I1ogLqzwBbGP1Evn%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Sun Apr 7 06:48:33 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 07 Apr 2019 06:48:33 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5ca99d41.0CQbjC89SQnq5xVa%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From ndevos at redhat.com Mon Apr 8 11:37:49 2019 From: ndevos at redhat.com (Niels de Vos) Date: Mon, 8 Apr 2019 13:37:49 +0200 Subject: [heketi-devel] Heketi v9.0.0 available for download In-Reply-To: <2297373.DkY5oybNEL@abydos> References: <2297373.DkY5oybNEL@abydos> Message-ID: <20190408113749.GB597@ndevos-x270> On Fri, Apr 05, 2019 at 03:30:29PM -0400, John Mulligan wrote: > Heketi v9.0.0 is now available [1]. > > This is the new stable version of Heketi. > > Major additions in this release: > * Limit volumes per Gluster cluster > * Prevent server from starting if db has unknown dbattributes > * Support a default admin mode option > * Add an option to enable strict zone checking on volume creation > * Add automatic pending operation clean-up functionality > * Configurable device formatting parameters > * Add consistency check feature and state examiner debugging tools > * The faulty and non-functional "db delete-pending-entries" command has been > removed > > This release contains numerous stability and bug fixes. A more detailed > changelog is available at the release page [1]. > > > -- John M. on behalf of the Heketi team > > > [1] https://github.com/heketi/heketi/releases/tag/v9.0.0 I've tried to build this version as an update for Fedora, but running 'make check' failed on ppc64le. Could it be that there is a race in the tests? >From https://kojipkgs.fedoraproject.org//work/tasks/7572/34047572/build.log : === RUN TestBackgroundOperationCleanerWithTracking --- FAIL: TestBackgroundOperationCleanerWithTracking (0.64s) assert.go:44: ASSERT: func (github.com/heketi/heketi/apps/glusterfs.TestBackgroundOperationCleanerWithTracking.func4) 0x111bcf1b File /builddir/build/BUILD/heketi-9.0.0/src/github.com/heketi/heketi/apps/glusterfs/operations_cleanup_test.go:952 Info: [expected len(l) == 0, got: 1] I'll run the build a 2nd time, just to check if the same failure happens again. Thanks, Niels From ndevos at redhat.com Mon Apr 8 12:07:11 2019 From: ndevos at redhat.com (Niels de Vos) Date: Mon, 8 Apr 2019 14:07:11 +0200 Subject: [heketi-devel] Heketi v9.0.0 available for download In-Reply-To: <20190408113749.GB597@ndevos-x270> References: <2297373.DkY5oybNEL@abydos> <20190408113749.GB597@ndevos-x270> Message-ID: <20190408120711.GC597@ndevos-x270> On Mon, Apr 08, 2019 at 01:37:49PM +0200, Niels de Vos wrote: > On Fri, Apr 05, 2019 at 03:30:29PM -0400, John Mulligan wrote: > > Heketi v9.0.0 is now available [1]. > > > > This is the new stable version of Heketi. > > > > Major additions in this release: > > * Limit volumes per Gluster cluster > > * Prevent server from starting if db has unknown dbattributes > > * Support a default admin mode option > > * Add an option to enable strict zone checking on volume creation > > * Add automatic pending operation clean-up functionality > > * Configurable device formatting parameters > > * Add consistency check feature and state examiner debugging tools > > * The faulty and non-functional "db delete-pending-entries" command has been > > removed > > > > This release contains numerous stability and bug fixes. A more detailed > > changelog is available at the release page [1]. > > > > > > -- John M. on behalf of the Heketi team > > > > > > [1] https://github.com/heketi/heketi/releases/tag/v9.0.0 > > I've tried to build this version as an update for Fedora, but running > 'make check' failed on ppc64le. Could it be that there is a race in the > tests? > > From https://kojipkgs.fedoraproject.org//work/tasks/7572/34047572/build.log : > > === RUN TestBackgroundOperationCleanerWithTracking > --- FAIL: TestBackgroundOperationCleanerWithTracking (0.64s) > assert.go:44: > > ASSERT: func (github.com/heketi/heketi/apps/glusterfs.TestBackgroundOperationCleanerWithTracking.func4) 0x111bcf1b > > File /builddir/build/BUILD/heketi-9.0.0/src/github.com/heketi/heketi/apps/glusterfs/operations_cleanup_test.go:952 > > Info: [expected len(l) == 0, got: 1] > > I'll run the build a 2nd time, just to check if the same failure happens > again. The 2nd time it worked fine for all arches, except armv7hl this time. Same failed test case. Niels From container-build-reports at centos.org Wed Apr 10 14:50:57 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 10 Apr 2019 14:50:57 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5cae02d1.PqgqzjOFPD7QvIn0%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 65f6a225fbba5e931a0a69586002d40e3d8c909a to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Wed Apr 10 14:53:39 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 10 Apr 2019 14:53:39 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5cae0373.dpw/b/RwZtqB74cO%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From johannes.grumboeck at porscheinformatik.at Thu Apr 11 06:57:02 2019 From: johannes.grumboeck at porscheinformatik.at (Grumboeck Johannes (POI - AT/Salzburg)) Date: Thu, 11 Apr 2019 06:57:02 +0000 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: 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? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From phlogistonjohn at asynchrono.us Thu Apr 11 12:51:39 2019 From: phlogistonjohn at asynchrono.us (John Mulligan) Date: Thu, 11 Apr 2019 08:51:39 -0400 Subject: [heketi-devel] Heketi v9.0.0 available for download In-Reply-To: <20190408120711.GC597@ndevos-x270> References: <2297373.DkY5oybNEL@abydos> <20190408113749.GB597@ndevos-x270> <20190408120711.GC597@ndevos-x270> Message-ID: <1636287.aAlJL8mxM1@abydos> On Monday, April 8, 2019 8:07:11 AM EDT Niels de Vos wrote: > On Mon, Apr 08, 2019 at 01:37:49PM +0200, Niels de Vos wrote: > > On Fri, Apr 05, 2019 at 03:30:29PM -0400, John Mulligan wrote: > > > Heketi v9.0.0 is now available [1]. > > > > > > This is the new stable version of Heketi. > > > > > > Major additions in this release: > > > * Limit volumes per Gluster cluster > > > * Prevent server from starting if db has unknown dbattributes > > > * Support a default admin mode option > > > * Add an option to enable strict zone checking on volume creation > > > * Add automatic pending operation clean-up functionality > > > * Configurable device formatting parameters > > > * Add consistency check feature and state examiner debugging tools > > > * The faulty and non-functional "db delete-pending-entries" command has > > > been removed > > > > > > This release contains numerous stability and bug fixes. A more detailed > > > changelog is available at the release page [1]. > > > > > > > > > -- John M. on behalf of the Heketi team > > > > > > > > > [1] https://github.com/heketi/heketi/releases/tag/v9.0.0 > > > > I've tried to build this version as an update for Fedora, but running > > 'make check' failed on ppc64le. Could it be that there is a race in the > > tests? > > > > From https://kojipkgs.fedoraproject.org//work/tasks/7572/34047572/ build.log : > > === RUN TestBackgroundOperationCleanerWithTracking > > --- FAIL: TestBackgroundOperationCleanerWithTracking (0.64s) > > > > assert.go:44: > > ASSERT: func > > (github.com/heketi/heketi/apps/glusterfs.TestBackgroundOperationClean > > erWithTracking.func4) 0x111bcf1b> > > File > > /builddir/build/BUILD/heketi-9.0.0/src/github.com/heketi/heketi/apps > > /glusterfs/operations_cleanup_test.go:952 > > > > Info: [expected len(l) == 0, got: 1] > > > > I'll run the build a 2nd time, just to check if the same failure happens > > again. > > The 2nd time it worked fine for all arches, except armv7hl this time. > Same failed test case. > > Niels Yes, I think the test is flaky as similar to the one reported here: https:// github.com/heketi/heketi/issues/1468 It succeeds enough that our CI doesn't fail on it often so, unfortunately, no one has spent much time improving it yet. Feel free to disable these tests as needed to get past that step in the build. From johannes.grumboeck at porscheinformatik.at Wed Apr 10 22:51:40 2019 From: johannes.grumboeck at porscheinformatik.at (Grumboeck Johannes (POI - AT/Salzburg)) Date: Wed, 10 Apr 2019 22:51:40 +0000 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid Message-ID: 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? 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rtalur at redhat.com Fri Apr 12 12:38:23 2019 From: rtalur at redhat.com (Raghavendra Talur) Date: Fri, 12 Apr 2019 08:38:23 -0400 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: 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: From container-build-reports at centos.org Fri Apr 12 14:20:50 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 12 Apr 2019 14:20:50 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5cb09ec2.3M2ZZjib6xN5PRJ9%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Fri Apr 12 14:23:37 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 12 Apr 2019 14:23:37 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5cb09f69.MQ5eBFNU813NHwuJ%container-build-reports@centos.org> Build Status: Failure Cause of build: Update to build configurations of the container image -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From rtalur at redhat.com Fri Apr 12 22:19:40 2019 From: rtalur at redhat.com (Raghavendra Talur) Date: Fri, 12 Apr 2019 18:19:40 -0400 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: On Fri, Apr 12, 2019 at 9:52 AM Grumboeck Johannes (POI - AT/Salzburg) wrote: > > Hi, > > > > Thanks for your answer. I?ve got one more question. > > > > > > 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. > > Does this mean that when I could change clusterid and nodeids in a heketi-topology file, > > reload it into heketi db and, as long as all references are fine within the topology file, all volumes and bricks should be safe? Yes replacing the ids is fine. > > > > I?m asking because I?m thinking about writing a script to generate a heketi-topology out of a gluster with all volumes/bricks in a safe state > > to recreate a corrupted heketi.db file. A word of warning, it is not trivial but it is doable. I suggest that you build a heketi db representation in json like the "heketi-cli db export" gives instead of building the topology file representation. If you have the json then creating a db out of it is easy using "heketi-cli db import" command. One added work would be to generate UUID for all the resources. Let me know what you think. We had plans to doing a similar feature but never prioritized. Thanks, Talur > > > > Greetings, > > Johannes > > > > Internal From johannes.grumboeck at porscheinformatik.at Fri Apr 12 13:52:13 2019 From: johannes.grumboeck at porscheinformatik.at (Grumboeck Johannes (POI - AT/Salzburg)) Date: Fri, 12 Apr 2019 13:52:13 +0000 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: Hi, Thanks for your answer. I've got one more question. > > 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. Does this mean that when I could change clusterid and nodeids in a heketi-topology file, reload it into heketi db and, as long as all references are fine within the topology file, all volumes and bricks should be safe? I'm asking because I'm thinking about writing a script to generate a heketi-topology out of a gluster with all volumes/bricks in a safe state to recreate a corrupted heketi.db file. Greetings, Johannes Internal -------------- next part -------------- An HTML attachment was scrubbed... URL: From container-build-reports at centos.org Sun Apr 14 06:45:36 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 14 Apr 2019 06:45:36 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5cb2d710.lqk6e7Tc7Hn866Jh%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Sun Apr 14 06:48:22 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 14 Apr 2019 06:48:22 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5cb2d7b6.sMtNTIVW+96Tkt2c%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From johannes.grumboeck at porscheinformatik.at Mon Apr 15 11:17:30 2019 From: johannes.grumboeck at porscheinformatik.at (Grumboeck Johannes (POI - AT/Salzburg)) Date: Mon, 15 Apr 2019 11:17:30 +0000 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: Hi Talur, > > I?m asking because I?m thinking about writing a script to generate a heketi-topology out of a gluster with all volumes/bricks in a safe state > > to recreate a corrupted heketi.db file. > > A word of warning, it is not trivial but it is doable. I suggest that > you build a heketi db representation in json like the > "heketi-cli db export" gives instead of building the topology file > representation. > > If you have the json then creating a db out of it is easy using > "heketi-cli db import" command. One added work would be to generate > UUID for all the resources. Do you mean the import process will generate the UUID or that I need to generate them before. I expected the later. > > Let me know what you think. We had plans to doing a similar feature > but never prioritized. Yes, this is my plan (maybe I mixed up topology and export-db-json). Creation of a json-file to do a db import afterwards. But you mean "heketi db import" and not "heketi-cli db import", right? I don't find an import option in heketi-cli, only a db dump option. But in the first run I would assume some things "as given", for example: - I would not consider block volumes (since I don't use them so far) - replica=3 and redundancy=2 (since I'm using Openshift Container Storage and that's the default there) - snapshot enable=false, I haven't used snapshots so far. (For sure there are some things I didn't think of yet.) Greetings, Johannes Internal From container-build-reports at centos.org Tue Apr 16 20:00:37 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 16 Apr 2019 20:00:37 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5cb63465.0RVR5ps9t/BCcDih%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 48fca17da73bb49e8707a3b8e9e4a3817276bef8 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 16 20:03:55 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 16 Apr 2019 20:03:55 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5cb6352b.aK2NMjggV9gKhJ/V%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 48fca17da73bb49e8707a3b8e9e4a3817276bef8 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From rtalur at redhat.com Tue Apr 16 20:10:05 2019 From: rtalur at redhat.com (Raghavendra Talur) Date: Tue, 16 Apr 2019 16:10:05 -0400 Subject: [heketi-devel] Question regarding heketi topology and clusterid/nodeid In-Reply-To: References: Message-ID: On Mon, Apr 15, 2019 at 7:17 AM Grumboeck Johannes (POI - AT/Salzburg) wrote: > > Hi Talur, > > > > I?m asking because I?m thinking about writing a script to generate a heketi-topology out of a gluster with all volumes/bricks in a safe state > > > to recreate a corrupted heketi.db file. > > > > A word of warning, it is not trivial but it is doable. I suggest that > > you build a heketi db representation in json like the > > "heketi-cli db export" gives instead of building the topology file > > representation. > > > > If you have the json then creating a db out of it is easy using > > "heketi-cli db import" command. One added work would be to generate > > UUID for all the resources. > Do you mean the import process will generate the UUID or that I need to generate them before. > I expected the later. You will have to generate them. > > > > > > Let me know what you think. We had plans to doing a similar feature > > but never prioritized. > > Yes, this is my plan (maybe I mixed up topology and export-db-json). > Creation of a json-file to do a db import afterwards. > But you mean "heketi db import" and not "heketi-cli db import", right? > I don't find an import option in heketi-cli, only a db dump option. Yes, right again. heketi db import, not heketi-cli. > > But in the first run I would assume some things "as given", > for example: > - I would not consider block volumes (since I don't use them so far) > - replica=3 and redundancy=2 (since I'm using Openshift Container Storage and that's the default there) > - snapshot enable=false, I haven't used snapshots so far. > (For sure there are some things I didn't think of yet.) Makes sense. > > Greetings, > Johannes > > Internal From sudheer.singh at stonybrook.edu Wed Apr 17 19:19:15 2019 From: sudheer.singh at stonybrook.edu (Sudheer Singh) Date: Wed, 17 Apr 2019 12:19:15 -0700 Subject: [heketi-devel] Why Boltdb ? Message-ID: Hi, I have been exploring glusterfs for a while now. I wanted to understand what lead to choosing BoltDb? Can we disable BoltDb? can you please provide some doc where I can get more information?. Thanks, Sudheer -------------- next part -------------- An HTML attachment was scrubbed... URL: From rtalur at redhat.com Wed Apr 17 20:28:09 2019 From: rtalur at redhat.com (Raghavendra Talur) Date: Wed, 17 Apr 2019 16:28:09 -0400 Subject: [heketi-devel] Why Boltdb ? In-Reply-To: References: Message-ID: On Wed, Apr 17, 2019 at 3:20 PM Sudheer Singh wrote: > > Hi, > I have been exploring glusterfs for a while now. I wanted to understand what lead to choosing BoltDb? Can we disable BoltDb? can you please provide some doc where I can get more information?. Gluster itself does not use boltdb and does not require heketi. If you choose to use heketi to administer your Gluster Cluster(s), then you also end up using BoltDB. Why did the original author choose BoltDB? I don't know all the reasons, but the slide[1] should tell the features that lead to the choice. Can we disable BoltDB? No, as of today, heketi relies on BoltDB to store the information about Gluster/Devices/Nodes. It is possible to refactor the code to store the information in any other key value store but we have not found any reason to. [1] https://talks.godoc.org/github.com/lpabon/go-slides/2016/fosdem-writing-go-rest.slide#36 > > Thanks, > Sudheer > > _______________________________________________ > heketi-devel mailing list > heketi-devel at gluster.org > https://lists.gluster.org/mailman/listinfo/heketi-devel From container-build-reports at centos.org Sun Apr 21 06:52:35 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 21 Apr 2019 06:52:35 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5cbc1333.xibu0niJzYA/mv4Y%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Sun Apr 21 06:55:37 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 21 Apr 2019 06:55:37 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5cbc13e9.MlRY3s3ODeYCqRki%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 23 20:30:51 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 23 Apr 2019 20:30:51 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5cbf75fb.fIH9RFUTFV+43DEO%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit fc06280b9f8b3e5bf629a4f5492669bc67a9b6c3 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Tue Apr 23 20:35:19 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 23 Apr 2019 20:35:19 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5cbf7707.AQvZX7kjkVTQNKcH%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit fc06280b9f8b3e5bf629a4f5492669bc67a9b6c3 to branch origin/master of repo https://github.com/heketi/heketi. -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Sun Apr 28 06:52:31 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 28 Apr 2019 06:52:31 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5cc54daf.nexi3lRi9G42r3fH%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline From container-build-reports at centos.org Sun Apr 28 06:53:26 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 28 Apr 2019 06:53:26 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5cc54de6.0j4LVvF4KYWqgHDV%container-build-reports@centos.org> Scan status: Success Repository: https://registry.centos.org/gluster/storagesig-heketi -- Do you have a query? Talk to CentOS Container Pipeline team on #centos-devel at freenode https://wiki.centos.org/ContainerPipeline