[heketi-devel] Update the Heketi package for the CentOS Storage SIG?

2017-02-17 Thread Niels de Vos 
Hi,

currently heketi-1.0.2-1.el7 is the version that is available in the
CentOS Storage SIG (for CentOS 7). I am currently preparing for the
GlusterFS 3.10 release in the Storage SIG, and would like to know if I
should update the Heketi package there as well.

Thanks,
Niels


signature.asc
Description: PGP signature
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

[heketi-devel] Heketi is being added to the Gluster repositories from the CentOS Storage SIG

2017-08-10 Thread Niels de Vos 
Hi,

I've added golang-1.8.3-1.2.1.el7 to the buildroot for the Gluster
repositories in the CentOS Storage SIG. This makes it possible to build
recent versions of Heketi for CentOS 7 (x86_64, aarch64, ppc64le). It
does not look like CentOS 6 has access to golang packages. So I'm not
planning to build Heketi for CentOS 6.

My plan is to put heketi-4.0.0 in the gluster-3.12 repository, but if
you expect users of gluster-3.10 to need heketi, I can add it there as
well. Just let me know in that case.

The current dist-git-like repository can be found here:
  https://github.com/CentOS-Storage-SIG/heketi/tree/sig-storage7-gluster-common

sig-storage7-gluster-common is the branch that is used for building
packages that do not rely on a specific glusterfs version. Pull requests
for this repository are welcome. I can do new builds when after patches
get merged.

https://cbs.centos.org/koji/taskinfo?taskID=208243 has just finished
while I'm writing this email. Some tests of the RPMs are appreciated.
The gluster-3.12 repository is not yet available, so you will need to
download the packages manually.

Cheers,
Niels
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] [Gluster-devel] Heketi version 5 has been released!

2017-09-20 Thread Niels de Vos 
On Fri, Sep 15, 2017 at 11:08:55AM +0200, Niels de Vos wrote:
> On Thu, Sep 14, 2017 at 11:32:02PM +0200, Michael Adam wrote:
> > Hi all,
> > 
> > 
> > Heketi version 5 has just been released.
> 
> Congrats with the new release!
> 
> > Here is the high-level changelog since version 4:
> > 
> > - Set Gluster Volume options based on user input.
> > - Allow disperse volumes to be 2+1.
> > - Use glide instead of godeps for build dependencies.
> > - Increase test coverage.
> > - Compress database when storing in a K8S Secret.
> > - Introduce switch `backup_db_to_kube_secret`, defaulting to false.
> > - Add functionality to remove a device.
> > - Add functionality to remove a node.
> > - Environmental variable support for config of sshexec.
> > 
> > Downloads of source code and binaries:
> > 
> > https://github.com/heketi/heketi/releases/tag/v5.0.0
> 
> Could someone send a pull request to update the packaging for the CentOS
> Storage SIG? I'm not very familiar with Golang yet, and the change from
> godeps to glide is not something I can do in a couple of minutes.
> 
> Contents of the 'dist-git like' packaging files can be found here:
>   
> https://github.com/CentOS-Storage-SIG/heketi/tree/sig-storage7-gluster-common

Thanks for the pull request!

heketi-5.0.0-1.el7 will become available in the testing repository
within the next few hours. Once it is there, you can install a standard
CentOS-7 system and get the packages with:

  # yum install centos-release-gluster
  # yum --enablerepo=centos-gluster*-test install heketi

Please give it a whirl and let me know when the package is ready for
promoting to the public mirrors.

Niels


signature.asc
Description: PGP signature
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] [Gluster-devel] Heketi version 5 has been released!

2017-09-18 Thread Niels de Vos 
On Thu, Sep 14, 2017 at 11:32:02PM +0200, Michael Adam wrote:
> Hi all,
> 
> 
> Heketi version 5 has just been released.

Congrats with the new release!

> Here is the high-level changelog since version 4:
> 
> - Set Gluster Volume options based on user input.
> - Allow disperse volumes to be 2+1.
> - Use glide instead of godeps for build dependencies.
> - Increase test coverage.
> - Compress database when storing in a K8S Secret.
> - Introduce switch `backup_db_to_kube_secret`, defaulting to false.
> - Add functionality to remove a device.
> - Add functionality to remove a node.
> - Environmental variable support for config of sshexec.
> 
> Downloads of source code and binaries:
> 
> https://github.com/heketi/heketi/releases/tag/v5.0.0

