Migrate the VM then migrate the logs for that VM. Or use some sort of central logging system/distributed database. A distributed NoSQL database seems like a good place to store the task logs, each task can simply be a document.
Three ways to deal with task logs when a VM is deleted: a) never reuse a VMID or b) Delete all task logs for that VM when it is deleted or c)generate a GUID on VM creation, store GUID in the VM conf file. Include GUID as part of the log index eg <VMID>+<GUID> If VM is deleted and VMID reused, the tasks with the old GUID would not be displayed for the same VMID with new GUID On Thu, Oct 2, 2014 at 3:18 PM, Dietmar Maurer <diet...@proxmox.com> wrote: >> I also like the rsync logs on migration. The only missing part is HA >> migration here. >> Can i ignore this one? > > So you would also need to sync the log on VM start. But from which node ?? > >> What do you think regarding deletion of VM? > > no opinion > > _______________________________________________ > pve-devel mailing list > pve-devel@pve.proxmox.com > http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel