DescriptionMichal Skrivanek
2014-03-04 11:16:21 UTC
+++ This bug was initially created as a clone of Bug #922377 +++
Description of problem:
It's quite inconvenient not to be able to edit all VM properties anytime. The old way of being to able to edit the VM properties anytime and applying some of them on VM shutdown is the best behaviour from administrator POV.
The only thing that may be missing is a note to user (admin) that the changes will be applied later.
Expected results:
update the VM properties in the database and the next time the VM is run, use them
Additional info:
--- Additional comment from Omer Frenkel on 2013-06-19 16:00:34 CEST ---
some more details on what is planned, no patches available yet:
when vm is run, new snapshot will be taken, for configutation only,
this will be special "running snapshot".
when vm is edited while running, changes will be saved to the snapshot.
this way when frontend get a vm object from db, it always reflect the 'real' state of the vm.
(general subtab of vm in ui, for example).
when vm goes down, all information from the snapshot will be saved to the vm table, to be used on next run.
the "next run configuration" will be available when querying the snapshot, as querying any other snapshot.