Could someone send a pull request to update the packaging for the CentOS
Storage SIG? I'm not very familiar with Golang yet, and the change from
godeps to glide is not something I can do in a couple of minutes.

Contents of the 'dist-git like' packaging files can be found here:
  https://github.com/CentOS-Storage-SIG/heketi/tree/sig-storage7-gluster-common

Thanks!
Niels


> Docker image:
> 
> docker pull heketi/heketi
> 
> or
> 
> docker pull heketi/heketi:5
> docker pull heketi/heketi:latest
> 
> 
> - Michael (for the heketi team)



> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

[heketi-devel] Fwd: FOSDEM Call for Participation: Software Defined Storage devroom

2017-10-18 Thread Niels de Vos 
- Forwarded message from Jan Fajerski  -

> Date: Thu, 12 Oct 2017 12:55:28 +0200
> From: Jan Fajerski 
> To: ceph-de...@vger.kernel.org, ceph-us...@ceph.com, gluster-us...@gluster.org
> Cc: devroom-manag...@lists.fosdem.org, fos...@lists.fosdem.org
> Subject: [Gluster-users] FOSDEM Call for Participation: Software Defined 
> Storage devroom
> 
> 
> CfP for the Software Defined Storage devroom at FOSDEM 2018
> (Brussels, Belgium, February 4th).
> 
> FOSDEM is a free software event that offers open source communities a place to
> meet, share ideas and collaborate.  It is renown for being highly developer-
> oriented and brings together 8000+ participants from all over the world.  It
> is held in the city of Brussels (Belgium).
> 
> FOSDEM 2018 will take place during the weekend of February 3rd-4th 2018. More
> details about the event can be found at http://fosdem.org/
> 
> ** Call For Participation
> 
> The Software Defined Storage devroom will go into it's second round for
> talks around Open Source Software Defined Storage projects, management tools
> and real world deployments.
> 
> Presentation topics could include but are not limited too:
> 
> - Your work on a SDS project like Ceph, GlusterFS or LizardFS
> 
> - Your work on or with SDS related projects like SWIFT or Container Storage
> Interface
> 
> - Management tools for SDS deployments
> 
> - Monitoring tools for SDS clusters
> 
> ** Important dates:
> 
> - 26 Nov 2017:  submission deadline for talk proposals
> - 15 Dec 2017:  announcement of the final schedule
> -  4 Feb 2018:  Software Defined Storage dev room
> 
> Talk proposals will be reviewed by a steering committee:
> - Leonardo Vaz (Ceph Community Manager - Red Hat Inc.)
> - Joao Luis (Core Ceph contributor - SUSE)
> - Jan Fajerski (Ceph Developer - SUSE)
> 
> Use the FOSDEM 'pentabarf' tool to submit your proposal:
> https://penta.fosdem.org/submission/FOSDEM18
> 
> - If necessary, create a Pentabarf account and activate it.
> Please reuse your account from previous years if you have
> already created it.
> 
> - In the "Person" section, provide First name, Last name
> (in the "General" tab), Email (in the "Contact" tab)
> and Bio ("Abstract" field in the "Description" tab).
> 
> - Submit a proposal by clicking on "Create event".
> 
> - Important! Select the "Software Defined Storage devroom" track
> (on the "General" tab).
> 
> - Provide the title of your talk ("Event title" in the "General" tab).
> 
> - Provide a description of the subject of the talk and the
> intended audience (in the "Abstract" field of the "Description" tab)
> 
> - Provide a rough outline of the talk or goals of the session (a short
> list of bullet points covering topics that will be discussed) in the
> "Full description" field in the "Description" tab
> 
> - Provide an expected length of your talk in the "Duration" field. Please
> count at least 10 minutes of discussion into your proposal.
> 
> Suggested talk length would be 15, 20+10, 30+15, and 45+15 minutes.
> 
> ** Recording of talks
> 
> The FOSDEM organizers plan to have live streaming and recording fully working,
> both for remote/later viewing of talks, and so that people can watch streams
> in the hallways when rooms are full. This requires speakers to consent to
> being recorded and streamed. If you plan to be a speaker, please understand
> that by doing so you implicitly give consent for your talk to be recorded and
> streamed. The recordings will be published under the same license as all
> FOSDEM content (CC-BY).
> 
> Hope to hear from you soon! And please forward this announcement.
> ___
> Gluster-users mailing list
> gluster-us...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users

- End forwarded message -
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] Fwd: FOSDEM Call for Participation: Software Defined Storage devroom

