<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I agree with option 3 considering that the idea here is to solve
this<br>
"Kimchi feature being coded in WoK" problem and this is easier<br>
than moving everything to WoK.<br>
<br>
<br>
Daniel <br>
<br>
<br>
<div class="moz-cite-prefix">On 07/04/2016 12:27 PM, Aline Manera
wrote:<br>
</div>
<blockquote
cite="mid:dcc1f9f3-6632-8b7c-9872-2c811b69039b@linux.vnet.ibm.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi all,<br>
<br>
Kimchi provides an feature called federation to discover other Wok
servers running in the same network.<br>
This feature is not enabled by default. To enable it, the user
needs to follow the instructions in
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/kimchi-project/kimchi/blob/master/docs/README-federation.md">https://github.com/kimchi-project/kimchi/blob/master/docs/README-federation.md</a><br>
<br>
The problem is: this feature is exposed by the user as a drop down
menu with a list of servers found. But it is displayed in the top
header, ie, on Wok header.<br>
That way, we have some code on Wok related to a Kimchi feature.<br>
To fix it, we should change the way we expose that feature on UI
moving it as a content tab.<br>
As it is not strictly related to virtualization I don't see it
fits in any current Kimchi tabs and I don't think it justifies a
new tab.<br>
But from the other hand, there is a plan to integrate the
federation feature with guest migration, so user don't need to
input the server details to do the migration - he/she only needs
to select one from the list. Said that, the federation feature is
still required for Kimchi.<br>
<br>
So I have 3 proposals:<br>
<br>
1. Move federation feature to WOK<br>
The peers will continue to be displayed as part of the top header
but all code (backend/API) will be moved to Wok.<br>
<br>
2. Move federation feature to Ginger Base<br>
The Dashboard tab will display a new section with the peers
information when federation is enabled.<br>
<br>
3. Keep federation feature on Kimchi and make Kimchi extend the
Ginger Base UI (the same way Ginger s390x does with Ginger tabs)<br>
The Dashboard tab will be extended by Kimchi to display a new
section with the peers information when federation is enabled.<br>
<br>
<b>I prefer the option 3</b> as it solves the original issue
(having UI code related to a Kimchi feature on Wok) and do not
affect any other plugin or Wok behavior.<br>
<br>
Once we get an agreement on it, I will proper involve Ginger
community if needed.<br>
<br>
What are you thoughts on it?<br>
<br>
Regards,<br>
Aline Manera<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>