[Gluster-devel] GCS milestone 0.3

[John Strunk]

Today, we are announcing the availability of GCS (Gluster Container
Storage) 0.3. GCS is following a release cadence of 2 weeks for all the
point releases leading up to 1.0. This enables developers and users to get
an overall experience of the latest changes on a more frequent basis. From
GCS 1.0 onward, we’ll re-evaluate the release cadance and update the list.

Highlights and updates since v0.2:
- Initial Prometheus and Grafana integration
- Glusterd2 container includes gluster-prometheus to export metrics
- CSI driver now supports snapshots
- CSI driver is pulled from a different location (that contains auto-built
images)

Included components:
- Glusterd2: https://github.com/gluster/glusterd2
- Gluster CSI driver: https://github.com/gluster/gluster-csi-driver
- Gluster-prometheus: https://github.com/gluster/gluster-prometheus

To get started with this snapshot, please see the releases page [1] and the
deploy instructions [2].

If you are interested in contributing, please see [3] or contact the
gluster-devel mailing list.

Regards,
Team GCS

[1] https://github.com/gluster/gcs/releases
[2] https://github.com/gluster/gcs/tree/master/deploy
[3] https://github.com/gluster/gcs
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Transfer file into WORM-State after FOP finished successfully

[David Spisla]

Hello folks,

I am implementing some stuff with the WORM Xlator and I have the idea to
transfer a file into the WORM state immediately after a FOP finished
successfully. Example

$ echo test >> test1.txt

After the FOP finished the file should be automatically WORMed. But I would
like to have an individual retention for each file, so I don't want to use
Volume Level WORM function.
At the moment autocommit is triggered after a specific period and the
current FOP (e.g. write) would be blocked, but I want it to be my file
WORMed immediately after the FOP (e.g. write) finished.

Maybe some of you have an idea. It should be possible to get the
information about the success of an FOP in one of cbk functions e.g if a
file is created and worm-file-level enabled, create_cbk sets the xattr
trusted.worm-file trusted.start_time for the file. So this should be
possible after a write FOP succeed?

Regards
David Spisla
___
Gluster-devel mailing list
Gluster-devel@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-devel