2017-11-22 Thread Niels de Vos 
Reminder! The Call for Participation ends later this week. There is
still time to propose talks.


On Wed, Oct 18, 2017 at 12:41:35PM +0200, Niels de Vos wrote:
> - Forwarded message from Jan Fajerski <jfajer...@suse.com> -
> 
> > Date: Thu, 12 Oct 2017 12:55:28 +0200
> > From: Jan Fajerski <jfajer...@suse.com>
> > To: ceph-de...@vger.kernel.org, ceph-us...@ceph.com, 
> > gluster-us...@gluster.org
> > Cc: devroom-manag...@lists.fosdem.org, fos...@lists.fosdem.org
> > Subject: [Gluster-users] FOSDEM Call for Participation: Software Defined 
> > Storage devroom
> > 
> > 
> > CfP for the Software Defined Storage devroom at FOSDEM 2018
> > (Brussels, Belgium, February 4th).
> > 
> > FOSDEM is a free software event that offers open source communities a place 
> > to
> > meet, share ideas and collaborate.  It is renown for being highly developer-
> > oriented and brings together 8000+ participants from all over the world.  It
> > is held in the city of Brussels (Belgium).
> > 
> > FOSDEM 2018 will take place during the weekend of February 3rd-4th 2018. 
> > More
> > details about the event can be found at http://fosdem.org/
> > 
> > ** Call For Participation
> > 
> > The Software Defined Storage devroom will go into it's second round for
> > talks around Open Source Software Defined Storage projects, management tools
> > and real world deployments.
> > 
> > Presentation topics could include but are not limited too:
> > 
> > - Your work on a SDS project like Ceph, GlusterFS or LizardFS
> > 
> > - Your work on or with SDS related projects like SWIFT or Container Storage
> > Interface
> > 
> > - Management tools for SDS deployments
> > 
> > - Monitoring tools for SDS clusters
> > 
> > ** Important dates:
> > 
> > - 26 Nov 2017:  submission deadline for talk proposals
> > - 15 Dec 2017:  announcement of the final schedule
> > -  4 Feb 2018:  Software Defined Storage dev room
> > 
> > Talk proposals will be reviewed by a steering committee:
> > - Leonardo Vaz (Ceph Community Manager - Red Hat Inc.)
> > - Joao Luis (Core Ceph contributor - SUSE)
> > - Jan Fajerski (Ceph Developer - SUSE)
> > 
> > Use the FOSDEM 'pentabarf' tool to submit your proposal:
> > https://penta.fosdem.org/submission/FOSDEM18
> > 
> > - If necessary, create a Pentabarf account and activate it.
> > Please reuse your account from previous years if you have
> > already created it.
> > 
> > - In the "Person" section, provide First name, Last name
> > (in the "General" tab), Email (in the "Contact" tab)
> > and Bio ("Abstract" field in the "Description" tab).
> > 
> > - Submit a proposal by clicking on "Create event".
> > 
> > - Important! Select the "Software Defined Storage devroom" track
> > (on the "General" tab).
> > 
> > - Provide the title of your talk ("Event title" in the "General" tab).
> > 
> > - Provide a description of the subject of the talk and the
> > intended audience (in the "Abstract" field of the "Description" tab)
> > 
> > - Provide a rough outline of the talk or goals of the session (a short
> > list of bullet points covering topics that will be discussed) in the
> > "Full description" field in the "Description" tab
> > 
> > - Provide an expected length of your talk in the "Duration" field. Please
> > count at least 10 minutes of discussion into your proposal.
> > 
> > Suggested talk length would be 15, 20+10, 30+15, and 45+15 minutes.
> > 
> > ** Recording of talks
> > 
> > The FOSDEM organizers plan to have live streaming and recording fully 
> > working,
> > both for remote/later viewing of talks, and so that people can watch streams
> > in the hallways when rooms are full. This requires speakers to consent to
> > being recorded and streamed. If you plan to be a speaker, please understand
> > that by doing so you implicitly give consent for your talk to be recorded 
> > and
> > streamed. The recordings will be published under the same license as all
> > FOSDEM content (CC-BY).
> > 
> > Hope to hear from you soon! And please forward this announcement.
> > ___
> > Gluster-users mailing list
> > gluster-us...@gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-users
> 
> - End forwarded message -
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] Heketi v5.0.1 security release available for download

2017-12-19 Thread Niels de Vos 
On Mon, Dec 18, 2017 at 06:10:29PM +0100, Michael Adam wrote:
> 
> Heketi v5.0.1 is now available.

