On Tue, Dec 04 2018, Jonathan Tan wrote:
I meant to follow-up after Git Merge, but didn't remember until this
thread was bumped.
But some things I'd like to clarify / am concerned about...
> +when the server sends the packfile, it MAY send a `packfile-uris` section
> +directly before the `packfile` section (right after `wanted-refs` if it is
> +sent) containing HTTP(S) URIs. See protocol-v2.txt for the documentation of
> +this section.
> +
> +Clients then should understand that the returned packfile could be incomplete,
> +and that it needs to download all the given URIs before the fetch or clone is
> +complete. Each URI should point to a Git packfile (which may be a thin pack and
> +which may contain offset deltas).
> [...]
> +This is the implementation: a feature, marked experimental, that allows the
> +server to be configured by one or more `uploadpack.blobPackfileUri=<sha1>
> +<uri>` entries. Whenever the list of objects to be sent is assembled, a blob
> +with the given sha1 can be replaced by the given URI. This allows, for example,
> +servers to delegate serving of large blobs to CDNs.
Okey, so the server advertisement is not just "<urls>" but <oid><url>
pairs. More on this later...
> +While fetching, the client needs to remember the list of URIs and cannot
> +declare that the fetch is complete until all URIs have been downloaded as
> +packfiles.
And this. I don't quite understand this well enough, but maybe it helps
if I talk about what I'd expect out of CDN offloading. It comes down to
three things:
* The server should be able to point to some "seed" packfiles *without*
necessarily knowing what OIDs are in it, or have to tell the client.
* The client should be able to just blindly get this data ("I guess
this is where most of it is"), unpack it, see what OIDs it has, and
*then* without initiating a new connection continue a want/have
dialog.
This effectively "bootstraps" a "clone" mid way into an arbitrary
"fetch".
* There should be no requirement that a client successfully downloads
the advertised CDNs, for fault handling (also discussed in
https://public-inbox.org/git/87lg2b6gg0.fsf@xxxxxxxxxxxxxxxxxxx/)
More concretely, I'd like to have a setup where a server can just dumbly
point to some URL that probably has most of the data, without having any
idea what OIDs are in it. So that e.g. some machine entirely
disconnected from the server (and with just a regular clone) can
continually generating an up-to-date-enough packfile.
I don't see how this is compatible with the server needing to send a
bunch of "<oid> <url>" lines, or why a client "cannot declare that the
fetch is complete until all URIs have been downloaded as
packfiles". Can't it fall back on the normal dialog?
Other thoughts:
* If there isn't such a close coordination between git server & CDN, is
there a case for having pack *.idx files on the CDN, so clients can
inspect them to see if they'd like to download the full referenced
pack?
* Without the server needing to know enough about the packs to
advertise "<oid> <url>" is there a way to e.g. advertise 4x packs to
clients:
big.pack, last-month.pack, last-week.pack, last-day.pack
Or some other optimistic negotiation where clients, even ones just
doing regular fetches, can seek to get more up-to-date with one of
the more recent packs before doing the first fetch in 3 days?
In the past I'd toyed with creating a similar "not quite CDN" setup
using git-bundle.
