From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D9B99138334 for ; Sun, 16 Dec 2018 04:16:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2BE38E09C1; Sun, 16 Dec 2018 04:16:01 +0000 (UTC) Received: from mail-ed1-f67.google.com (mail-ed1-f67.google.com [209.85.208.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id CCA55E09AD for ; Sun, 16 Dec 2018 04:16:00 +0000 (UTC) Received: by mail-ed1-f67.google.com with SMTP id f9so8028196eds.10 for ; Sat, 15 Dec 2018 20:16:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tvup5nKADthdNLL4JyEogOU4hJ9Z3vIlb8gCX1ZqC6E=; b=QQ1KBwj0qPiE8gUs/dpSJDu2PE9lSrby5/9bLqXAUlyIrsL5jnj45EjpFlQbqzYmQ3 ajVeWEorRejuFr0QzAsBLIr/7luBYAMt7b365ip+mAVFACSUuGfme4ebIEPgquqlLImm DvII0eoF9s+FAnJldKmDG0FiVWJNb8JdCzrrbpiz675l/70DeHRwYgm5TGI/x/ASeRVV 9hfacJm/jdSGBKEwwORCY9GTlZf+O4goInL+J+Fd4Ch0g3JbMS3uaSarjBXalXBFa/hQ 2MiLlpvn68RElsLfEKHulAUrz3UyofDdHZFOJ6kaO7XkC/bGNUsW8P4l0iflAxD/Jvld dLbA== X-Gm-Message-State: AA+aEWa0SBer9Dd3mfjJDuguiwUoNMx8/cl0ppFmkws42XQhu01uj36n mpS7r4RlRCf1rhRLp49qPR8GDBgSUGBvXHRdfwYAkAyWlnyRuw== X-Google-Smtp-Source: AFSGD/W53II+yDj9rFWcbR48Q7XC0I/YJjybC6zKSPYHgfKLsRoas69I/TsobEM05BaSaltkaCZO/QqIc/TMn0mlQlg= X-Received: by 2002:a17:906:495:: with SMTP id f21-v6mr6474042eja.95.1544933758841; Sat, 15 Dec 2018 20:15:58 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 From: Alec Warner Date: Sat, 15 Dec 2018 23:15:47 -0500 Message-ID: Subject: [gentoo-project] RFC: Dropping rsync as a tree distribution method To: gentoo-project Content-Type: multipart/alternative; boundary="000000000000e5d10b057d1bebcd" X-Archives-Salt: 32a4edca-7117-434f-b299-0ad3d74b3b15 X-Archives-Hash: 65a57ed8027b9bb606c01c0507db53f1 --000000000000e5d10b057d1bebcd Content-Type: text/plain; charset="UTF-8" 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. --000000000000e5d10b057d1bebcd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I am currently emb= arking 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 thi= nk 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 gi= t tree directly. To that end, I'm looking for blockers as to why variou= s 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 f= or 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 touch= ing.
[1] Rich talked about some downsides earlier at=C2=A0https://lwn.net/Articles/759539/;= but while these are challenges (some fixable) they are not necessarily blo= ckers.
--000000000000e5d10b057d1bebcd--