Am Monday 04 October 2010 schrieb Carsten Otto:
> Hi,
>
> On Mon, Oct 04, 2010 at 10:44:40AM +0200, Stephan Kulow wrote:
> > > We get our data pushed from OpenSUSE directly. If there are files
> > > missing, please push better :)
> >
> > I see that *Factory* is excluded for your mirror, that explains a good
> > share of what I see as it matches the project name - one of the most
> > busy ones actually.
>
> Oh, I thought we were mirroring everything OpenSUSE has to offer. What
> do we need to do to actually get that? Could you just add Factory to the
> pushes (and do a full sync)? We will extend disk space on demand, so it
> may take a while until we are complete (as an alternative could you tell
> us how much space we need?).
>
I don't think it makes sense to mirror everything. Many files are see so
little traffic that mirroring them costs way too much. And now I'm really
puzzled what your intention is - you strarted the thread with "remove all
mirrors" and now you want even more stuff noone downloads?
Greetings, Stephan
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
For additional commands, e-mail: mirror+help(a)opensuse.org
Related to the heads up about rolling updates for the upcoming
release:
Have you investigated speeding up your main rsync servers?
ftp.acc.umu.se syncs from stage.opensuse.org, and we are seeing
sync-times in excess of 24 hours at times.
Sync-bandwidth on our end is limited to 1 Gbps, but the speeds we are
getting are much lower so we suspect that the upstream server is the
bottleneck.
If you can't increase the performance of the main rsync server it
might be beneficial to investigate a tiered approach where a few
select primary high-bandwidth mirrors sync from the master site and
the rest sync from the closest primary mirror. This is the way Debian
has been doing it for quite some time with great success.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke(a)acc.umu.se
---------------------------------------------------------------------------
I parked my harddisk - and got a ticket!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
Just wondering - it isn't being archived either?
Unless there is some specific reason, I'll go ahead and list it and have
it archived.
--
Per Jessen, Zürich (10.1°C)
openSUSE mailing list admin
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
Dear Mirror hosts,
Based on your reports I've been investigating the issues with IPv6 performance of stage.opensuse.org vs IPv4
I've been trying to confirm that we do have a problem with IPv6 specifically
We know our bandwidth to stage.opensuse.org is suboptimal at the moment (6 days to go until we expect that to
be alleviated) but in three sample sizes of ~5 minutes each during periods where our link seemed to be
comfortable I've been able to come up with the current results
IPv6 - 7.77MB/s | 14.41MB/s | 19.25MB/s
IPv4 - 6.09MB/s | 10.09MB/s | 6.52MB/s
This is from my personal host (rootco.de) hosted at hetzner
These tests were conducted with the default recommended rsync string for all of our stage.o.o mirrors, with
the addition of -4 for IPv4, -6 for IPv6, and --info=progress2 to get the average bandwidth calculation out of
rsync.
The general conclusion - At time of writing I can find no evidence that IPv6 is consistently worse than IPv4
for stage.o.o. It might even be better, though I'd want more thorough testing before making such claims.
Obviously, I still think there is scope for different results from different hosts. Peering in particular
could be different for IPv4 vs IPv6. If you notice different performance profiles for IPv4 vs IPv6 please
report your findings, including source IP addresses and traceroutes. This information will be especially
useful after March 1st, when we expect our routing to be significantly different than today.
At time of writing, I can see no sign that anything needs to be changed on stage.opensuse.org or anything
after the last hop. If the reported problems originate from congestion or peering, the changes to our link
expected on March 1st will hopefully resolve them all, and if not we'll have to investigate and resolve with
our new arrangements from then.
Regards,
--
Richard Brown
Technical Lead - openQA
openSUSE Chairman
Phone +4991174053-361
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
On Tue, 2017-02-21 at 15:32 +0000, Tim Bishop wrote:
> On Tue, Feb 21, 2017 at 04:15:13PM +0100, Richard Brown wrote:
> > On Tue, 2017-02-21 at 08:27 -0300, Carlos Carvalho wrote:
> > > Not here (opensuse.c3sl.ufpr.br). Last update took 18h40m with a speed less
> > > than 1MB/s. That's not enough for the rate of change of your repository.
> >
> > Thank you Carlos, very useful to know the issue is more widespread
>
> If it's useful, here on mirrorservice.org our sync times are about an
> hour for
>
> rsync://stage.opensuse.org/opensuse-full/opensuse/
>
> So that's significantly quicker. Maybe we're mirroring a smaller set of
> data?
>
opensuse-full is one of the larger modules, so it's unlikely
It's probably a case of poor peering between our current ISP and yourselves
Given this will also change with the new 1Gb/4Gb links on the way, I'm hoping we'll find things improve for
the people currently finding things so
However my QA-tester sense is tingling. To satisfy my curiosity Carlos, can you double check and confirm
you're using stage.o.o, and not rsync.o.o?
Tim, as everything seems to be fine and fast for you, can you please consider changing your rsync module from
opensuse-full to opensuse-full-with-factory?
This will give us another Tumbleweed mirror in the UK, which we're quite short on at the moment.
Many Thanks,
--
Richard Brown
Technical Lead - openQA
openSUSE Chairman
Phone +4991174053-361
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
On Tue, 21 Feb 2017, Tim Bishop wrote:
> On Tue, Feb 21, 2017 at 04:15:13PM +0100, Richard Brown wrote:
>> On Tue, 2017-02-21 at 08:27 -0300, Carlos Carvalho wrote:
>>> Not here (opensuse.c3sl.ufpr.br). Last update took 18h40m with a speed less
>>> than 1MB/s. That's not enough for the rate of change of your repository.
>>
>> Thank you Carlos, very useful to know the issue is more widespread
>
> If it's useful, here on mirrorservice.org our sync times are about an
> hour for
>
> rsync://stage.opensuse.org/opensuse-full/opensuse/
>
> So that's significantly quicker. Maybe we're mirroring a smaller set of
> data?
We mirror the same path, and see sync times all over the place. From
16 minutes and up, with a few hours being the most common one, and
more than a day occasionally.
Our sync-host is ipv6 enabled and comparing the RTT:s it seems like
stage.opensuse.org is really bad at it.
Running mtr -4t stage.opensuse.org and mtr -6t stage.opensuse.org
simultaneously in different windows I see 45-ish ms RTT for IPv4 and
80-100ish ms RTT for IPv6. The difference is introduced in the last
hop, so it's definitely bad mojo somewhere at or near
stage.opensuse.org ...
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | nikke(a)acc.umu.se
---------------------------------------------------------------------------
Many pages make a thick book.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
Dear openSUSE Mirror Hosts,
Thank you for your continued hosting of openSUSE Mirrors.
While recently resolving an issue with rsync.opensuse.org we realised that a significant number of you are
using rsync.opensuse.org as your content source.
rsync.opensuse.org is meant to be a publicly available mirror host, but as registered hosts on this mailing
list, you are entitled to use stage.opensuse.org, our dedicated mirror host for you.
This server not only provides access to pre-release content, but is the authoritative source for all openSUSE
content, including rsync.opensuse.org.
As registered mirrors, please configure your sync cronjobs to use stage.opensuse.org instead of
rsync.opensuse.org.
This is particularly important for mirrors hosting openSUSE Tumbleweed (formerly known as Factory) which has a
higher rate of change.
While I'm mentioning Tumbleweed, if you are hosting a Tumbleweed mirror, please consider ensuring your sync
cronjobs run more often than once every 24 hours.
Also, if you are not running a Tumbleweed mirror, please consider altering your configuration to do so.
Tumbleweed is more and more a key offering of the openSUSE Project and we really could benefit from more
Tumbleweed mirrors.
Compared to the "opensuse-full" module the addition of Tumbleweed will take approximately 60GB more disk space
with an estimated rate of change of ~5GB per day (with a 'worst-case' rate of change being 60GB which occurs
once or twice a year).
You can achieve this by altering your sync cronjob to use the "opensuse-full-with-factory" rsync module.
This request is part of an ongoing program of improvements including increased bandwidth for
stage.opensuse.org expected on 1st March (doubling) & 1st June (4x more, 8x current)
If you are experiencing problems with stage.opensuse.org performance, please let us know, especially after the
above dates.
Your ongoing feedback & support will help us shape and tune these improvements as we go forward.
Many Thanks,
--
Richard Brown
openSUSE Chairman
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
Hi,
Just a heads up. Leap 42.3 in opensuse/distribution/leap/42.3 is set
up to be rolling during the development phase, similar to
Tumbleweed. That means there's no 42.3-Current and no fixed
milestones that get created from it. Instead we only have the 42.3
directory that gets regular updates when openQA says it's good
enough. I'm hoping for increased attention and download numbers
during development phase of course :-)
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
I was just looking into setting up a public mirror -
https://en.opensuse.org/openSUSE:Mirror_infrastructure
Some of this stuff is a bit odd. Look at section "rsync modules":
> Sizes of the rsync modules are triangulated nightly:
>
> rsync modules of stage.opensuse.org
> rsync modules of rsync.opensuse.org
These both link to Peter Poeml's private site http://www.poeml.de/
and the sizes listed are incomplete. I guess we have these somewhere
internally too?
--
Per Jessen, Zürich (4.1°C)
http://www.hostsuisse.com/ - dedicated server rental in Switzerland.
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org
As of this morning at 08:19.
--
Per Jessen, Zürich (-2.0°C)
http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
--
To unsubscribe, e-mail: mirror+unsubscribe(a)opensuse.org
To contact the owner, email: mirror+owner(a)opensuse.org