This is a multi-part message in MIME format. --------------060308090303000405080600 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 08/30/2013 10:51 PM, Leonardo Bianconi wrote:
Hi everyone!
During the development of PPC64 support in the engine, we faced some UX issues regarding the default Cluster (that Cluster with empty processor name).
Currently, oVirt engine allows the default Cluster to contain empty processor name, and the administrator can add VMs and/or Templates to it. The processor name can be assigned later, editing the cluster or assigning a valid host to it.
During the implementation of PPC64 support on the engine, the field "architecture" was added to Clusters, VMs and Templates entities.
So we have the following questions regarding how the UI should behave:
- Shall we keep allowing the administrator to assign VMs and Templates to the Cluster with no processor name or assigned architecture ?
-> If we have an "yes" for the question above:
-- We will have to assign the architecture to the Cluster based on the OS of the first assigned VM, and the processor name could be defined the same way as currently ... editing the Cluster or assigning a compatible Host to it.
-- The VM creation popup will have to be able to indicate the architecture of each OS ... some OSes have the same name, and it may get ambiguous since the Cluster architecture is still undefined at that point (before the first VM get already created).
Thanks!
Regards.
Leonardo Bianconi
To add VMs you anyway need a running host in the cluster which means the cpu name and the architecture would be the host's. So we can keep the cluster attributes - "cpu name" and "arch" consistent and allow them to be empty on creation.
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
--------------060308090303000405080600 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 08/30/2013 10:51 PM, Leonardo Bianconi wrote:<br> </div> <blockquote cite="mid:50EB20226B72D6419356FC320AB62B8719173370@SERV070.corp.eldorado.org.br" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style><!-- /* Font Definitions */ @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:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;} 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-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif"; mso-fareast-language:EN-US;} @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]--> <div class="WordSection1"> <p class="MsoNormal"><span lang="EN-US">Hi everyone!<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">During the development of PPC64 support in the engine, we faced some UX issues regarding the default Cluster (that Cluster with empty processor name).<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">Currently, oVirt engine allows the default Cluster to contain empty processor name, and the administrator can add VMs and/or Templates to it. The processor name can be assigned later, editing the cluster or assigning a valid host to it.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">During the implementation of PPC64 support on the engine, the field “architecture“ was added to Clusters, VMs and Templates entities.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">So we have the following questions regarding how the UI should behave:<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">- Shall we keep allowing the administrator to assign VMs and Templates to the Cluster with no processor name or assigned architecture ?<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"> -> If we have an “yes” for the question above:<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"> -- We will have to assign the architecture to the Cluster based on the OS of the first assigned VM, and the processor name could be defined the same way as currently … editing the Cluster or assigning a compatible Host to it.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"> -- The VM creation popup will have to be able to indicate the architecture of each OS … some OSes have the same name, and it may get ambiguous since the Cluster architecture is still undefined at that point (before the first VM get already created).<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal">Thanks!<o:p></o:p></p> <p class="MsoNormal">Regards.<o:p></o:p></p> <p class="MsoNormal">Leonardo Bianconi<o:p></o:p></p> </div> </blockquote> <br> To add VMs you anyway need a running host in the cluster which means the cpu name and the architecture would be the host's. <br> So we can keep the cluster attributes - "cpu name" and "arch" consistent and allow them to be empty on creation. <br> <blockquote cite="mid:50EB20226B72D6419356FC320AB62B8719173370@SERV070.corp.eldorado.org.br" type="cite"> <div class="WordSection1"> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Engine-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/engine-devel">http://lists.ovirt.org/mailman/listinfo/engine-devel</a> </pre> </blockquote> <br> </body> </html> --------------060308090303000405080600--