[Tendrl-devel] Using gdeploy for gluster brick provisioning

Darshan Narayana Murthy dnarayan at redhat.com
Fri Dec 16 10:49:43 UTC 2016



----- Original Message -----
> From: "Sachidananda URS" <surs at redhat.com>
> To: "Darshan Narayana Murthy" <dnarayan at redhat.com>
> Cc: "Mailing list for the contributors to the Tendrl project" <tendrl-devel at redhat.com>
> Sent: Friday, December 16, 2016 2:18:02 PM
> Subject: Re: Using gdeploy for gluster brick provisioning
> 
> Hi Darshan,
> 
> On Fri, Dec 16, 2016 at 12:17 PM, Darshan Narayana Murthy <
> dnarayan at redhat.com> wrote:
> 
> > Hi sac,
> >
> > Considering that tendrl will use gdeploy to provision gluster cluster, It
> > seems very
> > logical to use gdeploy for brick provisioning as well. Instead of having
> > the code to
> > provision bricks in tendrl code base. But for us to consume brick
> > provisioning from
> > gdeploy, we need some changes in it. Like gdeploy has to use tools like
> > blivet,
> > libstoragemgmt underneath to provision gluster bricks.
> >
> >
> That will be a lot of changes. We will have to see how this can be achieved.
> 
> 
> > To discuss the feasibility of including these changes, we can raise RFE
> > against
> > gdeploy. What would be the right place for this ?
> >
> >
> 
> Github would the place for that. Can you please raise an issue on github?

Thanks sac,

Have raised an issue: https://github.com/gluster/gdeploy/issues/257 to discuss
further about this

-Darshan

> 
> -sac
> 




More information about the Tendrl-devel mailing list