Blank template is quite useless and a constant source of confusion. We should make it editable so people can set a system-wide defaults. When it's renamed to "Defaults" it would also be a bit more clear why it can't be removed and is hard-wired into many flows. And as a bonus, we can replace some of the VdcOptions-only global things with simple edit of the "Default" template
*** Bug 1072045 has been marked as a duplicate of this bug. ***
address sub-version of defaults too
after consulting with Liz: Short term, I think it is OK to rename the 'Blank' template to 'Defaults', allow users to edit it, etc. towards 4.0, I think that we should re-think whether it makes sense to treat that 'Blank'/'Default' entity as a Template (i.e. display it in the Templates main tab, etc.), or does it make more sense to allow a completely different way of controlling the defaults for creating a VM from scratch.
Please note that the "38817: core: renamed the blank template to default" patch had to be rewerted because of backward compatibility - e.g. the implementation is that the blank template is editable but it is still named Blank. There is a possibility to rename it if the user decides to do so. The updated feature page: http://www.ovirt.org/Features/Blank_to_Defaults#Proposal
Tomas, thanks for your comments. i added the a test case and specific about SPICE and VNC. please approve the test plan, thanks.
yes, seems ok to me
try to verify on : Red Hat Enterprise Virtualization Manager Version: 3.6.0.3-0.1.el6 link to polarion test : https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/wiki/Compute/3_6_VIRT_Blank_template?query=NOT%20type:heading%20AND%20(NOT%20TEST_RECORDS:(%22RHEVM3/3_6_VIRT_Blank_template_2%22,@any))&tree_depth=0&tab=tree failed on the following test : check vnc+spice: 1. edit the blank template 2. got to Console tab 3. in Graphics protocol choose VNC+SPICE 4. create 2 vms with this template - one with the 3.5 cluster and one with 3.6 The vm in 3.6 cluster will inheritance the VNC+SPICE and the vm in 3.5 should be inherit only SPICE but she also inheritance VNC+SPICE Tomas, should i move this bug back to assigned?
In cluster level 3.5 you should not be able to create a VM which has both SPICE and VNC (regardless of Blank template setting). So, if the combo box contains the SPICE+VNC than it is a separate bug (which blocks this one from verification but still a separate one...).
verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.3-0.1.el6 link to polarion test run : https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/wiki/Compute/3_6_VIRT_Blank_template?query=TEST_RECORDS:%28%22RHEVM3/3_6_virt_blank_template_7_2%22,@any%29&tree_depth=0&sidebar=testrun&testrun=3_6_virt_blank_template_7_2&tab=tree