Hi Anssi,

Our mirror is sync'd and ready to be approved.

The information repeated below.

Eric

HTTP: http://mirror.genesishosting.com/centos/

Sync schedule: Every 6 hrs Bandwidth: 1Gbps Location: U.S. - Chicago, IL Sponsor: Genesis Hosting Sponsor URL: https://genesishosting.com/ IPv4 address to authorize: 104.36.110.9

Email contact: mirrors@genesishosting.com Mirroring AltArch: yes - HTTP: http://mirror.genesishosting.com/centos-altarch/

Thank you Anssi! We changed the mirror sync to the msync URLs shortly after your message.

However, a recent check shows that the mirror list being returned for: curl "http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os"

does not include our mirror.

Note that these two repo lists do include our mirror: curl "http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates" curl "http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras"

Is there something required of us to be included on the "os" list?

Thanks!

Eric

-----Original Message----- From: CentOS-mirror [mailto:centos-mirror-bounces@centos.org] On

Behalf

Of Anssi Johansson Sent: Friday, November 09, 2018 6:05 AM To: centos-mirror@centos.org Subject: Re: [CentOS-mirror] CentOS mirror

Eric K. Miller kirjoitti 8.11.2018 klo 22.49:

...

Hi Anssi,

Our mirror is sync'd and ready to be approved.

The information repeated below.

Eric

HTTP: http://mirror.genesishosting.com/centos/

Sync schedule: Every 6 hrs Bandwidth: 1Gbps Location: U.S. - Chicago, IL Sponsor: Genesis Hosting Sponsor URL: https://genesishosting.com/ IPv4 address to authorize: 104.36.110.9

Email contact: mirrors@genesishosting.com Mirroring AltArch: yes - HTTP: http://mirror.genesishosting.com/centos-altarch/

Thanks, added! You can now rsync from rsync://us-msync.centos.org/CentOS/ and rsync://us- msync.centos.org/altarch/

---

CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

Yes, the list includes only 10 entries. There are 11 mirrors in Illinois, so there is a smallish chance that sometimes your mirror doesn't get included in the 10 selected mirrors. The mirrors are picked randomly, and this process is repeated every 10 minutes or so.

Your mirror is not being neglected, ihere was just a bit of bad luck this time :)

Eric K. Miller kirjoitti 10.11.2018 klo 13.21:

So it looks like shortly after I sent this message, our mirror showed up in the "os" list. It appears that the list changed. It also looks like only 10 mirrors are chosen in this list. Is there something on your end that limits the list based on geography and some other factors?

Thanks!

Eric

...

-----Original Message----- From: CentOS-mirror [mailto:centos-mirror-bounces@centos.org] On

Behalf

...

Of Eric K. Miller Sent: Saturday, November 10, 2018 5:17 AM To: Mailing list for CentOS mirrors. Subject: Re: [CentOS-mirror] CentOS mirror

Thank you Anssi! We changed the mirror sync to the msync URLs shortly after your message.

However, a recent check shows that the mirror list being returned for: curl "http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os"

does not include our mirror.

Note that these two repo lists do include our mirror: curl

"http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates"

...

curl "http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras"

Is there something required of us to be included on the "os" list?

Thanks!

Eric

---

CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

Eric,

There's a couple options.

One is to change the repo files on all of your hosts, but that's annoying and doesn't scale well.

There's a second that probably highly unsupported, but it's worked well for me for many years. It relies on playing games with DNS.

1) You have to make your clients believe that mirrorlist.centos.org is on a webserver you control. I did this by creating a DNS zone for mirrorlist.centos.org and having it resolve to one of my webservers.

2) The webserver you point them to needs to reply with something that looks like the list returned by the real mirrorlist. I created /index.cgi (and added index.cgi to the DirectoryIndex and enabled CGI execution for .cgi files). The contents of index.cgi are:

----- BEGIN index.cgi ----- #!/usr/bin/perl use strict; use warnings; use CGI qw (param);

my $baseurl = 'http://mirror.chpc.utah.edu/pub/centos/';

print "Content-type: text/plain\n\n";

