[Engine-devel] [Engine-Devel] OvfDataUpdater

[Michael Kublin]

----- Original Message -----
> From: "Liron Aravot" <laravot at redhat.com>
> To: engine-devel at ovirt.org
> Sent: Monday, November 19, 2012 2:03:57 PM
> Subject: [Engine-devel] [Engine-Devel] OvfDataUpdater
> 
> starting a new discussion thread.
> 
> ----- Original Message -----
> > From: "Mike Kolesnik" <mkolesni at redhat.com>
> > To: "Liron Aravot" <laravot at redhat.com>
> > Sent: Monday, November 19, 2012 12:42:10 PM
> > Subject: Re: [Engine-devel]  OvfAutoUpdater
> > 
> > I think 'version' is a more standard term for the column names.
> > 
> > Also in:  4. If succesfull - for each vm update the ovf_generation
> > to
> > equal the db_generation.
> > I think you mean that the update should be to the entity version
> > you
> > initially selected.
> > 
1. I think should be version = version +1;
2. Now the quartz is automatic process, updateVmInSpm it is spm operation -it means it can trigger a reconstruct
and spm election. 
3. How your solution is handling a case of hotPlug/hotUnplug/remove/add of vm disks. vm_static is not usually updated.
4. Reconstruct/Recovery - updateVmInSpm should be called on all vms, no matter if they were updated.

> > Regards,
> > Mike
> > 
> > ----- Original Message -----
> > > http://wiki.ovirt.org/wiki/Feature/OvfAutoUpdater
> > > 
> > > Hi all, i'll be glad if you could review the wiki page of
> > > OvfAutoUpdater, if you have any suggestions or ideas please let
> > > me
> > > know.
> > > 
> > > http://wiki.ovirt.org/wiki/Feature/OvfAutoUpdater
> > > 
> > > short preview from the wiki:
> > > vm/template configurations (including disks info) are stored on
> > > the
> > > master storage domain for backup purposes, import/export and also
> > > to
> > > provide the abillity to run VMs without having a running
> > > engine/db.
> > > Currently ovf update is done synchronously when performing
> > > various
> > > operations on vms/templates - update, save, adding/removing a
> > > disk,
> > > etc. What's more, currently updating the ovf (updateVM vdsm call)
> > > is
> > > usually done within a transcation.
> > > 
> > > The idea behined OvfAutoUpdater is to perform batch ovf update
> > > operations that aggregate all outstanding updates per data
> > > center.
> > > These updates will be done in specifed time intervals which will
> > > reduce XML-RPC calls and will enable the removal of this
> > > syncronous
> > > vdsm call from all over the code.
> > > 
> > > Thanks,
> > > Liron Aravot.
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > > 
> > 
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>