1:18 p.m.
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE3301811EEASERV070corpeldo_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi everyone,
I noticed some issues with the "New Pool" dialog in the webadmin interface.=
When creating a new pool, I cannot change the selected cluster and the sel=
ected template, it automatically resets into the initial selection, that ap=
peared when the dialog was first shown, when I try to choose something else=
. I also noticed that, in the revision 0d9da7d0d922bc9f0eecaf6f4eecad77e8b2=
e3e2, the interface automatically changed the selected cluster after the us=
er had selected a template. How should this dialog behave? Was the previous=
behavior the correct one?
There are also some issues on how to introduce the multi-architecture suppo=
rt into the webadmin interface. When the user is creating a Pool or a VM, h=
e shouldn't be able to use templates that are based on a x86 VM to create a=
VM/Pool in a PPC64 cluster (and vice-versa). This kind of problem could be=
avoided if the interface hid incompatible templates given a cluster, or hi=
d incompatible clusters given a template, or maybe it could let the user ch=
oose any template or cluster, and only show an error after the OK button is=
pressed. What would be a proper way to handle this?
Thanks,
Vitor de Lima
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE3301811EEASERV070corpeldo_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40" <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"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=3D"edit" spidmax=3D"1026" / </xml><![endif]--><!--[if gte mso
9]><xml <o:shapelayout
v:ext=3D"edit" <o:idmap v:ext=3D"edit"
data=3D"1" /
</o:shapelayout></xml><![endif]--
</head <body lang=3D"PT-BR"
link=3D"blue" vlink=3D"purple" <div
class=3D"WordSection1" <p
class=3D"MsoNormal"><span lang=3D"EN-US">Hi
everyone,<o:p></o:p></span><=
/p <p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">I noticed some issues with the =
“New Pool” dialog in the webadmin interface. When creating a ne=
w pool, I cannot change the selected cluster and the selected template, it =
automatically resets into the initial selection,
that appeared when the dialog was first shown, when I try to choose someth=
ing else. I also noticed that, in the revision 0d9da7d0d922bc9f0eecaf6f4eec=
ad77e8b2e3e2, the interface automatically changed the selected cluster afte=
r the user had selected a template.
How should this dialog behave? Was the previous behavior the correct one?<=
o:p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">There are also some issues on h=
ow to introduce the multi-architecture support into the webadmin interface.=
When the user is creating a Pool or a VM, he shouldn’t be able to us=
e templates that are based on a x86 VM to
create a VM/Pool in a PPC64 cluster (and vice-versa). This kind of problem=
could be avoided if the interface hid incompatible templates given a clust=
er, or hid incompatible clusters given a template, or maybe it could let th=
e user choose any template or cluster,
and only show an error after the OK button is pressed. What would be a pro=
per way to handle this?<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-US">Thanks,<o:p></o:p></span></p <p class=3D"MsoNormal">Vitor de
Lima<o:p></o:p></p </div </body
</html
--_000_B2CAFC4D5E2D574A883EF61ACD5ADE3301811EEASERV070corpeldo_--
3:32 a.m.
Hi Vitor,
comments inline
have a nice day,
Tomas
----- Original Message -----
From: "Vitor de Lima" <vitor.lima(a)eldorado.org.br>
To: engine-devel(a)ovirt.org
Sent: Thursday, August 29, 2013 8:18:28 PM
Subject: [Engine-devel] About the "New Pool" dialog box
Hi everyone,
I noticed some issues with the “New Pool” dialog in the webadmin interface.
When creating a new pool, I cannot change the selected cluster and the
selected template, it automatically resets into the initial selection, that
appeared when the dialog was first shown, when I try to choose something
else. I also noticed that, in the revision
0d9da7d0d922bc9f0eecaf6f4eecad77e8b2e3e2, the interface automatically
changed the selected cluster after the user had selected a template. How
should this dialog behave? Was the previous behavior the correct one?
Thank you for reporting this! I have created a BZ for it
(https://bugzilla.redhat.com/show_bug.cgi?id=1002902)
and submitted a patch fixing it (http://gerrit.ovirt.org/#/c/18713/).
The correct behavior is that the selection of the template should not touch the
DC/Cluster.
There are also some issues on how to introduce the multi-architecture support
into the webadmin interface. When the user is creating a Pool or a VM, he
shouldn’t be able to use templates that are based on a x86 VM to create a
VM/Pool in a PPC64 cluster (and vice-versa). This kind of problem could be
avoided if the interface hid incompatible templates given a cluster, or hid
incompatible clusters given a template, or maybe it could let the user
choose any template or cluster, and only show an error after the OK button
is pressed. What would be a proper way to handle this?
Normally we hide the incompatible selections according to the selected DC/Cluster.
So, if it was me I would filter the list of the templates according to the selected
DC/Cluster.
Thanks,
Vitor de Lima
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
3891
days inactive
3892
days old
1 comments
2 participants
participants (2)
-
Tomas Jelinek -
Vitor de Lima