Packages for the CentOS Storage SIG are now becomnig available in the
testing repository. Packages can be obtained (soon) with the following
steps:

  # yum --enablerepo=centos-gluster*-test update heketi

The update will show up for systems that have the repository files from
the centos-release-gluster{310,312,313} packages. Other repositories
will not receive any updates anymore.

I'd appreciate it if someone could do basic testing of the update. When
some feedback is provided, the package can be marked for release to the
CentOS mirrors.

Niels


> This release[1] fixes a flaw that was found in heketi API that
> permits issuing of OS commands through specially crafted
> requests, possibly leading to escalation of privileges. More
> details can be obtained at CVE-2017-15103. [2]
> 
> If authentication is turned "on" in heketi configuration, the
> flaw can be exploited only by those who possess authentication
> key. In case you have a deployment without authentication set to
> true, we recommend that you turn it on and also upgrade to
> version with fix.
> 
> 
> We thank Markus Krell of NTT Security for identifying
> the vulnerability and notifying us about the it.
> 
> The fix was provided by Raghavendra Talur of Red Hat.
> 
> 
> Note that previous versions of Heketi are discontinued
> and users are strongly recommended to upgrade to Heketi 5.0.1.
> 
> 
> Michael Adam on behalf of the Heketi team
> 
> 
> [1] https://github.com/heketi/heketi/releases/tag/v5.0.1
> [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15103



> ___
> heketi-devel mailing list
> heketi-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/heketi-devel

___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

[heketi-devel] Proposal to provide Heketi containers in the CentOS Container Registry

2018-06-04 Thread Niels de Vos 
I'd like to get container images built with the CentOS Storage SIG
components in the CentOS Container Registry[0]. With this, I hope to be
able to provide a solid user experience, and a more stable build process
(the images on dockerhub still fail building[1]?).

For this, I've sent a PR[2] with new Dockerfiles, one for a
stable/released version (still heketi 4.0), and one for the packages in
testing (heketi 6.0).

I would like to see these containers used by any examples/demos that
target OpenShift (as that is mostly CentOS/RHEL already). At least I
will try to do so :-)

Feedback, reviews and suggestions are most welcome, thanks!
Niels


0. https://registry.centos.org/containers/
1. https://hub.docker.com/r/heketi/heketi/builds/
2. https://github.com/heketi/heketi/pull/1202
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] [RFC] Initial proposal for snapshot/cloning support

2018-02-14 Thread Niels de Vos 
Hi again!

The majority of the emails still stands, but the document has been
updated a little with early comments. The location is still the same,
and the updated version has been included below.

Niels

On Tue, Feb 13, 2018 at 05:17:44PM +0100, Niels de Vos wrote:
> Hi,
> 
> as we would like to see cloning of PVs soonish, I'd like to share my
> suggestions for the heketi-cli and bits of the ReST API that could be
> implemented. The document lives in my fork of the Heketi project and can
> be found here (nicely formatted):
>   https://github.com/nixpanic/heketi/blob/wip/snapshot/doc/admin/snapshot.md
> 
> It may be easier to reply with inline comments (please not on GitHub),
> so I'll include the text as well.
> 
> I hope this interface allows use to support the Snapshot functionality
> that Kubernetes recently added, as well as the cloning of PVs that is
> expected to be consumed by kubevirt.
> 
> There are two suggestions for the Endpoints of the API. That is the bit
> that probably needs most consideration.
> 
> Suggestions are most welcome!
> Niels
> 
 %< 
