Hi Arik,
El 10/11/20 a las 15:22, Arik Hadas escribió:
On Tue, Nov 10, 2020 at 4:37 PM Nicolás <nicolas(a)devels.es
<mailto:nicolas@devels.es>> wrote:
Hi Arik,
El 10/11/20 a las 13:21, Arik Hadas escribió:
>
>
> On Tue, Nov 10, 2020 at 3:08 PM Nicolás <nicolas(a)devels.es
> <mailto:nicolas@devels.es>> wrote:
>
> Hi Sharon,
>
> Thanks for the reply! I've opened [1], so hopefully someone
> will be able to implement it.
>
> Regards,
>
> Nico
>
> [1]:
https://github.com/oVirt/ovirt-site/issues/2389
>
> El 10/11/20 a las 11:38, Sharon Gratch escribió:
>> Hi,
>>
>> This feature of cloning a VM was indeed part of the old User
>> Portal and you are right that it's not supported by the
>> newer VM Portal (since oVirt 4.3).
>> It seemed that this wasn't required by VM Portal users (no
>> user complained up till now) and that's why we omitted it
>> and it's not part of our current roadmap to implement it as
>> well.
>>
>> Nevertheless, there is no real reason not to include that
>> ability as part of VM Portal, so you are most welcome to
>> open an issue on
https://github.com/oVirt/ovirt-web-ui/issues
>> <
https://github.com/oVirt/ovirt-site/issues>
>> and you can push a fix yourself if you have time (or someone
>> else from the community) :-)
>>
>> Thanks!
>> Sharon
>>
>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás <nicolas(a)devels.es
>> <mailto:nicolas@devels.es>> wrote:
>>
>> Hi,
>>
>> We're using oVirt 4.3.8, having an organization that
>> intensively uses
>> the User Portal. After upgrading from 4.2, we've noticed
>> that cloning a
>> VM from within the User Portal is not possible anymore.
>> In our case,
>> this feature was heavily used by hundreds of students
>> deploying their VMs.
>>
>
> Out of curiosity, why cloning a VM and not provisioning the VMs
> from template(s)?
Most of our students are IT-related, and their professors want to
teach them the procedure to deploy a VM from scratch. Some other
courses surely deploy their VMs from a template as they are not
that IT oriented and they just want to have a working VM instead
of building it from scratch. We have a lot of casuistry, but in
our case about 400~500 students would very welcome having back the
clone option.
Thanks Nicolás.
I'd say that even for the IT-related students it may make more sense
to provision VMs from templates instead of cloning VMs -
so you want them to deploy VMs from scratch, which means starting with
a VM that is based on the blank template, add disk(s) and other
devices, install and configure the guest and such; and then the
students would use clone-VM to duplicate the VM they just prepared, right?
Yep, that's mostly it.
Why would you want them to clone the VM rather than creating a
template out of this VM and provision further VMs from that template
with thin-provisioned disks?
Because that would involve creating templates, and would require a
permission they don't have. We've chosen a few permissions which make
them able to deploy their own machines, but we don't want them to create
templates or even access the admin panel.
Additionally, courses are composed of groups of students which deploy
different infrastructures. So one could deploy an HAproxy architecture,
some other could deploy a pacemaker+corosync architecture with different
parameters (some of them need more disk, some of them need more
memory...), so each group would need to create templates just to deploy
a couple machines.
I think it's more practical (in this case) to deploy the couple of
machines using a clone option. In some other courses, where all the VM
parameters are equal, it's better to deploy the VM from a template and
some subjects use this option too.
Thanks.
Nico
Regards,
Nico
>>
>> Is this feature in the roadmap yet? If not, do you
>> consider it useful to
>> open a RFE?
>>
>> Thank you.
>>
>> Regards,
>>
>> Nico
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> <mailto:users@ovirt.org>
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> <mailto:users-leave@ovirt.org>
>> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>>
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/HFMFJRV3AC3...
>>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave(a)ovirt.org
> <mailto:users-leave@ovirt.org>
> Privacy Statement:
https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/RUEW52WZUD2...
>