The Metabase API has been changed over. Some bugs were fixed and everything appears stable. If there are any problems, I will revert to the old Metabase API. If I am unresponsive, testers can point their machines to `metabase-old.cpantesters.org <http://metabase-old.cpantesters.org/>` to reach the old Metabase API. All the old infrastructure is still ticking over and will continue to do so until the new things have been stable for at least a week.
Moving away from EC2 is a fairly major cost savings: What we were paying $250/mo for we can now pay $0/mo for. That said, the Metabase section of the site has been its own server for a long time, and now we're adding its work to our one existing server that already does everything else except the database. To help spread the work out, if anyone still has one or two older, outdated servers sitting in a rack somewhere doing nothing and could make them available to the CPAN Testers project, let me know. I know people have volunteered hardware before, but I wasn't in a place where I could easily make use of it. Now that the new Metabase API exists, and now that I am very close to a Minion job-queue-based backend processing system, I can more easily spread work across multiple machines. For donating, you'll get a place on the sponsors list (http://iheart.cpantesters.org <http://iheart.cpantesters.org/>), and you'll help continue making Perl and CPAN a community of people collaborating on stable, useful software projects. If there are any other questions, problems, or concerns, please let me know. Thanks, Doug Bell [email protected] > On Aug 9, 2017, at 3:03 PM, Doug Bell <[email protected]> wrote: > > [Cross-posting from the CPAN Testers blog: > http://blog.cpantesters.org/diary/209 <http://blog.cpantesters.org/diary/209>] > > Summary: I will be doing work on the Metabase API on 2017-08-12. Writing test > reports may be unresponsive for a few minutes, and there may be bugs. Please > let me know if there are any problems submitting test reports. > > I have completed the processing script for the new test report format. This > was the last step in moving the Metabase API away from Amazon and on to our > MySQL cluster for cost and stability reasons: Amazon SimpleDB is too > expensive, and its limitations for our purposes outweigh its costs. We have > always maintained a copy of the Metabase data in our MySQL database, and > there's no real need to continue having two live copies of the same data > (especially when one of the copies costs money every time you ask for a piece > of data). > > This Saturday, 2017-08-12, around 1:00 PM US/Central (18:00 UTC), I will be > switching DNS over to the new, backwards-compatible Metabase API which writes > to our MySQL database. A few months ago, I asked for testers to try this new > API out, and everything went well (thanks to everyone who helped with that). > The new API works the same as the old API: No changes are needed for your > testers or anyone consuming the minimal data feeds out of the Metabase API > (the log.txt view). > > Since this is only a DNS change, the downtime for the change should be zero > as DNS propagates and your testers are pointed at the new IP address. Since > it's possible for me to mess up this change, there may be some downtime. > Since all software has bugs, there may be some downtime if any bugs are > revealed by all the testers being migrated to the new API. > > This change (and all the work around this change) sets up the project for new > changes down the road: > > * Speeding up report processing by triggering individual report processing > jobs as reports are submitted > * Distributing those processing jobs over multiple machines to improve > performance > * Making the test report text available immediately after submission instead > of having to wait for backend processing jobs > > If you have any questions, feel free to reply to this thread or to me > directly. > > Doug Bell > [email protected] <mailto:[email protected]> > > >
signature.asc
Description: Message signed with OpenPGP
