A brief overview of the Nimbus Infrastructure
The underlying infrastructure for the Nimbus system can be seen below:
Services offered in the cloud can change rapidly, an Nimbus has been designed with this in mind. We use blue-green
deployment, in order to allow rolling updates of the system with continuity of service. In essence there are two clusters, one active
and one inactive
. In order to ensure high availablity and increase resilience, on each cluster there are two login-nodes, and two schedulers.
As a user most of this will be unnoticable. The you will automatically be put onto one of the login nodes on the active cluster when you log onto the system.
The only time you may have to take action as a result of this infrastructure is if the active
cluster is switched. In which case you will get a message to the terminal informing you about the upcoming switch, and you will have to log out and back in in order to continue your work. Your jobs will continue to run, and you will not have to resubmit them.