On Fri, Dec 05, 2008 at 06:10:03PM +0000, Andy Smith wrote:
On Wed, Dec 03, 2008 at 01:11:56PM +0000, Andy Smith
One day in January between Saturday 10th and
Sunday 18th inclusive I
intend to be taking down all BitFolk servers in turn to perform a
memory upgrade and some other work. It shouldn't take more than
about 30 minutes per server.
This will be happening on the afternoon (GMT) of Sunday 11th
I should have confirmed sooner, but here is a reminder that this
work is going ahead on Sunday 11th January starting around 13:00
Unfortunately, my preparatory tests indicate that it is not possible
to suspend a domain with one version of Xen and then successfully
restore it with a later one, at least not between the version in
use and the version we need to move to.
A Xen upgrade is necessary because the newer kernels that ship with
more recent Linux distributions just do not work with Xen 3.0.x as
present in Debian Etch, used by Bitfolk. Without an upgrade, you
would be stuck using Debian Etch 2.6.18 era kernels for the
Therefore I am afraid this upgrade will entail a full shutdown /
boot for all customers.
The other major reason for this work is to max out the servers with
RAM for a planned RAM increase later in the month. This is going
ahead; it will be a 120M increase for all paying customers (except a
few special cases who are already aware). I'm not able to confirm
exactly when this will be happening, but it should be very soon
after the hardware work is done. I want to advertise the new plans
on the web site but I won't do it until existing customers have
started to be upgraded.
Some have asked why they cannot have the extra RAM on the day,
saving them one reboot. The original easy answer to that was that
it's not possible to alter a Xen domain's RAM or block devices
without restarting it. That obviously no longer applies, but there
are other reasons why I can't do this.
Primarily, the logistical reason is that I do not really want around
200 VPSes to boot into a new configuration while I am on the data
centre floor. Even though the config change for extra RAM is
obviously trivial, this is too risky for me.
Secondly, two of the servers are already full enough with RAM that
there will not be capacity for every VPS on them to grow by 120M.
Some customers will need to be moved from those servers first.
Thirdly, doing this involves changes to administrative details such
as who has which plan. Not every customer is eligible for this
upgrade, so not just a case of editing the description of every plan. :)
I have been very busy planning the other aspects of this work and
have only ever planned for a gradual upgrade of individual VPSes
after the day of the work.
So sorry, I am not able to offer the RAM increase immediately and
can't do any special favours for people to get them that. If you
are in dire need of this extra RAM, by all means drop an email to
support(a)bitfolk.com to that effect and I will make sure to put you
at the front of the queue. If you do this then it's quite likely
that you will get the upgrade on the same night, or the next day.
Finally, some have asked if it will be possible to downgrade since
they do not need the extra RAM. It is not my intention to provide a
package smaller than 240M after the upgrades. Anyone who wants to
downgrade to a 240M plan will be welcome to do so once their current
contract has finished.
-- No-nonsense VPS hosting
Encrypted mail welcome - keyid 0x604DE5DB