[engine-devel] Turn Blank template into defaults
Hi All, I have started to work on a new feature[1] which will make it possible to edit the Blank template. The proposal is available on the feature page[2] Any comments are more than welcome, Tomas [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1130174 [2]: http://www.ovirt.org/Features/Blank_to_Defaults
On 22/01/15 11:28, Tomas Jelinek wrote:
Hi All,
I have started to work on a new feature[1] which will make it possible to edit the Blank template. The proposal is available on the feature page[2]
Any comments are more than welcome, Tomas
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1130174 [2]: http://www.ovirt.org/Features/Blank_to_Defaults
Well you can't just rename the blank template to "default". You would break any upgrade from 3.5. if you did. At least you could not run any pre 3.6. cluster level vms on this 3.6. engine. Is it intended to break compatibility in this release or not? 3.5 cluster level vms (e.g. new created vms) need afaik the "blank" template. how do you want to handle that? could you instead add this "default" template just for cluster/dc level 3.6, so just "3.6" vms use it? In general I think this is a much anticipated and needed feature, so I'm looking forward to the 3.6 release! :) -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On Jan 22, 2015, at 13:15 , Sven Kieske <S.Kieske@mittwald.de> wrote:
On 22/01/15 11:28, Tomas Jelinek wrote:
Hi All,
I have started to work on a new feature[1] which will make it possible to edit the Blank template. The proposal is available on the feature page[2]
Any comments are more than welcome, Tomas
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1130174 [2]: http://www.ovirt.org/Features/Blank_to_Defaults
Well you can't just rename the blank template to "default". You would break any upgrade from 3.5. if you did. At least you could not run any pre 3.6. cluster level vms on this 3.6. engine.
it's not really that many changes in fact. existing VMs are not affected as on create VM the fields are being copied to the new VM db entry and the association to the Blank template is no longer needed/useful. Further edits of Default wouldn't affect existing VMs…so I think we can make it work for all cluster levels right away Thanks, michal
Is it intended to break compatibility in this release or not?
3.5 cluster level vms (e.g. new created vms) need afaik the "blank" template. how do you want to handle that?
could you instead add this "default" template just for cluster/dc level 3.6, so just "3.6" vms use it?
In general I think this is a much anticipated and needed feature, so I'm looking forward to the 3.6 release! :)
-- Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Michal Skrivanek" <michal.skrivanek@redhat.com> To: "Sven Kieske" <S.Kieske@mittwald.de> Cc: devel@ovirt.org Sent: Thursday, January 22, 2015 1:36:42 PM Subject: Re: [ovirt-devel] [engine-devel] Turn Blank template into defaults
On Jan 22, 2015, at 13:15 , Sven Kieske <S.Kieske@mittwald.de> wrote:
On 22/01/15 11:28, Tomas Jelinek wrote:
Hi All,
I have started to work on a new feature[1] which will make it possible to edit the Blank template. The proposal is available on the feature page[2]
Any comments are more than welcome, Tomas
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1130174 [2]: http://www.ovirt.org/Features/Blank_to_Defaults
Well you can't just rename the blank template to "default". You would break any upgrade from 3.5. if you did. At least you could not run any pre 3.6. cluster level vms on this 3.6. engine.
Why not? The VM is bound to the blank template ID, not name. There should not be any problem with this change.
it's not really that many changes in fact. existing VMs are not affected as on create VM the fields are being copied to the new VM db entry and the association to the Blank template is no longer needed/useful. Further edits of Default wouldn't affect existing VMs…so I think we can make it work for all cluster levels right away
Thanks, michal
Is it intended to break compatibility in this release or not?
3.5 cluster level vms (e.g. new created vms) need afaik the "blank" template. how do you want to handle that?
could you instead add this "default" template just for cluster/dc level 3.6, so just "3.6" vms use it?
In general I think this is a much anticipated and needed feature, so I'm looking forward to the 3.6 release! :)
-- Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (3)
-
Michal Skrivanek -
Sven Kieske -
Tomas Jelinek