Maintenance is scheduled for the following Xen Beta hosts:

host117, dallas38, dallas47, dallas52, dallas56, dallas60, host56, fremont34, atlanta28, atlanta29, atlanta35, and atlanta36

This reboot will update the Xen beta hosts to our Xen production environment.

Maintenance will begin at:

9:00 p.m. Sunday April 6, 2008 (Eastern)
1:00 a.m. Monday April 7, 2008 (UTC)

Please allow a two hour window to update all twelve hosts. Your Linode will be gracefully shut down, the host will be rebooted, and then your Linode will be rebooted. We expect 15-25 minutes of downtime per host.

-Tom

As soon as you got Xen out of beta I made a ticket requesting a migration from my UML host to a Xen host. I assumed you would move me to a "stable" Xen host. But in this post I can see that the atlanta36 is on the list as a Xen Beta host. Is there a difference between that host and the others ("non-beta" Xen hosts)?

To be honest, I think you were migrated to a Xen beta host by mistake. This was before we did an audit of all of our xen hosts which needed to be upgraded to our production version. The only difference is the software versions running on the hosts themselves.

Sorry about that -- but it should just be a quick reboot...

-Chris

Ok, thanks for being honest at least. I suppose that the Xen beta server software will become the same version after the reboot as the stable servers, thus becoming a stable server, yes?

And yes, the server was back online again after the reboot at least within 30 minutes, perhaps even quicker.

Just wondering if all the hosts are being rebooted at the same time? Or are you doing them one at a time?

Maintenance on host117, dallas38, dallas47, and dallas52 is complete. Linodes are booting up now.

-Tom

Maintenance on atlanta28, atlanta29, atlanta35, and atlanta36 is complete. Linodes should be up at this time.

Maintenance on dallas56, dallas60, host56, and fremont34 is complete. This concludes the updating of the Xen beta hosts.

Have a nice day!

-Chris

Yes, I would like to know that too.

Even if it's quite time consuming I think that the best way to do these maintenance reboots is to wait for all the linodes to be running again on one host to before rebooting the next one.

I say this because as you know it isn't uncommon for a linode to need half an hour to start after a host reboot. Since for very good reasons they are booted one at a time.

So it could be possible, for example, to have two linodes on two freshly rebooted hosts, that are waiting their turn to start. This might hurt any high availability configuration one might have. This is a pity since you provide us with many options to create such setups.

I'm looking forward to hear from you guys, thanks for your time.
And kudos for deploying Xen for all the hosts! I know you did your best to provide for all of us a stable and enjoyable experience.