[Bug 1234649] Review Request: testcloud - a small tool for running cloud images locally

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1234649



--- Comment #8 from Mike Ruckman <mruckman@xxxxxxxxxx> ---
(In reply to Michael Schwendt (Fedora Packager Sponsors Group) from comment #6)
> > Getting permissions ironed out for this has been a pain so far - 
> > so I welcome any ideas :) 
> 
> > What's the best way to solve this? 
> 
> More elegant, more ordinary and more expected would be to set up a local
> tree in user's $HOME and to work within that space. What else have you tried
> that hasn't worked? It seems simplification has gone too far, if users
> operate in a world-writable directory below /var/lib.

We've tried to put this directory tree in $HOME, but libvirt doesn't play well
with data in a home directory, since it has to own all the images it works
with. Libvirt already keeps it's images in /var/lib - so it seemed a logical
place to put them in this case. In the case of the permissions, the user
running the script needs to have write access to that directory in order to
download images for libvirt to use.

We're currently revisiting this to see if there's a viable approach for our use
case.

(In reply to Kamil Páral from comment #7)
> Out of curiosity, why is /var/lib/testcloud/cache used for cache dir instead
> of /var/cache/testcloud ? If I'm running out of space and I want to delete
> some caches, the latter location is expected and probably the first place
> where the user will look for such files.

I suppose the name "cache" is a bit misleading in a system context. Originally,
testcloud downloaded the image for your instance each time you launched an
instance. This made everything take a lot longer to run, wasted bandwidth and
disk space. So I started to cache the images, and use them as backing stores
for instances; saving disk space and bandwidth.

In your case, if you were to delete images from what is now
/var/lib/testcloud/cache it would break any instances using those as a backing
store. I've opened a ticket in phab [0] to make the name change on that
directory to better communicate what it contains.

[0] https://phab.qadevel.cloud.fedoraproject.org/T521

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review




[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]