[CentOS-devel] setting up an emergency update route

[Fabian Arrotin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/02/15 15:56, Nux! wrote:
> How about a variation on A: - ask some of the main mirrors for push
> access, put those in order and make a new [centos-security] repo
> with a mirrorlist pointing just at them.
> 
> Lucian
> 

well, asking "push access" can be problematic for various reasons (and
I clearly would understand why they'd all answer "no").
What I was thinking about (and discussing that at Fosdem with some
other distributions Infra team members) was something around something
light (like mqtt) or something light that can be used a simple message
queue and we'd publish, and all external mirrors could then just
subscribe and take action.

Without going that far, a simple file that we'd drop at a specific
place on the msync node that can be checked/parsed by external mirrors
in a frequent cron job running on those nodes (we can even just have a
simple bash example, so nothing really to install as a requirement for
those 580+ external mirrors)

The interesting thing is that we can also mix all current proposals
all together too (so an "emergency updates" repo, using only
centos.org nodes, a different crawler process running faster and only
dedicated for a specific release/updates and doing that in loop, and
that external trigger running on external mirrors

- -- 

Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlTQ5K4ACgkQnVkHo1a+xU4VvgCdFdWdqoH3Xv1CQnpaH0NoVJ8o
38wAn3J7wb3Mr9R1AI37/owG5pKR+nDR
=rA9B
-----END PGP SIGNATURE-----