I just wanted to provide you with a quick note that our blog roll’s “October silence” is nothing but just that. Some of us became a father to a son, have needed to deal with some citizen/resident paperwork, some of us choose to entertain the fresh snowfall way up the Alps, others took some vacation time, and such and so forth.
In the all-work-no-play area, I think we’ve figured out webmail decryption/signing, a responsive skin to be made available to mainstream Kolab Now, new exciting service venture definitions even though still under development, and we have now been able to deal with our midterm election anxiety (albeit November 25th could incur some implications domestically).
Last night, a failure in the storage layer caused most of our services to be unavailable. In the week before, we replaced a failed hard drive. In the week before that, a so-called Virtual Fabric Adapter failed, causing a hypervisor to shut itself off. Since the most recent incident was the more serious downtime, that’s what we’ll start our reporting on.
Continue Reading “Incident Report: Thursday, 20:25 – Friday 01:15 UTC”
I’m considering adding a little bit of transparency to how, and perhaps how well, Kolab Now infrastructure is run, or is running.
Continue Reading “Adding a Little Byte of Transparency”
If you’ve noticed our responses to support tickets or monitoring alerts is a little slower than usual, that’s because this is now the view from our office:
Continue Reading “I Apologize for the Delay”