RFC: Discover Kimchi Peers - UI Mockup
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc. On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 2014?08?19? 01:23, Aline Manera wrote:
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc.
New tab is needed if we want detailed info, and I would like we retain this as a shortcut that we can easily cruise between nodes.
On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 8/19/2014 1:23 AM, Aline Manera wrote:
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc.
This is kimchi peers and kimchi need login. My thinking is that when user click on a kimchi link, then open a new brower tab and the login screen will appear. Something like "Windows Network Neighborhood". Aline, how do you get more information like numbers of vms without login? or you have a much bigger picture in mind that this feature will evolve greatly in the future like virt-manager to add connection info for each kimchi peer? then all virtualization resources across the intranet will be managed in one web console(I strongly support to discuss this direction).
On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 08/19/2014 07:55 AM, Yu Xin Huo wrote:
On 8/19/2014 1:23 AM, Aline Manera wrote:
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc.
This is kimchi peers and kimchi need login. My thinking is that when user click on a kimchi link, then open a new brower tab and the login screen will appear.
That is the plan.
Something like "Windows Network Neighborhood".
Aline, how do you get more information like numbers of vms without login?
Ops... I have forgotten about this detail.
or you have a much bigger picture in mind that this feature will evolve greatly in the future like virt-manager to add connection info for each kimchi peer? then all virtualization resources across the intranet will be managed in one web console(I strongly support to discuss this direction).
I have thought a little bit about this bigger scenario but I haven't have a position on it yet.
On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 08/19/2014 09:13 AM, Aline Manera wrote:
On 08/19/2014 07:55 AM, Yu Xin Huo wrote:
On 8/19/2014 1:23 AM, Aline Manera wrote:
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc.
This is kimchi peers and kimchi need login. My thinking is that when user click on a kimchi link, then open a new brower tab and the login screen will appear.
That is the plan.
Something like "Windows Network Neighborhood".
Aline, how do you get more information like numbers of vms without login?
Ops... I have forgotten about this detail.
or you have a much bigger picture in mind that this feature will evolve greatly in the future like virt-manager to add connection info for each kimchi peer? then all virtualization resources across the intranet will be managed in one web console(I strongly support to discuss this direction).
I have thought a little bit about this bigger scenario but I haven't have a position on it yet.
Let's do it as you have proposed and then we can discuss in a bigger scenario with auto-login to peers and then switch to a tab view.
On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 8/19/2014 1:23 AM, Aline Manera wrote:
What about a new tab? So we can list the peers in a list view (as we did for storage and network) In this way we can easily display more information later: like number of vms, etc.
I have concerns about displaying the kimchi information in tab view: 1) It seems peers is a higher level than kimchi and can redirect to other kimchi whereas tabs are within one kimchi. So from my point of view, I suggest not to put peers in the tab. 2) I am worried about whether user should see the information from other server in the peer view, like number of vms, shouldn't those be protected from seen by others who might not have the authority to see. Thanks & Best Regards Wang Wen
On 08/18/2014 07:53 AM, Yu Xin Huo wrote:
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
participants (4)
-
Aline Manera -
Royce Lv -
Wen Wang -
Yu Xin Huo