| Outage start | Monday, July 11, 2016 3:30 p.m. |
| Expected end | Monday, July 11, 2016 5:50 p.m. |
Update: Connection to the authentication server has been reestablished, CHI@UC is now operational.
CHI@UC is temporarily unavailable due to a problem with our authentication server located at Chicago. We currently do not have an ETA on when the server will be available again.
| Outage start | Thursday, June 23, 2016 11 a.m. |
| Expected end | Thursday, June 23, 2016 2:25 p.m. |
Update: The issue has been resolved.
KVM@TACC is experiencing some issues with its networking infrastructure. Access to instances may not be possible. We expect to restore availability later today.
| Outage start | Friday, June 17, 2016 2 a.m. |
| Expected end | Tuesday, June 21, 2016 9:50 a.m. |
Update: CHI@UC has been restored. Thank you for your patience. If you experience any issue please open a ticket via our helpdesk.
We have received notice from the building housing the CHI resources at the University of Chicago that they will be performing power work starting on Friday, June 17th 2016.
| Outage start | Monday, May 09, 2016 3 a.m. |
| Expected end | Tuesday, May 10, 2016 3 a.m. |
REMINDER:
Dear Chameleon users,
We have received short notice from the building that they will be performing power work in the datacenter housing the CHI resources at the University of Chicago on Monday, May 9th 2016.
CHI@UC will be unavailable starting at 08:00 AM CST. Work is expected to last approximately 12 hours plus recovery time on our end. An all clear message will be sent out once the work has been completed.
NOTE: Instances may not be available after the maintenance period. We recommend that you snapshot your work ahead of time.
| Outage start | Tuesday, March 01, 2016 1 a.m. |
| Expected end | Tuesday, March 01, 2016 3 a.m. |
Update: The work has been completed.
In order to apply routine software updates, the Chameleon virtualization cluster at TACC (KVM@TACC) will be unavailable on Tuesday March 1, 2016 from 7:00 to 9:00 AM Central Time. During the work all API endpoints, the dashboard, and networking will be unavailable. Instances are not expected to be interrupted, but will not be accessible.
| Outage start | Monday, February 22, 2016 10:30 a.m. |
| Expected end | Monday, February 22, 2016 6:30 p.m. |
We discovered a configuration problem related to the upgrade of CHI@TACC which meant that since service was resumed on Friday, your instances could have been scheduled on different nodes than the ones you reserved. If during the week-end you gathered experiment results that require specific hardware, you should unfortunately discard them.
While we fixed this issue, we had have to terminate all active reservations and instances.
| Outage start | Thursday, February 18, 2016 8 a.m. |
| Expected end | Friday, February 19, 2016 3 p.m. |
Update: CHI@UC is now available as we have finished migrating services to a new server.
CHI@UC was scheduled to be unavailable for a short period of time from 08:00 AM on Thursday, February 18, 2016 in order to apply security updates and perform a small hardware maintenance. Due to hardware issues we needed to extend the maintenance.
| Outage start | Monday, February 15, 2016 12 a.m. |
| Expected end | Monday, February 22, 2016 12 a.m. |
CHI@TACC has been upgraded to OpenStack Liberty, and has been restored to service.
Users who use automation should note that the network ID used when booting nodes has changed, and how has the UUID 915853fe-10c5-4dac-a402-ef1ebc53e427.
| Outage start | Sunday, January 31, 2016 2 p.m. |
| Expected end | Monday, February 01, 2016 8 a.m. |
Update: The issue has been resolved.
KVM@TACC is temporarily unavailable due to a networking issue. We expect to restore availability later today.
| Outage start | Monday, February 08, 2016 3 a.m. |
| Expected end | Friday, February 12, 2016 6 p.m. |
We have reserved the entire bare-metal testbed at University of Chicago (CHI@UC) for a software upgrade from Monday, February 8 to Friday, February 12. This upgrade will bring exciting new capabilities to Chameleon users! Although we reserved resources for five days, we will release them as soon as we have successfully completed the upgrade process.