From container-build-reports at centos.org Sun Sep 1 06:52:45 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 01 Sep 2019 06:52:45 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5d6b6abd.9aOaG7kJUeHYQheV%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 Sep 1 06:55:39 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 01 Sep 2019 06:55:39 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5d6b6b6b.EN0CwaxGpjfkFyxm%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 Wed Sep 4 18:34:12 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 04 Sep 2019 18:34:12 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d7003a4.SCFUujDyYIBxcwka%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit e3797dcb6c7b63cb05638af34d52285aa30ed34d 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 Sep 4 18:40:32 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Wed, 04 Sep 2019 18:40:32 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5d700520.ieZl975huXlj+ts9%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit e3797dcb6c7b63cb05638af34d52285aa30ed34d 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 Sep 6 19:51:22 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 06 Sep 2019 19:51:22 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:testing Message-ID: <5d72b8ba.3f0d73fdegH1DzqZ%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 5883e726fce2d3379421c9969d4e75795381fbdd 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 Sep 6 19:55:13 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Fri, 06 Sep 2019 19:55:13 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d72b9a1.9j4Tmgzk3B52Eeul%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 5883e726fce2d3379421c9969d4e75795381fbdd 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 Sep 8 06:52:53 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 08 Sep 2019 06:52:53 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5d74a545.rZti0Kl/JQ0p3FK+%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 Sep 8 06:56:35 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 08 Sep 2019 06:56:35 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5d74a623./7qNPCEPRAiRjDEO%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 Sep 15 06:54:44 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 15 Sep 2019 06:54:44 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:latest Message-ID: <5d7de034.z5Go2lGZ3OZHmDnK%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 Sep 15 06:55:48 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Sun, 15 Sep 2019 06:55:48 +0000 Subject: [heketi-devel] [registry.centos.org] SUCCESS: Weekly scan for gluster/storagesig-heketi:testing Message-ID: <5d7de074.V55yOMWR2PAhbX16%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 Mon Sep 16 11:32:15 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 16 Sep 2019 11:32:15 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d7f72bf.CfP7R5MVhI0gmEz2%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 5883e726fce2d3379421c9969d4e75795381fbdd 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 Sep 16 14:03:26 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 16 Sep 2019 14:03:26 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d7f962e.XwJ/U3l9CEMsZTm6%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 5883e726fce2d3379421c9969d4e75795381fbdd 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 shambho100 at gmail.com Mon Sep 16 21:25:34 2019 From: shambho100 at gmail.com (Shambho) Date: Mon, 16 Sep 2019 17:25:34 -0400 Subject: [heketi-devel] how does arbiter: required work? Message-ID: Hello Group I setup a Glusterfs clustr with two nodes and configured heketi and settags on one of these nodes as arbiter:required. But creating a volume with --durability=none always creates the volume on the node with arbiter:required tag. Is this the expected behavior? I was under the impression that this tag will ensure only arbiter volumes will be created on this node. What I am trying to achieve is be able to use a node with smaller disk as an arbiter node. Thanks Shambho -------------- next part -------------- An HTML attachment was scrubbed... URL: From container-build-reports at centos.org Mon Sep 16 21:33:59 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Mon, 16 Sep 2019 21:33:59 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d7fffc7.ZQYzBBDCWOdTKPEa%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 Tue Sep 17 04:45:50 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 17 Sep 2019 04:45:50 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d8064fe.nPUPOkoaHghEP6nm%container-build-reports@centos.org> Build Status: Failure Cause of build: Git commit 5062b163a9e4e579e1153b54dc78cf22304eef52 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 shambho100 at gmail.com Tue Sep 17 12:44:14 2019 From: shambho100 at gmail.com (Shambho) Date: Tue, 17 Sep 2019 08:44:14 -0400 Subject: [heketi-devel] how does arbiter: required work? In-Reply-To: References: Message-ID: Please ignore my previous email. On Mon, Sep 16, 2019 at 5:25 PM Shambho wrote: > Hello Group > > I setup a Glusterfs clustr with two nodes and configured heketi and > settags on one of these nodes as arbiter:required. But creating a volume > with --durability=none always creates the volume on the node with > arbiter:required tag. Is this the expected behavior? I was under the > impression that this tag will ensure only arbiter volumes will be created > on this node. > > What I am trying to achieve is be able to use a node with smaller disk as > an arbiter node. > > Thanks > Shambho > -------------- next part -------------- An HTML attachment was scrubbed... URL: From container-build-reports at centos.org Tue Sep 17 15:43:41 2019 From: container-build-reports at centos.org (container-build-reports at centos.org) Date: Tue, 17 Sep 2019 15:43:41 +0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest Message-ID: <5d80ff2d.gqE76q8j6l+aFMBf%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 johnm at asynchrono.us Sun Sep 8 15:23:52 2019 From: johnm at asynchrono.us (John Mulligan) Date: Sun, 08 Sep 2019 15:23:52 -0000 Subject: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest In-Reply-To: <5d72b9a1.9j4Tmgzk3B52Eeul%container-build-reports@centos.org> References: <5d72b9a1.9j4Tmgzk3B52Eeul%container-build-reports@centos.org> Message-ID: <24531978.q7U7Xjo2SB@abydos> Can whoever has control of these stop sending these messages to the heketi- devel list? I am a maintainer of the project but I have zero insight into what makes these builds pass or fail and the messages themselves provide nearly zero information. I am sure there was good intention here when it was set up but it seems just like noise to me now. Plus, the heketi project itself takes no responsibility for the quality of these builds. On Friday, September 6, 2019 3:55:13 PM EDT container-build-reports at centos.org wrote: > Build Status: Failure > Cause of build: Git commit > 5883e726fce2d3379421c9969d4e75795381fbdd 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 > > _______________________________________________ > heketi-devel mailing list > heketi-devel at gluster.org > https://lists.gluster.org/mailman/listinfo/heketi-devel From amgad.saleh at nokia.com Mon Sep 9 03:00:18 2019 From: amgad.saleh at nokia.com (Saleh, Amgad (Nokia - US/Naperville)) Date: Mon, 09 Sep 2019 03:00:18 -0000 Subject: [heketi-devel] Expand volume's number bricks with arbiter option Message-ID: I can expand a volume from 2 replicas to 3 bricks (with anrbiter) using the gluster CLI. I don't know of a way to do it with heketi (using K8S storage classes) Is there such a way? if not this is a very needed viable option to add to be compatible with Gluster CLI. -------------- next part -------------- An HTML attachment was scrubbed... URL: