[Koha-devel] Outage for bugs.koha-community.org : Fwd: Linode Support Ticket 9818790 - Critical Maintenance for CPU Vulnerabilities (Meltdown)

[Chris Cormack]

* Mark Tompsett (mtompset at hotmail.com) wrote:
>Greetings,
>
>I believe the outage is over (it suggests 2 hours max), but something
>gateway-wise is still buggy for dashboard.
>Bugzilla is back up. It is the weekend there, so no rush, but it would be
>nice to have back up.

Should be all back now

Chris
>
>GPML,
>Mark Tompsett
>
>-----Original Message-----
>From: Chris Cormack
>Sent: Wednesday, January 17, 2018 10:45 PM
>To: koha-user ; koha-devel at lists.koha-community.org
>Subject: [Koha-devel] Outage for bugs.koha-community.org : Fwd: Linode
>Support Ticket 9818790 - Critical Maintenance for CPU Vulnerabilities
>(Meltdown)
>
>It looks like my linode which hosts bugs.koha-community.org and the
>dashboard and few other sites will be down for maintenance
>at 2018-01-19 9:00:00 AM UTC
>
>Chris
>
>
>
>---------- Forwarded message ----------
>From:  <support at linode.com>
>Date: 18 January 2018 at 16:39
>Subject: Linode Support Ticket 9818790 - Critical Maintenance for CPU
>Vulnerabilities (Meltdown)
>To: chris at bigballofwax.co.nz
>
>
>
>Hello,
>
>A number of serious security vulnerabilities affecting multiple CPU
>architectures were recently disclosed by Google's Project Zero team as
>outlined in our blog post[1]. In order to address the disclosed
>vulnerabilities, the physical hardware on which your Linode resides
>will need to undergo maintenance. This is the first of several
>separate maintenances that will be necessary to fully mitigate these
>vulnerabilities. This maintenance specifically patches the Meltdown
>vulnerability; the Spectre vulnerability will be addressed in a future
>maintenance cycle. We will inform you of these maintenance cycles via
>additional tickets.
>
>Scheduled maintenance windows are listed within the Linode Manager[2]
>in the time zone that was configured in your user's My Profile[3]. The
>maintenance window of new Linodes and upgraded, migrated, or resized
>Linodes will be reflected in the Linode Manager[2], but you may not
>receive maintenance ticket updates for these changes.
>
>The following Linode(s) have now been assigned a maintenance window in
>which a reboot will occur. Please note that these times can change as
>a result of the actions mentioned above. At this time your reboot
>schedule in UTC is as follows:
>
>* 2018-01-19 9:00:00 AM UTC - bugs
>
>You can prepare your Linode for this maintenance by following our
>Reboot Survival Guide. By following this guide before your
>maintenance, you will be able to ensure that services running on your
>Linode are resumed properly. The Reboot Survival Guide is available
>here:
>
>https://www.linode.com/docs/uptime/reboot-survival-guide
>
>These updates affect the underlying infrastructure that your Linode
>resides on and will not affect the data stored within your Linode. To
>further protect your Linode, we strongly recommend that you verify it
>is configured to boot using our latest kernel, which includes patches
>to help address these vulnerabilities. If your Linode's Configuration
>Profile is set to utilize our latest kernel, your kernel will
>automatically be updated upon rebooting.
>
>During the maintenance window, your Linode will be cleanly shut down
>and will be unavailable while we perform the updates. A two-hour
>window is allocated, however the actual downtime should be much less.
>After the maintenance has concluded, each Linode will be returned to
>its last state (running or powered off).
>
>We regret the short notice and the downtime required for this
>maintenance. However, due to the severity of these vulnerabilities, we
>have no choice but to take swift and immediate action to ensure the
>safety and security of our customers. For these reasons, we must
>adhere to a strict timetable, and will not be able to reschedule or
>defer this maintenance.
>
>If you experience any issues following the maintenance, please feel
>free to reach out to us and we will be happy to assist.
>
>--Linode
>
>[1]
><https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre>
>[2] <https://manager.linode.com>
>[3] <https://manager.linode.com/profile>
>
>
>---
>https://manager.linode.com/support/ticket/9818790
>_______________________________________________
>Koha-devel mailing list
>Koha-devel at lists.koha-community.org
>http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>website : http://www.koha-community.org/
>git : http://git.koha-community.org/
>bugs : http://bugs.koha-community.org/
>
>_______________________________________________
>Koha-devel mailing list
>Koha-devel at lists.koha-community.org
>http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>website : http://www.koha-community.org/
>git : http://git.koha-community.org/
>bugs : http://bugs.koha-community.org/

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20180120/aa8723c0/attachment.pgp>