<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="PT-BR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I agree with option 3. Once I finish the tasks I’m allocated with I’ll draw some mockups for Ginger sidebar proposal that
involves some minor changes in Wok navbar and main content area on HD screen resolutions and I think the navbar won’t have enough space to hold the menu items, the user actions and help button.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Samuel<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> kimchi-devel-bounces@ovirt.org
[mailto:kimchi-devel-bounces@ovirt.org] <b>On Behalf Of </b>Aline Manera<br>
<b>Sent:</b> segunda-feira, 4 de julho de 2016 12:27<br>
<b>To:</b> Kimchi Devel <kimchi-devel@ovirt.org><br>
<b>Subject:</b> [Kimchi-devel] Changing the way federation feature (peers) is exposed to user<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 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<o:p></o:p></p>
</div>
</body>
</html>