Linode Critical Xen Maintenance
For such a global upgrade, can we expect the reboot to happen at the very beginning of that 2 hours window, based on your experience?
I don't work for Linode so can't say that's what will happen but it's an educated guess
When using Debian under KVM and virt-manager at home, I need the acpi-support-base and acpid packages to be installed so that the "shutdown" menu works. Surprisingly, this package was not installed by default on my first linode Debian 7 deployment. Is Xen different about this?
Related question: How do we ensure that our machines will be "cleanly shut down" from the outside?
The mechanism should be identical to when you use the Shut down or Reboot buttons in the Linode Manager (or the automated shutdowns during a migration or upgrade, for that matter). So if you wanted, you could run a test in advance when convenient on your own schedule to ensure your Linode will do the right thing during such a shutdown/reboot cycle. But yes, for me such shutdowns (whether manually by me or automatically by Linode) has always been a graceful shutdown assuming the guest was operating properly in the first place.
> When using Debian under KVM and virt-manager at home, I need the acpi-support-base and acpid packages to be installed so that the "shutdown" menu works. Surprisingly, this package was not installed by default on my first linode Debian 7 deployment. Is Xen different about this?
I'm guessing here, as I don't know for sure, but Linode uses Xen PV for its guests, so I expect the PV drivers are shutting down the guest from within the guest itself. It's not simulating an external hardware signal to generic drivers; rather the Xen aware drivers execute a shutdown on your behalf.
It is interesting that the notice in the Linode Manager is less than useful….
Nice to know what my default timezone is set to, but what is the actual time of the outage?
Just received notice via email, which lists the times in UTC. So what is the point of telling me my default timezone if the notification is using UTC anyway?
One of my Linodes is getting less than 24 hour notice. That is a bit unusual. The other is 5 days out, which makes it easier to notify clients involved.
Look in the table of Linodes?
The time is different for each Linode, and as per the big yellow banner, each will be worked on "at the time listed below".
Look in the table of Linodes?
don't mind me… I am blind. I didn't notice the extra column maint times in the list of linode for some reason…
Can anyone who has had the maintenance done to their Linode comment on how long the downtime lasted? I understand it's scheduled for 2 hours but the actual downtime can be much less. Thanks.
For me this morning 9am MST, it was about 30-35 mins. I brought down my Linode myself and powered it up when the dashboard said complete rather than letting them shut it down and bring it back up. Might have been a bit faster as I wasn't watching the dashboard every minute.
I've had one so far, it was down 15 minutes. Fully automatic and no problems.
Good to hear, thanks for the info!
So what hour is that? I generally manage to figure out the AM/PM nonsense by thinking 'AM=after midnight' (yes I know it's meant to be some Latin). But 12:00:00 AM? Is it midnight or is it noon? Even a web search indicates it's ambiguous.
I'm sorted now because I just logged in to the linode manager and it says it's 11 hours left.
But come on, why use such an unscientific, stone-age time system? It starts out fine with '2015-03-07', standard date format and all, and then runs off into something that could as well be furlongs. Please, this is the 21th century, use 24 hour time formats!
of course everybody uses a 24-hour time format independent on which language is in use.
There, fixed that for you.
If Linode sent out an email saying the maintenance started at 03:00:00 then people would ask "is that am or pm?" Even though I speak 24hr, doesn't mean the person sending to me does!
The answer, of course, is "00:00:01 am" and "12:00:01 pm"; always add that extra second
The ISO format does not have AM/PM. See
I also had to think twice about the hour when I saw "12:00 AM" so the argument that they somehow "have" to use AM/PM to reduce confusion does not hold, IMHO.
As I said, I figured that out already due to the '11 hours left' message. The point is, why send out emails with a time specified in that horrid am/pm format? Most countries (nearly everyone) in the world are not in am/pm land, and use a sane 24 hour clock. Likewise, Linode's customers are all over the world. Linode should be precise with such important information, and that means using a sane time format in their email communication. And no, that has nothing to do with language. My work is 100% international, nearly everybody communicates in English, and of course everybody uses a 24-hour time format independent on which language is in use.
Linode is an American company, Americans use AM/PM. I work for an enormous international company based in NY. Almost everything that comes out is stated in AM/PM and in ET (US/Eastern time). Everyone else knows how to convert it.
A google is only ambiguous because some pedantic moron has butchered wikipedia to make it so. 12:00 AM is midnight, period.
Good news is that there's a nice countdown timer when you look at the overview page for your Linodes, so you can calibrate accordingly.
1am is in the middle of the night, therefore, 12am (1 hour before) is midnight.
1pm is the middle of the day, therefore, 12pm (1 hour before) is noon.
It's not all that hard, but I agree, 24hr time is much clearer.
I don't think so. If they sent a message saying the maintenance starts at "2015-03-06 03:00:00", people could easily infer from the year-month-day order that they are using the ISO format for the entire timestamp, not just for the day.
Except for those who don't know about such things.
Using AM/PM removes any ambiguity as to what's what.