Re: [gentoo-project] RFC: Dropping rsync as a tree distribution method

[Brian Evans <grknight@gentoo.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1540 bytes --]

On 12/15/2018 11:15 PM, Alec Warner wrote:
> Hi,
> 
> I am currently embarking on a plan to redo our existing rsync[0] mirror
> network. The current network has aged a bit. Its likely too large and is
> under-maintained. I think in the ideal case we would instead pivot this
> project to scaling out our git mirror capabilities and slowly migrate
> all consumers to pulling the git tree directly. To that end, I'm looking
> for blockers as to why various customers cannot switch to pulling the
> gentoo ebuild repository from git[1] instead of rsync.
> 
> So for example:
> 
> - bandwidth concerns (preferably with documentation / data.)
> - Firewall concerns
> - CPU concerns (e.g. rsync is great for tiny systems?)
> - Disk usage for git vs rsync
> - Other things i have not thought of.
> 
> -A
> 
> [0] This excludes emerge-webrsync; which I don't plan on touching.
> [1] Rich talked about some downsides earlier
> at https://lwn.net/Articles/759539/; but while these are challenges
> (some fixable) they are not necessarily blockers.

I personally would be sad to see rsync go as I use the git developer
tree as my main repository on 2 machines. This is so I can develop and
update from the single source.  These have no news or md5-cache and it
can be painful to generate metadata on one of them.

I rely on scripts to pull down the rsync metadata to expedite this
process. eg. rsync <host>/gentoo-portage/metadata/md5-cache/.  Git has
no easy sub-tree download equivalent that I know of.

Brian


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]