...
All dates are "latest". Meaning it might happen earlier depending on when the carpenter work finish etc.
Date | Event |
---|---|
05-06.02.24 | Shutdown all servers and remove them from the racks |
07-08.02.24 | Carpenter work. Build support framing, replace tiles |
09.02.24 | Insert all SkyHiGh servers back in the racks, and resume production |
12.02.24 | Insert the rest of IIK's servers back in the rack, and resume production (NBL, Hansken, DSE) |
12-16.02.24 | Place all SkyLow servers back, and open for external users with servers in the outside part of K001. |
Event log
Time | Event |
---|---|
16.12.23 - 20:22 | The broken floor tile was discovered |
16.12.23 - ca. 23:00 | Agreed that we should remove some weight from R3, and contact help on Monday |
18.12.23 - ca. 09:00 | Contacted a company that will assess the damage, and come up with a plan to fix the floor |
18.12.23 - ca. 12:00 | Placed a steel beam under R3, to support it. Migrated all VMs from five of the compute nodes in R3, and removed them from the rack - meaning we are currently running on reduced capacity. |
20.12.23 | Visit from the carpenter company. Made an initial plan for what needed to be done. Decided that the steel beam would suffice for support. Little to no measured further "sinking". |
17.01.24 - 10:00 | Meeting with the carpenter. A plan was made for repairing the floor. They will build support framing between all the floor tile legs, and replace all necessary tiles. The carpenters will need two days, and we schedule two days for removing all servers, and one day to put everything back in after the floor is fixed. Meaning a total downtime of five days. |
18.01.24 - 13:00 | Received confirmation from the carpenter, that they can start the repair work on 7th of February. We accepted the offer. |
23.01.24 - 15:23 | Messaged all users about the planned downtime in week 6 |
...