Gluster blog stories provide high-level spotlights on our users all over the world
Today, we are announcing the availability of GCS (Gluster Container Storage) 0.1. This initial release is designed to provide a platform for community members to try out and provide feedback on the new Gluster container storage stack. This new stack is a collaboration across a number of repositories, currently including the main GCS repository , core glusterfs , glusterd2 , and gluster-csi-driver .
The GCS repository provides a VM-based (Vagrant) environment that makes it easy to install and take GCS for a test-drive. See https://github.com/gluster/gcs/tree/master/deploy#local-cluster-using-vagrant for a set of instructions to bring up a multi-node cluster with GCS installed. The Ansible-based deploy scripts create a Kubernetes cluster using kubespray, then deploy the GCS components. These playbooks can also be used to bring up GCS on other Kubernetes clusters as well.
This is the initial release of the GCS stack. It allows dynamic provisioning of persistent volumes using the CSI interface. Supported features include:
Adding e2e testing for nightly validation of entire system
Will be adding gluster-prometheus for metrics. The work under this can be tracked at the gluster-prometheus repo 
Starting work on operator to deploy and manage the stack through anthill 
Bi-weekly update to the community on the progress made on GCS.
GCS project management
GCS and the other associated repos are coordinated via waffle.io for planning and tracking deliverables over sprints.
Cross-repo coordination of milestones and sprints will be tracked through a common set of labels, prefixed with “GCS/”. For example, we already have labels for major milestones defined like ‘GCS/alpha1’ , ‘GCS/beta0’. Additional labels will be created for each sprint so that the respective teams can tag planned deliverables in a common way.
Relationship to Heketi and glusterd (the legacy stack)
While GCS is shaping the future stack for Gluster in containers, the traditional method for deploying container-based storage with Gluster (and current GlusterD) and Heketi is still available, and it remains the preferred method for production usage. To find out more about Heketi and this production-ready stack, visit the gluster-kubernetes repo .
In order to plan the content for upcoming releases, it is good to take a moment of pause, step back and attempt to look at the consumption of GlusterFS within large enterprises. With the enterprise architecture taking large strides towards cloud and more specifically, the hybrid cloud, continued efforts towards...
The Gluster community is pleased to announce the release of 7.0, our latest release. This is a major release that includes a range of code improvements and stability fixes along with a few features as noted below. A selection of the key features and bugs addressed are documented in this...
Progress cannot be made without change. As technologists, we recognize this every day. Most of the time, these changes are iterative: progresssive additions of features to projects like Gluster. Sometimes those changes are small, and sometimes not. And that’s, of course, just talking about our project. But one of the...