7 Feb
2013
7 Feb
'13
3:54 a.m.
Hi Tomas,
I've couple of comments, mainly from User POV.
Currently:
- we've many useful information, but only on Template tab. Once user
(administrator) wants create new VM, he HAVE TO go to template tab,
remember/write down name of template & then went back to VM tab & create Vm
from desired template.
New after this change:
- Administrator will go to tree - clicks few times (or just once in case is
expanded by default), then to DC then to Template tab.
Overall at lest +1 click => almost EACH time someone needs to create VM?
What if we bring these changes?
- Create VM window will show as much info about template as possible
- Description, NICs, list pf apps! (there is plenty useless space in gray
area on top of this window above/top/between {DC & CLUSTER})
- as much info as possible (VM subtab on Hosts/Templates main tabs)
- links between entities which are leading to different entities - once I'm in
template VM subtab, why I can't click to button & be transferred to VM tab to
see all info about this VM?
After mentioned changes I don't really care in which layer or how deep tabs
are. Currently we're adding/deleting tabs in each release in a loop.
P.
On Thursday 07 of February 2013 04:18:36 Tomas Jelinek wrote:
> I have completed the "User Interface" part (e.g. where the Images, Instance
> Types and Templates main tabs will be).
> http://www.ovirt.org/Features/Instance_Types#User_Interface
>
> Your comments are welcome,
> Tomas
>
> ----- Original Message -----
> From: "Tomas Jelinek" <tjelinek@redhat.com>
> To: "Oved Ourfalli" <ovedo@redhat.com>
> Cc: engine-devel@ovirt.org
> Sent: Tuesday, February 5, 2013 5:14:00 PM
> Subject: Re: [Engine-devel] Instance Types Feature
>
> > 1. Why do we need a new set of permissions for "Create Instance" and
> > "Instance Owner"? Aren't the VmCreator role and the UserVmManager role
> > enough in these use-cases?
> so checked this with Andy:
> - Create Instance: it is a permission to actually see the instance types in
> the list of instance types when creating the VM and to be able to create a
> VM from that instance type - Instance Owner: if the user has this
> permission, he can edit the fields marked as "Basic User" in the table in
> the wiki (but not the others)
>
> ----- Original Message -----
> From: "Oved Ourfalli" <ovedo@redhat.com>
> To: "Tomas Jelinek" <tjelinek@redhat.com>
> Cc: engine-devel@ovirt.org
> Sent: Tuesday, January 29, 2013 2:54:13 PM
> Subject: Re: [Engine-devel] Instance Types Feature
>
> Some questions:
> 1. Why do we need a new set of permissions for "Create Instance" and
> "Instance Owner"? Aren't the VmCreator role and the UserVmManager role
> enough in these use-cases? 2. iiuc, the internal implementation of instance
> types and images will be done using templates. However, I guess we plan to
> expose instance types and images as REST resources, right?
>
> Thank you,
> Oved
>
> ----- Original Message -----
>
> > From: "Tomas Jelinek" <tjelinek@redhat.com>
> > To: engine-devel@ovirt.org
> > Sent: Tuesday, January 22, 2013 3:09:51 PM
> > Subject: [Engine-devel] Instance Types Feature
> >
> > Hi All,
> >
> > this is the proposed new feature called instance types:
> > http://www.ovirt.org/Features/Instance_Types
> >
> > Long story short - it should basically split the VM template into:
> > - "hardware profile" called instance types
> > - "software profile" called image
> >
> > This should enable to do something like: Create a new "small" VM and
> > attach a disk with "RHEL + Postgres" installed.
> >
> > Any comments are more than welcome!
> >
> > Tomas
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
> _______________________________________________
> Engine-devel mailing list
> Engine-devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel