[Pulp-list] pulp ostree + mirroring

[Bryan Kearney]

On 10/30/2014 05:18 PM, Colin Walters wrote:
> Hi!
>
> It seems critical for the Atomic/OSTree model to support organization local mirrors.  In v2014.11, we include this commit:
> https://git.gnome.org/browse/ostree/commit/?id=bcf40b49023ec4cc3a7a6f832d311eac9319901e
>
> Which would allow a client like pulp to perform depth traversal of the repository - in general the goal is to support making a complete mirror, although there are still some remaining issues there like https://bugzilla.gnome.org/show_bug.cgi?id=739377
>
> An interesting question arises though around whether a complete traversal is *desired*.  It would likely need to be configurable.
>
> The default might depend on whether the cadence of the producer and consumer match.  If they do, then we might as well mirror the whole thing, because it'd be nearly equivalent to not doing so.
>
> If however, the producer is making 80+ releases a day (as e.g. gnome-continuous does), and the consumer only updates once a week, I doubt they'd want to download all ~2,240 trees.  (Interesting factoid though: gnome-continuous last time I did stats had 17,296 trees, but they took up just 153G).
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
Is there any notion of squash in ostree? I assume there is a case where 
I produce 80 builds a day and I want them published, there are others 
where I assume I would only want to publish 1 and combine there rest. It 
sounds like git squash. Anyone know Conary.. how did it address things 
like this?

-- bk