Snapshots are read-only copies of volumes that can be used for cloning new
volumes from. Its is possible to create a snapshot through the [Snapshot Create
API](../api/api.md#create-a-snapshot) or the commandline client.

>From the command line client, you can type the following to create a snapshot
from an existing volume:

```
$ heketi-cli snapshot create -volume= [-name=]
```

The new snapshot can be used to create a new volume:

```
$ heketi-cli snapshot clone -from-snap= [-name=]
```

The clones of snapshots are new volumes with the same properties as the
original. The cloned volumes can be deleted with the `heketi-cli volume delete`
command. In a similar fashion, snapshots can be removed with the `heketi-cli
snapshot delete` command.

# Proposed CLI

The parameters for the `heketi-cli` should be easily identifiable. Every time a
`` is used, the parameter will be called `-volume=`, and the same
counts for `` and `-snapshot=`. Upon creation, the name of the new
object can be passed as `-name=`, or left out so that Heketi generates a name
based on the UUID that will be assigned to the object.

```
$ heketi-cli snapshot create -volume= [-name=] 
[-description=]
$ heketi-cli snapshot clone -snapshot= [-name=]
$ heketi-cli snapshot delete -snapshot=
$ heketi-cli snapshot list -volume=
$ heketi-cli snapshot info -snapshot=
```

# API Proposal

For file volume types only. A similar implementation might get added for
block-volumes at a later time.

### Create a Snapshot
* **Method:** _POST_
* **Endpoint**:`/volumes/{volume_uuid}/snapshots`

### Clone a Volume from a Snapshot
* **Method:** _POST_
* **Endpoint**:`/volumes/{volume_uuid}/snapshots/{snapshot_uuid}`

### Delete a Snapshot
* **Method:** _DELETE_
* **Endpoint**:`/volumes/{volume_uuid}/snapshots/{snapshot_uuid}`

### List Snapshots
* **Method:** _GET_
* **Endpoint**:`/volumes/{volume_uuid}/snapshots`

### Get Snapshot Information
* **Method:** _GET_
* **Endpoint**:`/volumes/{volume_uuid}/snapshots/{snapshot_uuid}`


# Gluster Snapshot CLI Reference
```
$ gluster --log-file=/dev/null snapshot help

gluster snapshot commands
=

snapshot activate  [force] - Activate snapshot volume.
snapshot clone   - Snapshot Clone.
snapshot config [volname] ([snap-max-hard-limit ] [snap-max-soft-limit 
]) | ([auto-delete <enable|disable>])| ([activate-on-create 
<enable|disable>]) - Snapshot Config.
snapshot create   [no-timestamp] [description ] 
[force] - Snapshot Create.
snapshot deactivate  - Deactivate snapshot volume.
snapshot delete (all | snapname | volume ) - Snapshot Delete.
snapshot help - display help for snapshot commands
snapshot info [(snapname | volume )] - Snapshot Info.
snapshot list [volname] - Snapshot List.
snapshot restore  - Snapshot Restore.
snapshot status [(snapname | volume )] - Snapshot Status.
```

- 
[Snapshot](https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.6/Gluster%20Volume%20Snapshot.md)
- 
[Cloning](https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.7/Clone%20of%20Snapshot.md)
___
heketi-devel mailing list
heketi-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/heketi-devel

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

2018-07-30 Thread Niels de Vos 
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 is that the RPM "doesn't know" this.

Ok, thanks! It seems I can change the .spec to use python3 and at least
it builds just fine (not sure what automated tests there are).

> If you really want to remove the RPM from Fedora because of lack of use I 
> suppose that might be OK, but the binding themselves will continue to exist 
> and I hope to use them more for tests in heketi's own repo.

If the intention is to use it only for testing, then I'll drop it.
Otherwise we can keep the Python bindings. What is your suggestion or
preference?

Niels


> On Sunday, July 29, 2018 2:47:54 PM EDT Niels de Vos wrote:
> > The Fedora package currently fails to build for Rawhide (Fedora 29)
> > because the python bindings under client/api/python have a requirement
> > on Python 2.
> > 
> > I do not know how much work it is to make the bindings compatible with
> > both Python 2 and 3. Before spending time on this, I would like to know
> > if there are any users of the Python bindings at all. In case nobody has
> > a use-case for the bindings, I propose we remove them from the
> > repository.
> > 
> > Thanks,
> > Niels
> 
> 
> 
> 


signature.asc
Description: PGP signature
___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel

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

2018-07-29 Thread Niels de Vos 
The Fedora package currently fails to build for Rawhide (Fedora 29)
because the python bindings under client/api/python have a requirement
on Python 2.

I do not know how much work it is to make the bindings compatible with
both Python 2 and 3. Before spending time on this, I would like to know
if there are any users of the Python bindings at all. In case nobody has
a use-case for the bindings, I propose we remove them from the
repository.

Thanks,
Niels


signature.asc
Description: PGP signature
___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] Time for a new release?

2018-08-19 Thread Niels de Vos 
On Sat, Aug 18, 2018 at 08:56:15AM -0400, John Mulligan wrote:
> I think we ought to do a version 8 release within the next week or so. A lot 
> of patches have gone in on master that improve the reliability and management 
> of Heketi and I think it would be good for users who are not running directly 
> on master to benefit from this work.
> 
> Any opinions or objections?

Yes, a new release is most welcome!

