9:54 a.m.
Hi List,
I've made an oVirt node installation (oVirt ver. 4.4.9) for a VDI project and I'd
like to ask if it is possible to create an empty pool with a maximum number of machine and
as the machine are required by the end user (so when the users use the think client to
request the provisioning of a machine of the pool in question) the pool will dynamically
create the machine and link it to the end user.
To specify once more the pool will be create with no machine in it, only a maximum limit
on the number of machines, and as the user start connecting to the pool the VM will be
created, started and provisioned to the user requesting them.
Then when the user stop using the machine they would like the system to save the datas and
stop the machine and from that point on when the user will connect the virtual machine
connected to their account on the AD system should start.
Do you know if this is possibile?
Thanks a lot to everybody,
Luca
10:32 a.m.
On Sun, Dec 5, 2021 at 12:33 PM Luca Contessa <ifdevurandom(a)gmail.com>
wrote:
oVirt doesn't provide that exact behavior but maybe the existing behavior
could also fit your needs.
You can't create a pool that is initially empty and grows as users ask for
VMs - the VMs are rather created when creating the pool. From a storage
perspective, empty thin-provisioned volumes are created on top of the
template volumes so they don't consume much space. From a virtualization
perspective, no compute resources are consumed until the VMs are started.
Having the VMs created "in advance" enables users to take VMs faster -
there's no need to create them but just to assign and start them.
As for the second part, you can configure a console disconnect option to
shut-down/power-off so when a user disconnects, the VM would stop. If you
wish VMs to remain assigned to users also when they go down, you can set
the pool to "manual" mode and then VMs remain assigned until the admin
detaches their assigned users.
8:08 a.m.
Thanks a lot for the detailed answer, the first part was just a personal preference and
it's good to know that the performance will not be impacted by the presence of the
inactive VMs.
As for the second part I will set the pool to "manual" mode and configure the
console disconnect option as you suggested.
1271
days inactive
1274
days old
2 comments
2 participants
participants (2)
-
Arik Hadas -
Luca Contessa