Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03AC69877 for ; Fri, 20 Apr 2012 16:24:30 +0000 (UTC) Received: (qmail 89764 invoked by uid 500); 20 Apr 2012 16:24:29 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 89695 invoked by uid 500); 20 Apr 2012 16:24:29 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 89687 invoked by uid 99); 20 Apr 2012 16:24:29 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 16:24:29 +0000 Received: from localhost (HELO mail-vb0-f47.google.com) (127.0.0.1) (smtp-auth username robweir, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2012 16:24:29 +0000 Received: by vbbfr13 with SMTP id fr13so7303134vbb.6 for ; Fri, 20 Apr 2012 09:24:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.67.208 with SMTP id p16mr4528510vdt.93.1334939068272; Fri, 20 Apr 2012 09:24:28 -0700 (PDT) Received: by 10.220.118.147 with HTTP; Fri, 20 Apr 2012 09:24:28 -0700 (PDT) In-Reply-To: References: <4F907AF2.4080806@gmail.com> <4F90857E.50105@gmail.com> <1334889404.9163.1.camel@sybil-gnome> Date: Fri, 20 Apr 2012 18:24:28 +0200 Message-ID: Subject: Re: mirrors, release publishing...again From: Rob Weir To: ooo-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Apr 20, 2012 at 6:06 PM, Kay Schenk wrote: > On Thu, Apr 19, 2012 at 7:36 PM, drew wrote: > >> On Thu, 2012-04-19 at 21:57 -0400, Mark Ramm wrote: >> > > A few ways, some worse than others: >> > > >> > > 1) Offer several download links: =C2=A0"Download from Apache, from >> > > SourceForge, from MirrorBrain". Of course that doesn't balance the >> > > load, but maybe it would if we randomized the order that they are >> > > listed. >> > > >> > > 2) Have a single link, but it is JavaScript that then directs to one >> > > of the three mirrors systems. =C2=A0This is easy to distribute the l= oad >> > > according to a defined schedule. =C2=A0Marcus prototyped an approach= like >> > > this. It looked like it was working. =C2=A0I'm not sure, however, wh= ether >> > > it handled fallbacks. =C2=A0For example, you randomly select to use = the >> > > Apache mirror, but the particular operator chosen is down. =C2=A0Use= r >> > > experience for backing out of that and repeating was as nice as it >> > > could be. >> > > I'll take a look at what Marcus did. It is very easy to just do a "random= " > link based on 3 mirror systems -- ASF, SourceForge, MirrorBrain. > > >> > > >> > > 3) Some variation on 3 where we handle the fallbacks better, or at >> > > least handle failures better, so the user just needs to click again. >> > >> > > Yes, this is desirable -- but I think this would involve more server-side > intelligence or ajax programming instead of simple JS. =C2=A0I'd need to = look > into it. Maybe beyond my capabilities. :/ > > > >> > I would be in favor of a forth option suggested by Andreas in another >> thread: >> > >> > * Route "autoupdater" traffic through one system (MirrorBrain) >> > > Ah yes...ye olde autoupdater. As of yet, I don't think we have nailed dow= n > the "format" of the feed document for this. I could be wrong, but I haven= 't > seen anything from anyone -- maybe another separate thread on this is in > order. I tried several approaches to make this actually work, and nothing= ! > So, this makes sense but ????? I havent' forgotten about it, I just don't > know what to do about it. We need very specific details on constructing t= he > atom feed and then, of course, constructing it. > > >> > * Route web based traffic through another (SF as primary, and Apache >> > mirrors as secondary) >> >> Well, that sure looks like to most sane way to go from what I've seen >> described - seems the cleanest way. >> >> //drew >> >> > OK, in summary -- I'll take a look at what Marcus has already done -- and > get a prototype "simple" random selection DL script out there early on ne= xt > week for additional comments. > It looks like we need to worry about three things: legacy downloads, AOO 3.4 downloads and OOo 3.3 upgrades. So how about something like this: 1) Legacy downloads (OOo 3.3.0 and earlier) are distributed only via Mirror= Brain 2) AOO 3,4 release goes to SourceForge and Apache for download, with random selection and a splitting ratio that we can tune in the script. The script Marcus started is a good start, This allows us to gain some experience working with all three networks, see how they perform, get user feedback,etc, before tackling the upgrades. Then 3) When we are ready to turn on the automatic updates for 3.3.0->3.4.0, then we make a choice based on what we've learned by doing 1) and 2). In other words, don't worry about the update downloads until later, based on which one appears to have more latent capacity. -Rob > >> >> > >> > This eliminates potential problems with "which mirror network is >> > having a problem" kinds of debugging which would be particularly >> > pernicious if we randomized anything about the process. It also has >> > the benefit of most closely matching Joe's original suggestion of how >> > to use SF.net, and provides a clear accountability/support chain for >> > users when downloads fail. >> > >> > SF.net will as previously mentioned provide an API to collect stats on >> > downloads from our system, and we'd be happy to help host a bouncer >> > that forwards requests to a MirrorBrain server so that updater stats >> > can be collected as well if that helps the team measure the release >> > download volume more effectively. >> > >> > --Mark Ramm >> > =3D=3D=3D=3D >> > This e- mail message is intended only for the named recipient(s) above= . >> It may contain confidential and privileged information. If you are not t= he >> intended recipient you are hereby notified that any dissemination, >> distribution or copying of this e-mail and any attachment(s) is strictly >> prohibited. If you have received this e-mail in error, please immediatel= y >> notify the sender by replying to this e-mail and delete the message and = any >> attachment(s) from your system. Thank you. >> > >> > >> >> >> > > > -- > -------------------------------------------------------------------------= --------------- > MzK > > "Women and cats will do as they please, > =C2=A0and men and dogs should relax and get used to the idea." > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0-- > Robert Heinlein