Hi Luis,
On Sat, Dec 12, 2015 at 3:35 AM, Luis Pabón wrote:
> My proposal is for gdeploy to communicate with Heketi, glusterd, and the
> system itself to service requests from the administrator. Communicate with
> Heketi for all volume allocation/deallocation, with glusterd for any
> modificat
My proposal is for gdeploy to communicate with Heketi, glusterd, and the
system itself to service requests from the administrator. Communicate
with Heketi for all volume allocation/deallocation, with glusterd for
any modifications on the volume, and with the node operating system (if
really nec
On Fri, Dec 11, 2015 at 12:31 PM, Luis Pabon wrote:
> I think at its simplest would be to specify workflow examples and how
> gdploy+Heketi would satisfy them. I will be sending out some possible
> workflows tomorrow.
>
Awesome, I will see if we can add something to it.
>
> Also, there is a p
I think at its simplest would be to specify workflow examples and how
gdploy+Heketi would satisfy them. I will be sending out some possible
workflows tomorrow.
Also, there is a python Heketi client in the works right now which would
benefit gdeploy: https://github.com/heketi/heketi/pull/251 .
Hi Luis,
On Fri, Dec 11, 2015 at 12:01 PM, Luis Pabon wrote:
> Hi Sachidananda,
> I think there is a great opportunity to enhance GlusterFS management by
> using gdeploy as a service which uses Heketi for volume management.
> Currently, gdeploy sets up nodes, file systems, bricks, and volumes.
Hi Sachidananda,
I think there is a great opportunity to enhance GlusterFS management by using
gdeploy as a service which uses Heketi for volume management. Currently,
gdeploy sets up nodes, file systems, bricks, and volumes. It does all this
with input from the administrator, but it does no