* Michal Pryc <[EMAIL PROTECTED]> [2008-08-19 11:13]: > [EMAIL PROTECTED] wrote: > >> Moreover we could provide zfs snapshot not of the repository but > >> "/var/pkg/download/" directory with most of the files for updates and > >> if someone had other application installed only those bits would be > >> downloaded, so there would be much less network traffic. > > > > Dan and I have talked about something like this for Zones, since it > > would be ideal to use the global zone's content cache to populate other > > zones, where appropriate. Neither one of us has had much time to do any > > work on this, since we've both been busy with other tasks. > > Having clone of the full repository is fine, but it in some cases just > too big and takes a lot of time to simply download few packages. (Not sure how you got to "full repository" from the previous paragraph.)
> Let's say that some customer or admin wan't to set up per-site download > cache folder so every user will benefit using this shared folder. Once > any user will download one/few applications (of course specified > version) then the next user will probably download much less data from > the Internet (pkg repository). > > Of course there is a problem what happens when two people are > downloading the same file at the same time, but this is also the problem > that should be solved (If it is not yet??) when two people are trying to > install the same package on the same machine at the same time. > > > When we last discussed this, we realized that we need to implement some > > kind of cache maintenance policy. (How long do things stay in here, > > when should we remove them, etc.) We also wanted to figure out where > > the download cache should live, so that we can always find it. One idea > > was to have a separate ZFS filesystem, similar to your idea above. > > Right, the policy could be a tricky part. > > For the location IMHO separate ZFS filesystem would be the best > solution, but with possible overriding this value using env variable. > Without big effort it would allow things like easy sharing between users > (zfs set sharenfs/sharesmb). I believe what you're asking for will be implemented as a lazy caching option to pkg.depotd, where it can be used as a basis for a number of software distribution flows. That is, although we could do tricks with the download cache, I think there's some consensus that an actively managed cache is more versatile. The separate filesystem idea is interesting, for both cases. - Stephen -- [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
