 |
In a nutshell - Move the deb.roundr.devuan.org name server to something that can be automated, so apt-panopticon and Evilhams Prometheus instance can decide to add and remove IPs very quickly. It remains as a CNAME for deb.devuan.org. Somehow alerts are sent to this thing that removes DNS records when mirrors drop below "good enough for the RR", or adds them when they rise above that limit. The alerts could be some new output module I write for apt-panopticon, Nagios / Icinga using the existing plugin, or some alert thingy from Evilhams Prometheus instance. What "good enough" is can be tunable. To avoid nasty people trying to screw with us, the alert has to be cryptographically secure if being sent between computers. (The VPS owned by rrq I just setup apt-panopticon on to avoid "server running it gets ludicrous speed" I doubt is secure enough for this.) |
|
|
Think we will need to add a "DNS-RR" field to https://pkgmaster.devuan.org/mirror_list.txt, so we know which mirrors should be part of this automated to and fro. Done. |
|
|
[03:40:30] <bb|hcb> Next step (maybe) is to make that script to also generate more proper CC.deb.devuan.org resolvings, at least to keep the traffic at the same continent and spread the traffic on the mirrors instead on pkgmaster (where resources are quite limited at 250mbit/s) [03:43:10] <onefang> Luckily I already added the CountryCode field. [03:48:52] <bb|hcb> I was thinking about including the ipv4/ipv6 addresses in mirror_list.txt, so that resolving happens only at apt-panopticon, else with misconfigured resolvers both sides may use different views of the internet (not highly probable, though) [03:52:18] <bb|hcb> Also some clarification on the semantics of Active and DNSRR fields - Active should mean that the mirror is good to use and DNSRR should mean that the mirror is configured and properly serving deb.devuan.org AND that the admin agrees to include it there [03:52:23] <onefang> Then we would have to keep an eye on those and change them if needed. [03:53:26] <onefang> That was already my idea for the DNSRR field. [03:54:16] <onefang> So you are saying apt-panopticon updates https://pkgmaster.devuan.org/mirror_list.txt ? [03:55:12] <bb|hcb> Isn't it? That was my undestanding [03:56:41] <onefang> There's a master file on pkgmaster that I update manually, and a cron job that runs once an hour that does that currently. [03:57:57] <onefang> /home/mirror-admin/mirror_list.txt [04:39:11] <bb|hcb> Oops, I was thinking that this is auto updated... [04:42:51] <bb|hcb> And about CC RR, one more field will be needed - DNSRRCC, because not all mirrors may want to be included or configured to serve the content... [10:53:27] <bb|hcb> onefang: What are your thoughts about automatic update of the Active field in mirror_list.txt? Do you need help for that? [10:55:10] <bb|hcb> Obviously maintaining some form of the mirror admin intent in DNSRR and/or DNSRRCC should happen manually [14:38:35] <onefang> bb|hcb: That's one way to deal with things. I have long planned to automatically update the DNS-RR based on the three apt-panopticons voting on which mirrors are up. [14:39:18] <onefang> If you are now using / planning on using mirror_list.txt to change DNS-RR, that'll work. |
|
|
IMPORTANT - if something like the version number of base-files that we are testing for goes away, coz it got updated, than we shouldn't disable ALL the mirrors coz they all failed that test. |
- Anonymous
