Bug#702122: mirrors: add debian-mirror.sakura.ne.jp to syncproxy leaf
On Sun, 03 Mar 2013, Hideki Yamane wrote: > > Some of you may know, I've started debian-mirror.sakura.ne.jp. > > http://henrich-on-debian.blogspot.com/2013/02/introducing-debian-mirrorsakuranejp.html > > Now it is pushed-mirror under hanzubon.jp, and I think it's better to be > pushed > from upstream syncproxy if we can. Is this request still standing? The closes syncproxy to .jp would be in the US, syncproxy2.wna.debian.org -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/
Bug#702122: mirrors: add debian-mirror.sakura.ne.jp to syncproxy leaf
Hi, Sorry for the late reply. On Mon, Mar 04, 2013 at 06:33:14PM +0900, ISHIKAWA Mutsumi wrote: > I don't think it is good idea. Because synxproxy to Japan trans > pacific network connection bandwidth is narrow (~ 5Mbps). A little test shows ~5MBytes/s i.e. 40Mbps (as of now). > If you want to setup some kind of redundancy of push primary in Japan, > we should build some kind of pushproxy and management system of > primary pusy mirror backend. Could you please check what you want to do on your side, before we configure the push ? For push setup, we need: - you to record your mirror at http://www.debian.org/mirror/submit - a hostname/user/port for the SSH trigger Then we'll provide you a rsync access (though you may use the same as hanzubon). Best regards. > > Hideki Yamane wrote: > >> > >> Some of you may know, I've started debian-mirror.sakura.ne.jp. > >> > >> http://henrich-on-debian.blogspot.com/2013/02/introducing-debian-mirrorsakuranejp.html > >> > >> Now it is pushed-mirror under hanzubon.jp, and I think it's better to be > >> pushed > >> from upstream syncproxy if we can. > >> > >> The reason is, sakura mirror and other mirrors pushed from hanzubon.jp is > >> providing > >> ftp.jp.debian.org. ftp.jp.d.o has some robustness mechanism that if > >> primary one goes > >> down or not sync some days and be obsolete, then DNS entry will switch to > >> point > >> another mirror. However, if hanzubon.jp archive will stop or be > >> corrupted, then > >> **all** of those mirrors are same state. If sakura mirror can get updated > >> archives > >> from syncproxy, ftp.jp.d.o get more robustness IMO. > >> > >> Could you consider to add sakura mirror as syncproxy leaf, please? -- Simon Paillard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702122: mirrors: add debian-mirror.sakura.ne.jp to syncproxy leaf
I don't think it is good idea. Because synxproxy to Japan trans pacific network connection bandwidth is narrow (~ 5Mbps). If you want to setup some kind of redundancy of push primary in Japan, we should build some kind of pushproxy and management system of primary pusy mirror backend. > In <20130303075058.c44c71f5a6785883bddec...@debian.or.jp> > Hideki Yamane wrote: >> Package: mirrors >> Severity: normal >> X-debbugs-CC: debian-mirr...@lists.debian.org, bo...@debian.or.jp >> >> Hi, >> >> Some of you may know, I've started debian-mirror.sakura.ne.jp. >> >> http://henrich-on-debian.blogspot.com/2013/02/introducing-debian-mirrorsakuranejp.html >> >> Now it is pushed-mirror under hanzubon.jp, and I think it's better to be >> pushed >> from upstream syncproxy if we can. >> >> The reason is, sakura mirror and other mirrors pushed from hanzubon.jp is >> providing >> ftp.jp.debian.org. ftp.jp.d.o has some robustness mechanism that if primary >> one goes >> down or not sync some days and be obsolete, then DNS entry will switch to >> point >> another mirror. However, if hanzubon.jp archive will stop or be corrupted, >> then >> **all** of those mirrors are same state. If sakura mirror can get updated >> archives >> from syncproxy, ftp.jp.d.o get more robustness IMO. >> >> Could you consider to add sakura mirror as syncproxy leaf, please? >> >> -- >> Regards, >> >> Hideki Yamane henrich @ debian.or.jp/org >> http://wiki.debian.org/HidekiYamane -- ISHIKAWA Mutsumi , -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702122: mirrors: add debian-mirror.sakura.ne.jp to syncproxy leaf
Package: mirrors Severity: normal X-debbugs-CC: debian-mirr...@lists.debian.org, bo...@debian.or.jp Hi, Some of you may know, I've started debian-mirror.sakura.ne.jp. http://henrich-on-debian.blogspot.com/2013/02/introducing-debian-mirrorsakuranejp.html Now it is pushed-mirror under hanzubon.jp, and I think it's better to be pushed from upstream syncproxy if we can. The reason is, sakura mirror and other mirrors pushed from hanzubon.jp is providing ftp.jp.debian.org. ftp.jp.d.o has some robustness mechanism that if primary one goes down or not sync some days and be obsolete, then DNS entry will switch to point another mirror. However, if hanzubon.jp archive will stop or be corrupted, then **all** of those mirrors are same state. If sakura mirror can get updated archives from syncproxy, ftp.jp.d.o get more robustness IMO. Could you consider to add sakura mirror as syncproxy leaf, please? -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
