<div dir="ltr"><div>Thanks a lot for the welcome and suggestion! </div><div><br></div><div>I brought your suggestion up with my tutor and was informed VM pooling is something which has been discussed and considered internally and at this juncture it has been decided that pooling is an optimisation which is going to be implemented at a later date. At this time the system is going to be used </div><div><br></div><div>Makes sense from a performance perspective in an enterprise because you'd have separate storage server + all the images / software would likely be pre-loaded with the same bits of software. </div><div><br></div><div>This is not always going to be the case with us as we've got a lot of different images with varied installations, we've got students from different year groups using different images at the same time. Also we want the students to have the freedom to install their own tools / software.</div><div><br></div><div>The primary motivation for using oVirt at our university is to enable the students remote access to a lab environment. Although I mentioned in my previous mail that we wanted students to be able to quickly spin up VMs, I should have used the word simply, as it's more a case of minimising distractions + amount of actions required to create a VM from template.</div><div> </div><div>Unfortunately at this juncture we do not have the resources available to set up VM pooling for all of the different images we make use of so are going to approach the workflow in terms of students creating the VMs from template.</div><div><br></div><div>Many Thanks,</div><div>Thomas</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 January 2016 at 09:02, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Thanks for getting involved with oVirt!<br>
<span class="">><br>
> 1) The ability to quickly create a new VM from a template, whilst hiding<br>
> some of the complexity from the user.<br>
><br>
</span>It seems to me you can gain the same simplicity benefits by using VM<br>
pools and with no additional code...<br>
While cloud environments have made people used to dynamically spinning<br>
up VMs, this is a hammer that does not fit all nails, a pool of<br>
stateless pre-created VMs might suit your need better, and will work<br>
faster from an individual user's point of view.<br>
It is also more efficient in storage terms.<br>
<span class=""><br>
><br>
> 2) The ability to provide some of the more advanced features whilst hiding<br>
> some of the complexities of the Extended view<br>
</span>> ...<br>
><br>
> Proposed Solution A: Create a third tab ...<br>
><br>
> Proposed Solution B: Similar to the above ...<br>
<span class="">><br>
> Proposed Solution C: Add settings that will allow the user to enable/disable<br>
> GUI elements in the userportal as required.<br>
><br>
</span>I would go with solution C which seems to me the most generally useful...<br>
<span class=""><br>
><br>
> 3) Ability to specify sets of VM templates which can be created as new VMs<br>
> together<br>
><br>
</span>In conjunction with my proposal for feature 1, think about how this<br>
would work for pools...<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHEV-CI Team<br>
</font></span></blockquote></div><br></div>