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(a)redhat.com>
To: "Tomas Jelinek" <tjelinek(a)redhat.com>
Cc: engine-devel(a)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(a)redhat.com>
To: engine-devel(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel