----- Original Message ----- > From: "Krishnan Parthasarathi" <kparthas@xxxxxxxxxx> > To: "Balamurugan Arumugam" <barumuga@xxxxxxxxxx> > Cc: gluster-users@xxxxxxxxxxx, "Gluster Devel" <gluster-devel@xxxxxxxxxxx> > Sent: Thursday, September 11, 2014 2:25:45 PM > Subject: Re: [Gluster-devel] Proposal for GlusterD-2.0 > > Bala, > > I think using Salt as the orchestration framework is a good idea. > We would still need to have a consistent distributed store. I hope > Salt has the provision to use one of our choice. It could be consul > or something that satisfies the criteria for choosing alternate technology. > I would wait for a couple of days for the community to chew on this and > share their thoughts. If we have a consensus on this, we could 'port' > the 'basic'[1] volume management commands to a system built using Salt and > see for real how it fits our use case. Thoughts? > For distributed store, I would think of MongoDB which provides distributed/replicated/highly available/master read-write/slave read-only database. Lets get what community think about SaltStack and/or MongoDB. > > [1] basic commands - peer-probe, volume-create, volume-start and > volume-add-brick > Regards, Bala _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
