{"id":3364,"date":"2017-04-07T20:00:17","date_gmt":"2017-04-07T20:00:17","guid":{"rendered":"https:\/\/blog.mageia.org\/en\/?p=3364"},"modified":"2017-04-08T16:52:20","modified_gmt":"2017-04-08T16:52:20","slug":"weekly-roundup-2017-week-14","status":"publish","type":"post","link":"https:\/\/blog.mageia.org\/en\/2017\/04\/07\/weekly-roundup-2017-week-14\/","title":{"rendered":"Weekly roundup 2017 – week 14"},"content":{"rendered":"

Infrastructure<\/span><\/h2>\n

So sadly the big news this week is the outage of <\/span>two<\/span> of our servers for needed upgrades. The status of the services that are down can be read here<\/a>. Our sysadmins have <\/span>been hard at work, already <\/span>push<\/span>ing<\/span> 30 patches to our infrastructure and work<\/span>ing<\/span> on porting the PostgreSQL database<\/span> used by most services<\/span> to a new server<\/span>.<\/span><\/p>\n

The first priority is to<\/span> get the mirrorlist service running again quickly as it has the largest impact on users. Our Bugzilla, which will not only be moved to a machine running Mageia 5 but will also be upgraded to <\/span>Bugzilla<\/span> 5<\/span>,<\/span> will be<\/span> the next <\/span>step<\/span>. The <\/span>homepage <\/span>ha<\/span>s<\/span> already been moved to a server that is fully up to date and had <\/span>no<\/span> downtime.<\/span><\/p>\n

Note that the mirrorlist and Bugzilla\u00a0were restored shortly after publishing, thanks to the sysadmins for finishing the upgrades so quickly.<\/em><\/p>\n

While the updates on the <\/span>two<\/span> servers we preventively took down were severely needed<\/span> for security reasons<\/span>, they have been in planning for a significant time, <\/span>and require non-trivial development work to port scripts, templates and configurations to the updated Mageia 5 ecosystem.<\/span><\/p>\n

The outage only affected two of our many servers. All of our other servers, including the build nodes, for i586, x86_64 and arm, which I struggled to count from memory, 6 arm and 3 x86 at last count – I swear the arm nodes are multiplying, ISO builder and the repository server have remained active and fully up to date on <\/span>Mageia 5<\/span>, busily building for Cauldron and Mageia 5, you can see the queue here<\/a>.<\/span> Nevertheless, it must be noted that the two servers which had to be taken down were the most exposed as they hosted most web-facing services (and since they ran outdated software, also the most vulnerable).<\/span><\/p>\n

We can only apologise that these upgrades have not happened sooner, even if the impact on the development has been minimal, we will have to continue to make changes in our sysadmin procedure<\/span>s<\/span> to ensure th<\/span>at<\/span> upgrades are simpler <\/span>and timelier <\/span>in the future.<\/span><\/p>\n

Once the services migration is complete, we will publish a blog post to give a better overview of what the components of our infrastructure<\/span> are<\/span>, what software they run,<\/span> how the sysadmin team maintains it<\/span> and the evolution in our sysadmin team that has been happening to for some time now<\/span>.<\/span><\/p>\n

Cauldron<\/span><\/h2>\n

ISO building and testing for Mageia 6 RC has been making good progress. The release blockers are being fixed nicely, a new drakxtools included on the latest ISOs fixed a number of <\/span>partitioning <\/span>bugs so the ISOs are starting to <\/span>b<\/span>ecome<\/span> satisf<\/span>actory. The Live ISOs are now ready for wider QA testing, and an EFI issue that was holding up the\u00a0<\/span>64-bit <\/span>Classical ISOs has hopefully been fixed.\u00a0<\/span><\/p>\n

There were u<\/span>pdates to many packages, the highlights o<\/span>f<\/span> which were:<\/span><\/p>\n