5:53 p.m.
"{ftp,www}.muug.mb.ca" is being transitioned to
"{ftp,www,(null)}.muug.ca", along with some new email addresses, etc.
The old hostnames will remain valid throughout, but we're setting up the
new mirror from scratch and will rationalize ACLs etc when we're done.
- Location: Winnipeg, Manitoba, Canada
- IP address: currently 198.51.75.34 / 2620:42:c000:1::34,
- Bandwidth: 100Mbps IPv4 commercial transit, 1Gbps IPv6 commercial
transit, 1Gbps to MBIX-and-connected-members
The IP address and bandwidth situation will both be changing in January,
as a local ISP is willing to host it at much higher bandwidth (10Gig,
unlimited, dual-stack), but we have enough bandwidth to start
pre-filling the mirror right away.
One question: on
https://fedoraproject.org/wiki/Infrastructure/Mirroring, the suggested
rsync module is "fedora-buffet0" and/or "fedora-enchilada0" but those
don't seem to exist on any of the mirror servers, not even the two
master servers. What's up with that?
In any case, we're currently going to mirror ::fedora,
::fedora-secondary and ::fedora-epel.
--
-Adam Thompson
athompso(a)athompso.net
Cell: +1 204 291-7950
Fax: +1 204 489-6515
12:09 p.m.
On Sun, Dec 21, 2014 at 05:53:51PM -0600, MUUG Mirror Manager wrote:
"{ftp,www}.muug.mb.ca" is being transitioned to
"{ftp,www,(null)}.muug.ca",
along with some new email addresses, etc.
The old hostnames will remain valid throughout, but we're setting up the new
mirror from scratch and will rationalize ACLs etc when we're done.
- Location: Winnipeg, Manitoba, Canada
- IP address: currently 198.51.75.34 / 2620:42:c000:1::34,
- Bandwidth: 100Mbps IPv4 commercial transit, 1Gbps IPv6 commercial transit,
1Gbps to MBIX-and-connected-members
The IP address and bandwidth situation will both be changing in January, as
a local ISP is willing to host it at much higher bandwidth (10Gig,
unlimited, dual-stack), but we have enough bandwidth to start pre-filling
the mirror right away.
Thanks for supporting Fedora. I see your mirror has already been added
to MirrorManager and so far everything looks correct. You should already
see clients being redirected to your mirror
One question: on
https://fedoraproject.org/wiki/Infrastructure/Mirroring,
the suggested rsync module is "fedora-buffet0" and/or
"fedora-enchilada0"
but those don't seem to exist on any of the mirror servers, not even the two
master servers. What's up with that?
This is for the tier 1 mirrors. To reduce the load on the master mirror
we are trying to get some tiering in place. If you could sync from a
close tier 1 mirror that would be great.
In any case, we're currently going to mirror ::fedora,
::fedora-secondary
and ::fedora-epel.
In your MirrorManager entry I see "Fedora Linux" and "Fedora EPEL". I
do
not see "Fedora Secondary Arches" but instead "Fedora Archive" (with
the
wrong content). So something in this area does not seem 100% correct.
If you have further questions do not hesitate to ask and thanks again
for your support.
Adrian
12:43 p.m.
On 14-12-22 12:09 PM, Adrian Reber wrote:
Thanks for supporting Fedora. I see your mirror has already been
added
to MirrorManager and so far everything looks correct. You should already
see clients being redirected to your mirror
Oh, I see I misunderstood the meaning of the user_active flag :). Oh,
well, no harm so far.
> One question: on
https://fedoraproject.org/wiki/Infrastructure/Mirroring,
> the suggested rsync module is "fedora-buffet0" and/or
"fedora-enchilada0"
> but those don't seem to exist on any of the mirror servers, not even the two
> master servers. What's up with that?
This is for the tier 1 mirrors. To reduce the load on the master mirror
we are trying to get some tiering in place. If you could sync from a
close tier 1 mirror that would be great.
As of January, we'll have not only the disk space but also the bandwidth
(10G) to be a tier-1 mirror. I don't think this server & disk
combination can actually push 10G, but we've already tested it up to 4G.
> In any case, we're currently going to mirror ::fedora,
::fedora-secondary
> and ::fedora-epel.
In your MirrorManager entry I see "Fedora Linux" and "Fedora EPEL". I
do
not see "Fedora Secondary Arches" but instead "Fedora Archive" (with
the
wrong content). So something in this area does not seem 100% correct.
I'm not sure what problem you're seeing...
In the MirrorManager online web app, I don't have any categories added
at all yet... correction, that's now fixed and I've added Fedora Linux,
Fedora EPEL and Fedora Secondary with matching URLs.
The mirrormanager-client config file appears to be correct.
The content appears to be correct, or at least, the top few levels match
what's on dl.fedoraproject.org. (I'm pulling from
mirrors.us.kernel.org, since my IPv6 connection is way faster than IPv4
right now.)
Also, re Peer ASNs, is there any way to let me manage my own list? As a
board member of MBIX, and a colleague of Les (at Les.net, the future
hoster) I'm aware of what ASNs connect here via private peering and via
the local IX. Right now, I count 12 ASNs being learned from the IX's
route servers.
If there's some reasonable way to automate the creation of site-local
netblocks, I could do it that way, too... there's 94 netblocks
(excluding Hurricane Electric, who peers here too) involved.
-Adam Thompson
athompso(a)athompso.net
1:06 p.m.
On Mon, Dec 22, 2014 at 12:43:15PM -0600, MUUG Mirror Manager wrote:
>>In any case, we're currently going to mirror ::fedora,
::fedora-secondary
>>and ::fedora-epel.
>
>In your MirrorManager entry I see "Fedora Linux" and "Fedora
EPEL". I do
>not see "Fedora Secondary Arches" but instead "Fedora Archive"
(with the
>wrong content). So something in this area does not seem 100% correct.
I'm not sure what problem you're seeing...
In the MirrorManager online web app, I don't have any categories added at
all yet... correction, that's now fixed and I've added Fedora Linux, Fedora
EPEL and Fedora Secondary with matching URLs.
I was confused by the different muug entries. I was looking at the old
entry. If you add rsync URLs the crawler can scan the state of your
mirror much faster.
The mirrormanager-client config file appears to be correct.
The content appears to be correct, or at least, the top few levels match
what's on dl.fedoraproject.org. (I'm pulling from mirrors.us.kernel.org,
since my IPv6 connection is way faster than IPv4 right now.)
Also, re Peer ASNs, is there any way to let me manage my own list? As a
board member of MBIX, and a colleague of Les (at Les.net, the future hoster)
I'm aware of what ASNs connect here via private peering and via the local
IX. Right now, I count 12 ASNs being learned from the IX's route servers.
I think it should be possible for me to add those ASNs to your entry. I
think this might be the first time Peer ASNs are used.
If there's some reasonable way to automate the creation of
site-local
netblocks, I could do it that way, too... there's 94 netblocks (excluding
Hurricane Electric, who peers here too) involved.
Not really, I added 43 manually for my mirrors.
Adrian
12:06 p.m.
On 14-12-22 01:06 PM, Adrian Reber wrote:
I was confused by the different muug entries. I was looking at the
old
entry. If you add rsync URLs the crawler can scan the state of your
mirror much faster.
Done... but, I notice that I'm getting a lot of 404 errors in my web
server logs. All of them are for
http://muug.ca/pub/fedora/updates/something. Whereas the directory tree
I'm rsync'ing would put the files at
http://muug.ca/pub/fedora/linux/updates/something.
Is there some local manipulation required, or have I misunderstood
something about mirroring the "enchilada" source?
I think it should be possible for me to add those ASNs to your entry.
I
think this might be the first time Peer ASNs are used.
Let's wait until after the server gets moved - I have too many other
things on my plate right now.
Thanks,
-Adam
2:30 p.m.
On Sun, Dec 28, 2014 at 12:06:01PM -0600, MUUG Mirror Manager wrote:
On 14-12-22 01:06 PM, Adrian Reber wrote:
>I was confused by the different muug entries. I was looking at the old
>entry. If you add rsync URLs the crawler can scan the state of your
>mirror much faster.
Done... but, I notice that I'm getting a lot of 404 errors in my web server
logs. All of them are for http://muug.ca/pub/fedora/updates/something.
Whereas the directory tree I'm rsync'ing would put the files at
http://muug.ca/pub/fedora/linux/updates/something.
Is there some local manipulation required, or have I misunderstood something
about mirroring the "enchilada" source?
No, you just entered the wrong path. You should enter:
http://muug.ca/pub/fedora/linux/
The crawler marks your mirror as out of date but as you also are running
report_mirror your mirror is marked up to date (because report_mirror
with your configuration claims it is up to date). So your mirror is
flipping between being marked up to date and not. As long as it is
marked as up to date clients are redirected to your mirror and with the
information from MirrorManager they are searching for files which do not
exist. So, if you update the URL like mentioned above everything should
be fine.
If you have rsync running and mention it as a URL in MirrorManager our
crawler can use rsync for crawling which is much faster than via http.
What about the mirror ftp.muug.mb.ca. Is this also run by you? Can this
be removed?
Adrian
11:49 p.m.
On 14-12-29 02:30 PM, Adrian Reber wrote:
No, you just entered the wrong path. You should enter:
http://muug.ca/pub/fedora/linux/
Trying to fix that now, but am getting timeouts from
admin.fedoraproject.org when I follow the link
https://admin.fedoraproject.org/mirrormanager/host_category/7133?_csrf_to...
I can make changes to the host (like disabling it), but anytime I go
into the "Categories Carried" links, I get timeouts, so I can't change
the path.
The crawler marks your mirror as out of date but as you also are
running
report_mirror your mirror is marked up to date (because report_mirror
with your configuration claims it is up to date). So your mirror is
flipping between being marked up to date and not. As long as it is
marked as up to date clients are redirected to your mirror and with the
information from MirrorManager they are searching for files which do not
exist. So, if you update the URL like mentioned above everything should
be fine.
If you have rsync running and mention it as a URL in MirrorManager our
crawler can use rsync for crawling which is much faster than via http.
See above - I'm unable to edit the URLs right now.
What about the mirror ftp.muug.mb.ca. Is this also run by you? Can
this
be removed?
Yes, and not yet - not until the new one (muug.ca) is fully up and
stable and in its permanent home, which should be sometime in January.
Then we'll be in a better position to turn off the old one, and point
its hostnames over to the new server.
-Adam
11:58 a.m.
On Mon, 29 Dec 2014 23:49:30 -0600
MUUG Mirror Manager <mirror(a)muug.ca> wrote:
On 14-12-29 02:30 PM, Adrian Reber wrote:
> No, you just entered the wrong path. You should enter:
> http://muug.ca/pub/fedora/linux/
Trying to fix that now, but am getting timeouts from
admin.fedoraproject.org when I follow the link
https://admin.fedoraproject.org/mirrormanager/host_category/7133?_csrf_to...
I can make changes to the host (like disabling it), but anytime I go
into the "Categories Carried" links, I get timeouts, so I can't
change the path.
Odd. I was able to reach it from here ok. (Although it was very slow).
I hope you don't mind, but I went ahead and added the correct path
there for you.
Can you see if it looks ok now?
kevin
3402
days inactive
3412
days old
mirror-admin@lists.fedoraproject.org
7 comments
3 participants
participants (3)
-
Adrian Reber -
Kevin Fenzi -
MUUG Mirror Manager