1. Why GlusterD 2.0 - Gluster has come a long way being the POSIX-compliant distributed filesystem in clusters of small to medium sized clusters (10s-100s). Gluster.Next is a collection of improvements to push Gluster's capabilities to cloud-scale (read 1000s of nodes). GlusterD 2.0, the next version of our native Gluster management software, aims to offer devops-friendly interfaces to build, configure and deploy a 'thousand-node' Gluster cloud. 2. A high level description - The high level goal is to replace the current order-n-squared heartbeat/membership protocol with a much smaller "monitor cluster" based on Paxos or Raft. Replication of store can also be built using consistent distributed store like etcd/consul where only a subset of peers maintain the store. The transaction framework will be built around this store. The design should be modular with pluggable interfaces such that every features which consumes GlusterD becomes a separate plugin and feature owners owns the same. This will bring down lot of maintainability issues seen over recent past. GlusterD 2.0 will also focus on extending GlusterD to support new features as well as the external integration. We believe the following are important when we design a scalable enterprise-grade system. At scale, node failures, network failures are more common and the following are a few things we would continuously work on: * Query APIs, REST for every new feature/capability * Useful and searchable logs * Better documentation (both user and development) I'd request other 4.0 feature owners to share their feature details with Niels. Thanks, Atin On 01/20/2016 04:11 PM, Niels de Vos wrote: > Hi all, > > on Saturday the 30th of January I am scheduled to give a presentation > titled "Gluster roadmap, recent improvements and upcoming features": > > https://fosdem.org/2016/schedule/event/gluster_roadmap/ > > I would like to ask from all feature owners/developers to reply to this > email with a short description and a few keywords about their features. > My plan is to have at most one slide for each feature, so keep it short. > > Thanks, > Niels > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel