Open Stack

On Jul 6, 2014, at 10:22 PM, Rafi Khardalian <rafi at metacloud.com> wrote:

> Hi All --
> 
> It seems as though it would be beneficial to use virDomainSave rather than virDomainManagedSave for suspending instances.  The primary benefit of doing so would be to locate the save files within the instance's dedicated directory.  As it stands suspend operations are utilizing ManagedSave, which places all save files in a single directory (/var/lib/libvirt/qemu/save by default on Ubuntu).  This is the only instance-specific state data which lives both outside the instance directory and the database.  Also, ManagedSave does not consider Libvirt's "save_image_format" directive and stores all saves as raw, rather than offering the various compression options available when DomainSave is used.
> 
> ManagedSave is certainly easier but offers less control than what I think is desired in this case.  Is there anything I'm missing?  If not, would folks be open to this change?

+1

Vish

> 
> Thanks,
> Rafi
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140707/93a39e45/attachment.pgp>