print $baseurl, param('release'), '/', param('repo'), '/', param('arch'), '/', "\n" ----- END index.cgi -----

This makes every client that uses my DNS server use my CentOS mirror. One advantage is that it requires no client configuration. To stop it, I remove the DNS override from my name server. To continue, I put the override back. One disadvantage is that each client only gets one mirror, so if there's something wrong with my mirror, they don't have any others to try.

As I said before, probably highly not-recommended, but it seems to have worked OK for me.

Thanks, DR

Thanks for the tip about repo length! I had not considered providing the packages from a second repo, only repointing the base repo.

DR

-- David Richardson <david.richardson@utah.edumailto:david.richardson@utah.edu> Center for High Performance Computing University of Utah

On Nov 12, 2018, at 2:47 PM, Anssi Johansson <avij@centosproject.orgmailto:avij@centosproject.org> wrote:

The chances for your mirror to be included in the 10 randomly picked mirrors is around 10/11 (91%) which does not sound that bad to me. The fastestmirror yum plugin should then theoretically be able to pick your mirror from that list of 10 mirrors, but if it fails, you will end up using some other mirror from Illinois. The fastestmirror plugin is suitable for determining if a mirror is in the same country or not, but its precision might not be sufficient for determining the absolutely fastest mirror if the candidate mirrors are very close to you. Note that the fastestmirror plugin does not measure bandwidth, but DNS resolution time and the time it takes to establish a TCP connection to each mirror. There can be small fluctuations in these measurements.

One way to guarantee your mirror's inclusion in the top 10 (at least at this moment) would be to make your mirror available over IPv6, and make the mirrorlist.centos.orghttp://mirrorlist.centos.org request from an IPv6-enabled host. mirrorlist.centos.orghttp://mirrorlist.centos.org returns only IPv6-capable mirrors if accessed via IPv6. There are currently five IPv6-enabled mirrors in Illinois.

Some people have suggested "overriding" mirrorlist.centos.orghttp://mirrorlist.centos.org, but I'm not a fan of that approach. That would break if mirrorlist.centos.orghttp://mirrorlist.centos.org switched to using https, or if centos.orghttp://centos.org started using DNSSEC. My own approach for my own unpublished private mirror is to drop a .repo file like this in /etc/yum.repos.d:

--- [b] name=CentOS-$releasever - Base baseurl=http://mirror.example.com/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[u] name=CentOS-$releasever - Updates baseurl=http://mirror.example.com/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[e] name=CentOS-$releasever - Extras baseurl=http://mirror.example.com/centos/$releasever/extras/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 ---

The trick here is that the default CentOS repositories would also remain active. When yum sees that the update is available from both the "updates" repository and the "u" repository, yum will download the package from the repo whose name is the shortest. This way it is not particularly harmful if the local mirror is not up-to-date for some reason, the other packages that are not on the local mirror will get downloaded from other mirrors instead. Obviously this does not meet the "default yum settings" criteria, but this should still be easy enough to accomplish using some sort of configuration management tool.

Eric K. Miller kirjoitti 10.11.2018 klo 13.36: Ah - makes sense. I was hoping that our mirror would be selected for our own systems every time, since the latency is quite a bit lower than other mirrors (1ms to 2ms, but still... would be nice to pull from our own repositories with default yum settings). Is there anything we can do? Thanks for the quick response! Eric -----Original Message----- From: CentOS-mirror [mailto:centos-mirror-bounces@centos.org] On Behalf Of Anssi Johansson Sent: Saturday, November 10, 2018 5:33 AM To: centos-mirror@centos.orgmailto:centos-mirror@centos.org Subject: Re: [CentOS-mirror] CentOS mirror

Yes, the list includes only 10 entries. There are 11 mirrors in Illinois, so there is a smallish chance that sometimes your mirror doesn't get included in the 10 selected mirrors. The mirrors are picked randomly, and this process is repeated every 10 minutes or so.

Your mirror is not being neglected, ihere was just a bit of bad luck this time :) _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.orgmailto:CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror

_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.orgmailto:CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror