FYI... Feedback about geo-replication user flows - thanks to Ju.
(http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience).
Please feel free to add/comment
thanks
sahina
-------- Original Message --------
Subject: Re: Geo-replication user flows
Date: Tue, 16 Sep 2014 13:49:17 -0400
From: Ju Lim <ju...@redhat.com>
To: Sahina Bose <sab...@redhat.com>
Hi Sahina:
Thanks for getting back to me. I took away 3 action items from the email:
Geo-replication session configuration options mockup -- we're working on
putting something together
Dashboard - what to show in the dashboard; we're working on putting
something together
Checkpoint history - what to show. Here's what I believe you should show:
* show what you would get from the "# gluster volume geo-replication
<source_volume> <destination_host>::<destination_volume> config
log-file | xargs grep checkpoint" command
* show the following columns (I'll assume you don't need a mockup as
this most likely would be shown in a table)
o checkpoint name, checkpoint creation date, amount of data
transferred (indicate if delta or cumulative size), status
Please feel free to forward to oVirt users.
Thanks,
Ju
On Sep 12, 2014, at 5:01 AM, Sahina Bose <sab...@redhat.com
<mailto:sab...@redhat.com>> wrote:
Ju,
Thanks for the detailed feedback. My responses inline.
On 09/11/2014 01:24 AM, Ju Lim wrote:
Sahina:
I finally had some time to review the Geo-replication proposal on
http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience.
Will we have a tab (sibling to Volumes, Clusters, etc.) for
Replication Sessions so a user can see all Geo-Replication Sessions
in 1 place vs. looking into every volume to identify them? I see
later a question asked about it. +1 that we need a "Geo-Replication
Sessions" or "Geo-Replication" in the main tab.
This tab would be empty if there are no replication sessions.
But having a tab will all replication sessions would be useful and
could be used to start a new one.
Is there a proposal yet for what we'll show related to replication in
the dashboard?
No, no proposal yet.
For the Geo-Replication detail tab (in the Volume main tab),
Should the action be "New" or "Create Session"? Reason I ask is that
it's "Create Volume" vs. "New Volume" in the master area.
We are trying to be consistent with the verbs..and have changed to
Volume -> New for creating a volume. So it should be "New Session" IMO
For the Create Session / New, can we use the same dialog whether it's
coming from the Geo-Replication detail tab (in the Volume main tab)
and the "Geo-Replication Sessions" main tab?
The only difference is that the one from the main tab would
additionally ask the source (host / IP Address + volume). For the
detail tab, instead of prompting for the source, we can show it.
Yes, it can be the same dialog. The information regarding source
volume would be prefilled if it's coming from the geo-replication sub-tab.
For the Destination (or Remote) Cluster Volumes, can the destination
volume be of a different volume type to participate in geo-replication?
Destination volume can be of a different volume type.
For the Geo-Replication Session Options, can we make the
configuration options
(https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/chap-User_Guide-Geo_Rep-Starting-Configure.html) more
usable vs. cryptic as it currently seems? Specifically, can we
showcase the defaults and provide the rest as Advanced configurations
that they can change?
We were planning to have a UI similar to the volume options. Do let us
know, if there's a better way to do this.
The Geo-Replication Session Details view -- I'm not sure what this is
telling the user other then how long the host has been up. Does this
mean that replication has been running for as long as the uptime for
those hosts? It seems to be missing Checkpoint information and
Checkpoint history information, which is important for
geo-replication consistency.
Specifically, when I think of what is typically shown in a
geo-replication session, I'd expect to see the following columns of
information:
Source Volume, Destination / Remote Volume, Status, Last Checkpoint,
Last Checkpoint Label
If different volume types can be used within the same replication
session, then we would also want to show the volume type on the
remote volume.
Session details view will also show information on files/bytes
skipped, moved etc per brick node.
Regarding checkpoint, there's currently only a checkpoint status being
shown. There's some enhancements to be done in gluster geo-rep with
regards to checkpoints
What information would need to be shown in checkpoint history?
BTW, do you know if there are plans to show volume size (total, used,
available/remaining) in the Volume master area?
Yes, we have introduced a volume capacity column in the Volumes tab,
which will show these details.
Is there any possibility to change the terminology from master-slave
to source-destination, source-remote, master-remote? The
master-slave terminology is quite unusual in the storage replication
realm. I ask as I see docs, CLI, etc. that already use the
master-slave terminology.
We could change in the docs and UI...CLI, not so sure.
We're happy to put together mockups and/or a proposal if it would be
helpful. Is this the best way to provide input, or should I be
posting my comments on
http://www.ovirt.org/Talk:Features/Gluster_Geo_Replication?
If you have suggestions on showing the configuration options and for
the dashboard, that would be welcome.
I could forward this to ovirt users for wider circulation.
thanks!
Please advise.
Thanks,
Ju
On Sep 4, 2014, at 10:23 AM, Sahina Bose <sab...@redhat.com
<mailto:sab...@redhat.com>> wrote:
Hi all,
The user experience section
http://www.ovirt.org/Features/Gluster_Geo_Replication#User_Experience ,
has been updated to capture the user flows. (The mockups, however,
are older and do not completely reflect the updated text)
There are couple of open questions. Please review and provide
suggestions.
thanks
sahina
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
