[Openstack] How do I stop image-create from using /tmp?

Boris Filippov bfilippov at griddynamics.com
Mon Jul 2 20:49:57 UTC 2012


2012/7/2 Daniel P. Berrange <berrange at redhat.com>:
> On Mon, Jul 02, 2012 at 10:24:02AM -0700, Matt Joyce wrote:
>> I like the idea of making this a flagfile option.
>
> In the particular case of the qemu-img command described
> in earlier in this thread, I'm not convinced we need a
> new option. Instead of using /tmp when extracting a snapshot
> from an existing disk image, it could just use the path
> where the source image already resides. ie the existing
> FLAGS.instances_path directory, which can be assumed to
> be a suitably large persistent data store.
>
> Other uses of temporary files should be analysed ona case
> by case basis to figure out a suitable storage location.
> This might perhaps identify a need for a generic temp
> file location for nova, such as /var/run/nova/ or
> /var/cache/nova or both (depending on use case).
>
> Regards,
> Daniel
> --
> |: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
> |: http://libvirt.org              -o-             http://virt-manager.org :|
> |: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
> |: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

Sure, we can place snapshots inside instances_path. At least, just
separate them from instances and place them in
%instances_path%/snapshots.




More information about the Openstack mailing list