Hi all,

Last evening, the old sponsor where cvs/git/git.overlays was hosted
turned off the old servers, earlier than I expected.

With two notable exceptions listed below, almost everything should be
how it should be, so you can continue as before.

The new SSH keys, in case you still didn't have them:
On Mon, Jun 30, 2014 at 10:26:52PM +0000, Robin H. Johnson wrote:
> 1024 5f:c3:fe:9a:ac:a7:99:f4:d3:c1:93:4c:52:87:74:28 (DSA)
> 256  aa:6a:e4:74:1d:73:d2:5a:9f:45:9f:18:55:81:c9:9a (ECDSA)
> 256  1c:2e:99:7d:c7:f0:bc:3b:a9:fb:d0:3e:2c:2a:79:ba (ED25519)
> 2048 24:3b:2d:3b:47:ca:7e:62:48:97:49:6a:f5:ad:66:88 (RSA)

1.
Overlays missing commits since 2014/07/22 02:49 UTC
---------------------------------------------------
So last time overlays had an outage, infra promised to look into a git
mirroring setup, so when this forced migration was announced, I started
to implement a very rough version of mirroring for both the main cvs/git
repos, as well as the overlays repos.

It worked on the primary repos, but after some initial runs it failed on
all of the git.overlays repos at Jul 22 02:49 UTC. I've been busy with
real life, and I unfortunately didn't notice it until too late.

As a direct result, any commits pushed to git.overlays repos after
2014/07/22 22 02:49 UTC, are missing. If you have them locally, all you
need to do is 'git push' for all of your branches, and they'll be
restored.

2.
gitweb/cgit offline, anongit rate-limited
-----------------------------------------
One of the plans was to merge the hosting of git.gentoo.org and
git.overlays.gentoo.org into a single large Gitolite deployment, in
preparation for the Git migration of gentoo-x86.

The gotcha is that while we want all of the write traffic to be
consolidated, we want to be able to scale the readonly capacity easily
(without the budget or sharding that GitHub has).

It isn't a 100% solved problem yet (one of the reasons that I hadn't
flipped stuff over yet). There is also a lot more read-only Git traffic
than I expected (enough to kill some systems); so I'm NOT enabling a web
server on the box that runs the readwrite traffic yet.

The leading solution I have, that allows the most flexibility, is simply
splitting at the hostname:
http://gitweb.gentoo.org/$REPO
git://readonly.git.gentoo.org/$REPO
git://ro.git.gentoo.org/$REPO
git+ssh://g...@readwrite.git.gentoo.org/$REPO
git+ssh://g...@rw.git.gentoo.org/$REPO

This also lets us trivially distribute readonly mirrors distributed
around the world, which would hugely improve performance when the Git
migration is done.

As a migration plan, git.gentoo.org would continue to host R+RW git for
a month.

Any concerns or alternative ideas should be proposed on the gentoo-dev
lists.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robb...@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85

Reply via email to