[Topic Migration - not a question really but something that comes to
mind wrt volume mgmt]
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.
Anand
On 12/12/2013 07:22 AM, Anand Avati wrote:
Hello all,
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.
https://gist.github.com/avati/af04f1030dcf52e16535#file-plan-md
Avati
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
