7:33 a.m.
Hello,
Our organization is running high number of linux machines and to save bandwidth and
resources, we've created private mirror to redirect all our machines via metalink to
it.
We sync data every 2 hours with quick-fedora-mirror and then run report_mirror to inform
upstream about our state. We only mirror part of the EPEL tree, could that be the reason,
why metalink is not returning our URL to our restricted ranges? If yes, how can we
override all that without mirroring entire EPEL tree?
Thanks
George Machitidze
Linux Consultant
JSC CURATIO
11:09 a.m.
On Sun, Jan 28, 2018 at 05:33:23PM +0400, admin(a)curatio.ge wrote:
Our organization is running high number of linux machines and to save
bandwidth and resources, we've created private mirror to redirect all our machines via
metalink to it.
We sync data every 2 hours with quick-fedora-mirror and then run report_mirror to inform
upstream about our state. We only mirror part of the EPEL tree, could that be the reason,
why metalink is not returning our URL to our restricted ranges? If yes, how can we
override all that without mirroring entire EPEL tree?
It should actually work. If you tell me the name of your mirrormanager
entry I can take a closer look.
Adrian
12:50 p.m.
Hi Adrian,
Thanks for response,
Account: curatio
Site name: Curatio
George Machitidze
Linux Consultant
JSC CURATIO
----- Original Message -----
From: "Adrian Reber" <adrian(a)lisas.de>
To: admin(a)curatio.ge
Cc: mirror-admin(a)lists.fedoraproject.org
Sent: Sunday, January 28, 2018 9:09:09 PM
Subject: Re: metalink not returning URL for private mirror
On Sun, Jan 28, 2018 at 05:33:23PM +0400, admin(a)curatio.ge wrote:
Our organization is running high number of linux machines and to save
bandwidth and resources, we've created private mirror to redirect all our machines via
metalink to it.
We sync data every 2 hours with quick-fedora-mirror and then run report_mirror to inform
upstream about our state. We only mirror part of the EPEL tree, could that be the reason,
why metalink is not returning our URL to our restricted ranges? If yes, how can we
override all that without mirroring entire EPEL tree?
It should actually work. If you tell me the name of your mirrormanager
entry I can take a closer look.
Adrian
4:05 p.m.
If I look at it right now it seems to work:
curl -s
"https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&ip=212.58.118.240"
| grep curatio
<url protocol="http" type="http" location="GE"
preference="100"
mm0:private="True">http://space.curatio.loc/repo/epel/7/x86_64/repodata/repomd.xml</url>
Do you still see the problem? Maybe it was a temporary problem?
Adrian
On Sun, Jan 28, 2018 at 10:50:38PM +0400, admin(a)curatio.ge wrote:
Hi Adrian,
Thanks for response,
Account: curatio
Site name: Curatio
George Machitidze
Linux Consultant
JSC CURATIO
----- Original Message -----
From: "Adrian Reber" <adrian(a)lisas.de>
To: admin(a)curatio.ge
Cc: mirror-admin(a)lists.fedoraproject.org
Sent: Sunday, January 28, 2018 9:09:09 PM
Subject: Re: metalink not returning URL for private mirror
On Sun, Jan 28, 2018 at 05:33:23PM +0400, admin(a)curatio.ge wrote:
> Our organization is running high number of linux machines and to save bandwidth and
resources, we've created private mirror to redirect all our machines via metalink to
it.
> We sync data every 2 hours with quick-fedora-mirror and then run report_mirror to
inform upstream about our state. We only mirror part of the EPEL tree, could that be the
reason, why metalink is not returning our URL to our restricted ranges? If yes, how can we
override all that without mirroring entire EPEL tree?
It should actually work. If you tell me the name of your mirrormanager
entry I can take a closer look.
Adrian
4:12 p.m.
Yes, it’s working now, I will monitor if problem will show up again
Thanks!
George Machitidze
Linux Consultant
JSC CURATIO
On 2018/01/29, at 2:05 AM, Adrian Reber <adrian(a)lisas.de>
wrote:
If I look at it right now it seems to work:
curl -s
"https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&ip=212.58.118.240"
| grep curatio
<url protocol="http" type="http" location="GE"
preference="100"
mm0:private="True">http://space.curatio.loc/repo/epel/7/x86_64/repodata/repomd.xml</url>
Do you still see the problem? Maybe it was a temporary problem?
Adrian
On Sun, Jan 28, 2018 at 10:50:38PM +0400, admin(a)curatio.ge wrote:
> Hi Adrian,
>
> Thanks for response,
>
> Account: curatio
> Site name: Curatio
>
> George Machitidze
> Linux Consultant
> JSC CURATIO
>
> ----- Original Message -----
> From: "Adrian Reber" <adrian(a)lisas.de>
> To: admin(a)curatio.ge
> Cc: mirror-admin(a)lists.fedoraproject.org
> Sent: Sunday, January 28, 2018 9:09:09 PM
> Subject: Re: metalink not returning URL for private mirror
>
> On Sun, Jan 28, 2018 at 05:33:23PM +0400, admin(a)curatio.ge wrote:
>> Our organization is running high number of linux machines and to save bandwidth
and resources, we've created private mirror to redirect all our machines via metalink
to it.
>> We sync data every 2 hours with quick-fedora-mirror and then run report_mirror to
inform upstream about our state. We only mirror part of the EPEL tree, could that be the
reason, why metalink is not returning our URL to our restricted ranges? If yes, how can we
override all that without mirroring entire EPEL tree?
>
> It should actually work. If you tell me the name of your mirrormanager
> entry I can take a closer look.
>
> Adrian
2285
days inactive
2285
days old
mirror-admin@lists.fedoraproject.org
4 comments
3 participants
participants (3)
-
admin＠curatio.ge -
Adrian Reber -
George Machitidze