<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 21, 2016 at 10:48 AM, Shyam <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 12/21/2016 09:15 PM, Prasanna Kalever wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[Top posting]<br>
<br>
I agree with Niels and Shyam here. We are now trying to decouple the<br>
gluster-block cli from gluster cli.<br>
Since anyway it doesn't depend on core gluster changes, I think its<br>
better to move it out. Also I do not see a decent tool/util that does<br>
these jobs, hence its better we make it as a separate project (may be<br>
gluster-block).<br>
The design side changes are still in discussion, I shall give an<br>
update once we conclude on it.<br>
<br>
Since gluster-block plans to maintain it as separate project, I don't<br>
think we still need to make it as 3.10 feature.<br>
With gluster-block we will aim to support all possible versions of gluster.<br>
</blockquote>
<br></span>
Should this be bundled with gluster? If so, it maybe a good thing to track that part against gluster releases (3.10 or otherwise). Just a thought.</blockquote><div><br></div><div>I think gluster-block can have an independent lifecycle as it will be more iterative than gluster in terms of releases. Nevertheless for the next few Gluster releases it would be good to highlight gluster-block's capabilities as part of our release notes.</div><div><br></div><div>Thanks,</div><div>Vijay</div><div><br></div></div></div></div>