<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">[Topic Migration - not a question
really but something that comes to mind wrt volume mgmt]<br>
<br>
The doc mentions volumes as "virtual objects" - are these (in
any way) being planned as objects/units of migration should the
use-case arise as one of the architectural goals? or could that
change? For example, if one wants to migrate an entire cluster to
a completely new (but similar in configuration) set of hardware -
is it an op better managed at a cluster level or at a
virtual-volume or virtual object level? Think cross DC migration
scenarios.<br>
<br>
Anand<br>
<br>
On 12/12/2013 07:22 AM, Anand Avati wrote:<br>
</div>
<blockquote
cite="mid:CAFboF2y-oBz16qV0FP7MZV7Zh0Lx3B9H7o3=d9SwzLHrmGM6BA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hello all,</div>
<div><br>
</div>
Here is a working draft of the plan for 4.0. It has pretty
significant changes from the current model. Sending it out for
early review/feedback. Further revisions will follow over time.
<div>
<br>
</div>
<div><a moz-do-not-send="true"
href="https://gist.github.com/avati/af04f1030dcf52e16535#file-plan-md">https://gist.github.com/avati/af04f1030dcf52e16535#file-plan-md</a><br>
</div>
<div><br>
</div>
<div>Avati</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a>
<a class="moz-txt-link-freetext" href="https://lists.nongnu.org/mailman/listinfo/gluster-devel">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>