Good Morning! I recently added a second cluster to an oVirt environment and I am looking to re-use a number of templates between the clusters while providing self-service to users through the VM Portal. I would like to describe what I am seeing and ask whether you might know of what I am missing - or if you could share your experience.
For sake of discussion, let us call the clusters "CORE" and "PROD" (the new cluster) and the template "UbuntuServer24". The template was created in cluster CORE against Storage Domain "CORE1". The template is visible to all users (role "UserTemplateBasedVm" for Everyone). CORE and PROD clusters contain the same networks and the hosts mount the same Storage Domains though, by policy, PROD cluster users are restricted to creating Disks only on Storage Domain "PROD1" through roles/permissions. User JDOE is a PROD cluster user, has VM Portal/"User role" rights to the cluster and Storage Domain and is able to deploy and manage VMs in Cluster PROD. JDOE is not intended to have any permissions against Cluster CORE. JDOE has temporary Admin Portal rights but I would prefer they operate through VM Portal at all times. Here is what I am seeing: Using the Administrator Portal, JDOE can deploy template UbuntuServer24 in PROD without any trouble. Using the VM Portal, using "Create Virtual Machine", JDOE does not see the "UbuntuServer24" template in the list of available templates. It appears to be filtered out of the list. Based on research so far, I can create a second copy of the template (ex: deploy a VM and capture a template in cluster PROD) as different name "UbuntuServer24-PROD". With no other changes, user JDOE can successfully deploy this new template into cluster PROD via VM Portal. I think this proves JDOE permissions and roles are in good shape. For testing I have also temporarily added equivalent permissions for JDOE against Cluster CORE and can confirm that the "UbuntuServer24" is only displayed as a Template when cluster "CORE" is selected as the target for the new VM in the "Create Virtual Machine" flow. The duplicated template approach does work but it means that there are two templates to offer the same result in each of the two clusters. I am concerned that this leaves an opportunity for de-sync, some additional storage consumption, and an enforced requirement for a different template name (string) which complicates user-facing documentation. Ideally I would like to maintain a single template to keep things simple and make it easy for other team members to use and maintain the environment. I tried to find a reference to my query in the docs as well as web search but didn't come up with something I was confident was on the right path. Is there a way to reuse templates between clusters in this manner and, if so, could you kindly please point me in the right direction? Thank you very much for any advice you may have, Dan Galway _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]/message/TMJALW7UVEM3FGTAHXDC2UHFRPFR3XZV/