Some sort of more regular releases would be good. Maybe every 6 weeks or
2 months is a nice interval?

Niels
___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel

[heketi-devel] Dynamic provisioning does not provide the amount of 'free space' that was requested

2018-11-16 Thread Niels de Vos 
The KubeVirt team found a bug in how Heketi provisions requested volumes
(PVCs). The problem that they hit is related to how much overhead a
filesystem needs vs how much free space is expected. This comes down to
the following:

- Heketi gets asked to provision a volume of 4GB
- checking the available space once the volume is a little less
- KubeVirt will not be able to create a 4GB disk image and errors out

It seems that Heketi does not take all overhead into account while
creating bricks, and the Gluster volume. The following overhead items
are identified:

- XFS metadata after formatting the block-device (LVM/LV)
- GlusterFS metadata under .glusterfs
- space reservation with the `storage.reserve` volume option

In order to improve Heketi and fullfill the 'requested size' correctly,
we will need to estimate/calculate the overhead and only then execute
the volume creation operations. Ideas and suggestions for this are most
welcome.

https://bugzilla.redhat.com/show_bug.cgi?id=1649991 is the main bug for
this. However it is likely that gluster-block, glusterd2 and other smart
provisioners are affected with the same problem.

Niels
___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] Heketi v8.0.0 available for download

2018-09-13 Thread Niels de Vos 
On Wed, Sep 12, 2018 at 07:43:47PM -0400, John Mulligan wrote:
> Heketi v8.0.0 is now available [1].
> 
> This is the new stable version of Heketi.
> 
> Major additions in this release:
> * Resumable delete of Volumes and Block Volumes
> * Server administrative modes
> * Throttling of concurrent operations
> * Support configuration of block hosting volume options
> * Heketi cli command to fetch operation counters
> * Support setting restrictions on block hosting volume; to prevent block 
> hosting volumes from taking new block volumes
> * Add an option to destroy data while adding a device to a node
> * Heketi Container: load an initial topology if HEKETI_TOPOLOGY_FILE is set
> 
> This release contains numerous stability and bug fixes. A more detailed 
> changelog is available at the release page [1].

Packages for Fedora 29 (and 30/Rawhide), and CentOS Storage SIG have
been built and are available for testing (if not yet, then very soon).

For Fedora, please run 'dnf --enablerepo=updates-testing install heketi'
and leave feedback in 
https://bodhi.fedoraproject.org/updates/FEDORA-2018-5aa0a9dc9b
(Fedora 29 is in Beta at the moment, makes testing more difficult.)

On CentOS-7, use this (assumes centos-release-gluster{312,41} is
installed):

  # yum --enablerepo=centos-gluster*-test install heketi

Once packages for CentOS have been tested, email these lists and we'll
mark the package for release.

A container image based on CentOS should land in the CentOS Registry
soon (tomorrow?) as well. Check
https://registry.centos.org/gluster/storagesig-heketi for the latest
builds, the :testing tag will get heketi-8.0.0 with a new image build.

Thanks,
Niels


> Special thanks to Michael Adam and Raghavendra Talur for assisting me with 
> creating my first release.
> 
> -- John M. on behalf of the Heketi team
> 
> 
> [1] https://github.com/heketi/heketi/releases/tag/v8.0.0
> 
> 
> ___
> heketi-devel mailing list
> heketi-devel@gluster.org
> https://lists.gluster.org/mailman/listinfo/heketi-devel


signature.asc
Description: PGP signature
___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel

Re: [heketi-devel] [registry.centos.org] FAILED: Container build gluster/storagesig-heketi:latest

2019-10-29 Thread Niels de Vos 
On Sun, Sep 08, 2019 at 11:18:45AM -0400, John Mulligan wrote:
> 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.

The logs are difficult to get, they are internal to the CentOS Container
Pipeline and require someone that has access to those systesm to
investigate the details of the build failures (one of the CentOS
admins).

That said, the configuration about the build and reporting is at 
https://github.com/CentOS/container-index/blob/master/index.d/gluster.yaml

HTH,
Niels

> 
> 
> On Friday, September 6, 2019 3:55:13 PM EDT 
> container-build-repo...@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@gluster.org
> > https://lists.gluster.org/mailman/listinfo/heketi-devel
> 
> 
> 
> 
> ___
> heketi-devel mailing list
> heketi-devel@gluster.org
> https://lists.gluster.org/mailman/listinfo/heketi-devel

___
heketi-devel mailing list
heketi-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/heketi-devel