Re: 2012 PHP Mirror Overhaul
| From: | Mark | Date: | Sun, 20 May 2012 15:24:11 +0000 |
| Subject: | Re: 2012 PHP Mirror Overhaul | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-39200@lists.php.net to get a copy of this message | ||
Hi Danie Regarding tw.php.net: 1. sqlite: already installed 2. php was
upgraded Updated as of June 3. round-rubin configuration: done. tw1.php.net
4. LAYERED RSYNC:done. asia.rsync.php.net twemail.com
webmasterTWemail.comwebmaster"Daniel Brown" <danbrown@php.net>
???????:CAD9cnePhaZYrX4d5aV2dbVeeE6jSu_Ar-oBW-nrLKW3RaJ4S0w@mail.gmail.com...
> Greetings, official mirror maintainers;
>
> First of all, I would like to take the opportunity to thank you
> all very, very much, on behalf of the entire PHP user community around
> the world. Without your generosity in providing an official mirror of
> php.net, we would not be able to serve the community as we're able to
> at present. I've even built friendly, non-PHP-centric relationships
> with many of you over the years, and speak with some of you on a
> somewhat regular-basis, via email, Facebook, or other media. You all
> do a wonderfully fantastic job, and for that, I applaud and thank you.
> Keep up the great work.
>
> This month we're kicking off our mirror overhaul project for 2012.
> A lot of major changes are to be made, but the good news for all of
> you is that they're pretty simple. And, in fact, some of you only
> need to do 50% of them, because you're already ahead of the game. The
> vast majority will only need to do 75% of the work, while just nine
> mirrors will need to complete all steps to remain in compliance.
>
> The spring overhaul will consist of four phases, and will wrap up
> in totality on 30 June, 2012. These phases, with their respective
> deadlines, are as follows:
>
> * Install pdo_sqlite (31 May, 2012)
> * Upgrade to PHP >= 5.3.10/5.4.0 (15 June, 2012)
> * Round-robin country-code configuration (30 June, 2012)
> * Layered, "geodispersed" rsync (30 June, 2012)
>
>
>
> == PHASE 1: PDO_SQLITE ==
>
> The first phase is so simple, and affects so few of you, that I've
> only allotted two weeks, and that's still more than enough time.
> Because of this, no extensions will be granted beyond the deadline
> date. The only mirrors who need to add support for pdo_sqlite as of
> this moment are:
>
> CN.PHP.NET (Dai Yun Jie)
> FI.PHP.NET (Sami Louko)
> GR2.PHP.NET (Spyros Ioakim)
> ID.PHP.NET (Budi Setiawan)
> IT.PHP.NET (Sandro Tosi)
> PA.PHP.NET (Oscar Echeverry)
> RO.PHP.NET (Werner Wasicsek)
> RU.PHP.NET (Yaroslav Gorodetsky)
> RU2.PHP.NET (Dmitry Morozovsky)
>
> Please note that, at this time, we are requiring pdo_sqlite, not
> pdo_sqlite2, sqlite3, or anything else. You may feel free to install
> any other SQLite extension(s) you'd like, and are encouraged to also
> install pdo_sqlite2, but we require the installation and availability
> of pdo_sqlite on all mirrors.
>
>
>
> == PHASE 2: PHP UPGRADE ==
>
> The PHP upgrade requirement will affect 90 mirrors in total (only
> 19 as of today are compliant with the new requirement). Many of you
> probably recall the last overhaul, when we finally rid the network of
> PHP4. This time around, it will affect many, many more mirrors, but
> the upgrade won't be nearly as drastic. All we need you to do is
> upgrade your mirror to PHP 5.3 >= 5.3.10, or PHP 5.4 >= 5.4.0. You
> can choose which branch you'd like to use, and are strongly advised to
> compare the differences prior to upgrading. The deadline for this
> phase is set for 15 June, 2012 (one month from today), and can be
> extended to 30 June, 2012, if you contact me NO LATER THAN 1 June,
> 2012. Requests for deadlines after 1 June, 2012, will be rejected for
> all but the most compelling of reasons, and acceptance will be judged
> on a case-by-case basis. On or before 1 June, however, extensions
> will be automatically granted upon request.
>
>
>
> == PHASE 3: ROUND-ROBIN ==
>
> Round-robin country code configuration --- this is something I had
> initially considered and opted to avoid, but then Hannes Magnusson
> (bjori), a long-time PHP project centerpiece, made some very strong
> arguments in favor of doing this, and I couldn't agree more. All we
> need you, the maintainer, to do on your end is to add a numberless
> ServerAlias reference of your mirror to your Apache configuration
> file. So, for example, if your mirror is CA2.PHP.NET (which is one I
> provide), you would add: ServerAlias ca.php.net. Please also retain
> your existing hostname configuration. Caveat: if your mirror does not
> have a number, you will need to do one more step; you will need to add
> XX1.PHP.NET as a ServerAlias. So, for example, Jaime Echeverry runs
> the primary mirror in Switzerland, CH.PHP.NET. In his case, he will
> keep that hostname, but also add the ServerAlias entry of CH1.PHP.NET.
> When this step has been completed, I need each and every one of you
> to send an email to php-mirrors@lists.php.net and CC me
> (danbrown@php.net) so that I can update your record in our system and
> enable the round-robin load-balancing for your country. The deadline
> for this phase is set for 30 June, 2012, and can be extended to 15
> July, 2012, if you contact me NO LATER THAN 15 June, 2012. Requests
> for deadlines after 15 June, 2012, will be rejected for all but the
> most compelling of reasons, and acceptance will be judged on a
> case-by-case basis. On or before 15 June, however, extensions will be
> automatically granted upon request.
>
>
>
> == PHASE 4: LAYERED RSYNC ==
>
> In a move that is the very epitome of the phrase "better late than
> never," we're finally going to implement something I designed back in
> January, 2011. And thanks to the patience of Mark Scholten
> (NL.PHP.NET), we can still make it happen almost a year-and-a-half
> after its conception. The plan is to reduce the load on the rsync
> server (RSYNC.PHP.NET), distribute the data for redundancy, and speed
> up the entire process, making network-wide updates much quicker and
> much more reliable. Please see http://links.parasane.net/r5sh
> for
> more information on this.
>
> To complete this phase, all you'll need to do is update your cron
> script, based upon your mirror's physical location in accordance with
> the map on the link provided above, to pull from your regional rsync
> node (RRN). After this is complete, no one should be pulling from the
> master rsync server except for the three RRNs. This phase will not
> begin until the RRNs are all in place sometime during the month of
> May, but I will make another announcement when your local RRN is
> available so that you can make the necessary changes, and will be sure
> to provide ample time for you to complete the changeover and remain in
> compliance. The deadline for this phase is set for 30 June, 2012, and
> can be extended to 15 July, 2012, if you contact me NO LATER THAN 15
> June, 2012. Requests for deadlines after 15 June, 2012, will be
> rejected for all but the most compelling of reasons, and acceptance
> will be judged on a case-by-case basis. On or before 15 June,
> however, extensions will be automatically granted upon request.
>
>
>
> That's it for now. If anyone has any questions, please don't
> hesitate to reply-all to this email. Otherwise, folks, I'm looking
> forward to working with you all through this overhaul and having it
> completed on time by everyone involved (including myself). Please
> feel free to work ahead of schedule, as well (with the exception of
> the layered rsync servers, of course), and let me know about your
> progress.
>
> ALSO: Please remember to inform me when you've added the required
> ServerAlias for your mirror so that I can update your mirror in our
> system.
>
> And again, thank you all very much for everything you do.
>
> --
> </Daniel P. Brown>
> Network Infrastructure Manager
> http://www.php.net/