Berkeley's bSpace Content Management System WROSE THAN HILTER!!1!!11! Update
An email from the Deputy Chief Information Officer:
I understand that the current outage is difficult and I regret any inconvenience or problems we have caused. IST has been working directly with supporting vendors since the outage began. The short version is that a large file system (around 1TB) became corrupted and could no longer be accessed. How this happened is not known as it is not supposed to be possible. We responded by deploying a replacement file system and have been building a copy of the data from backups, but the size makes restoration time consuming.
These problems, while they negatively impact bSpace, have taken place entirely in IST facilities and areas of responsibility. Unfortunately, the negative impact that our storage outage created for bSpace is ultimately transferred to its community. I apologize for this outage and I assure you it is receiving our highest priority.
I do understand that making cloud services work is really, really hard. R/W file systems become corrupted in what appears to be normal use. Even write-once-to-archive file systems become corrupted in what appears to be normal use (although that, I must admit, I have a harder time understanding). The question is: is running a cloud system within Berkeley's scope of comparative advantage? Make yourself or buy from outside?
