Re: [heketi-devel] Does anyone object to removing the python bindings for the Heketi client?

On Mon, Jul 30, 2018 at 07:12:33AM -0400, John Mulligan wrote: > Hi Niels, > > The Heketi python bindings should already be Python 3 compatible. I updated > them a while back and tried to make sure that they would be regularly tested > for both Python 2 and 3 compatibility via tox. > My guess

Re: [heketi-devel] Does anyone object to removing the python bindings for the Heketi client?

Hi Niels, The Heketi python bindings should already be Python 3 compatible. I updated them a while back and tried to make sure that they would be regularly tested for both Python 2 and 3 compatibility via tox. My guess is that the RPM "doesn't know" this. If you really want to remove the RPM

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:latest is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:latest Build logs:

[heketi-devel] Weekly scanning results for image: registry.centos.org/gluster/storagesig-heketi:latest

CentOS Community Container Pipeline Service = Atomic scanners results for built image registry.centos.org/gluster/storagesig-heketi:latest container-capabilities-scanner: Dockerfile for

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:testing is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:testing Build logs:

[heketi-devel] Weekly scanning results for image: registry.centos.org/gluster/storagesig-heketi:latest

CentOS Community Container Pipeline Service = Atomic scanners results for built image registry.centos.org/gluster/storagesig-heketi:latest container-capabilities-scanner: Dockerfile for

[heketi-devel] FAILED: Container build: gluster-storagesig-heketi-latest is failed

CentOS Community Container Pipeline Service = Container build gluster-storagesig-heketi-latest is failed due to error in build or test steps. Build status: Failure Build logs:

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:latest is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:latest Build logs:

[heketi-devel] Weekly scanning results for image: registry.centos.org/gluster/storagesig-heketi:latest

CentOS Community Container Pipeline Service = Atomic scanners results for built image registry.centos.org/gluster/storagesig-heketi:latest container-capabilities-scanner: Dockerfile for

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:testing is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:testing Build logs:

[heketi-devel] Does heketi support stripe volume type?

If heketi supports stripe volume type, tell me please！ Best regards！ Neo.W JD.COM ___ heketi-devel mailing list heketi-devel@gluster.org https://lists.gluster.org/mailman/listinfo/heketi-devel

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:testing is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:testing Build logs:

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:testing is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:testing Build logs:

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:testing is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:testing Build logs:

[heketi-devel] Disk symlink not accepted by heketi

As the device names are not persistence across reboot, I was using symlink of the disk to configure Heketi topology. In my setup, both Heketi (version 5) and GlusterFS (version 3.12.1) runs a Pods. symlink "/dev/disk/by-path/pci-:00:10.0-scsi-0:0:1:0" was working perfectly for us. However,

[heketi-devel] volume delete

Hi, please let me know if I am looking in the wrong place. I deleted a volume from gluster directly rather than from heketi, I am now unable to recreate the volume as heketi thinks its still there. Is there a way to delete the volume from the heketi DB so that I can create it again? Thank you

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:latest is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:latest Build logs:

[heketi-devel] SUCCESS: Container build: gluster/storagesig-heketi:latest is complete

CentOS Community Container Pipeline Service = Build status: Success Image: registry.centos.org/gluster/storagesig-heketi:latest Build logs: