16 Mar 2016
17:44 UTC
Bytemark Engineer
This happened at the scheduled time and went according to plan, aside from a brief (~5 second) outage to authoritative DNS at around 17:33.
We did overrun the maintenance window by approx. 15 minutes, due to a couple of unforeseen configuration issues. Shouldn't need to do this again, though.
As ever, do get in touch if you see any problems.
9 Mar 2016
17:48 UTC
Bytemark Engineer
We're planning to make a few changes to where BigV stores its data on the 16th March. This will require a brief period where we won't be able to accept changes (creating new machines, altering existing ones, etc). This is necessary to avoid data inconsistencies!
The maintenance window should start at 5pm and last for around 20 minutes. Guest operation will be unaffected; attempts to make changes via the API, CLI or web interfaces will report a "try again later" error.
In the event of a problem, we will roll back to the old database location and try again another time. I expect the following items to be unaffected, but they will be at-risk for the maintenance window:
9 Mar 2016
14:51 UTC
Bytemark Engineer
We're planning to make a few changes to where BigV stores its data on the 16th March. This will require a brief period where we won't be able to accept changes (creating new machines, altering existing ones, etc). This is necessary to avoid data inconsistencies!
The maintenance window should start at 5pm and last for around 20 minutes. Guest operation will be unaffected; attempts to make changes via the API, CLI or web interfaces will report a "try again later" error.
In the event of a problem, we will roll back to the old database location and try again another time. I expect the following items to be unaffected, but they will be at-risk for the maintenance window: