Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HideElements
breadcrumbtrue
titletrue
spacelogotrue

<< Zurück zur Dokumentationsstartseite

Lrz box
Picture/images/lrz/Icon_HPC.png
Heading1High Performance Computing

System Status (see also: Access and Overview of HPC Systems)

Status
colourGreen
= fully operational
Status
colourYellow
= operational but experiencing problems (see messages below)
Status
colourRed
= not available


SuperMUC Phase 2

(only available until end of 2019)

Status
colourYellow
titleEND OF LIFE

login: hw.supermuc.lrz.de

Status
colourGreen
titleUP

File Systems:
HOME:
WORK:
SCRATCH:

Important: Please migrate data to SuperMUC-NG asap! 


Status
colourYellow
titleEND OF LIFE

Status
colourYellow
titleEND OF LIFE

Status
colourGreen
titleUP

Queues: micro, general, test, big

Status
colourGreen
titleUP

Detailed node status: 

Status
colourGreen
titleUP

login: skx.supermuc.lrz.de

Status
colourGreen
titleUP

File Systems: 
HOME:
WORK:
SCRATCH:
DSS:


Status
colourGreen
titleUP

Status
colourGreen
titleUP

Status
colourGreen
titleUP

Status
colourGreen
titleup

Partitions/Queues: 
micro, fat, general, large


Status
colourGreen
titleUP

Globus Online File Transfer: 

Status
colourGreen
titleUP

Detailed node status: 

Details:



Submit an Incident Ticket for SuperMUC-NG 



Linux Cluster

 

login: lxlogin(5, 6, 7).lrz.de

Status
colourGreen
titleUP

lxlogin(8, 10).lrz.de

Status
colourGreen
titleUP



Partitions/Queue:

mpp2_batch

Status
colourGreen
titleUP

mpp2_inter

Status
colourGreen
titleUP

serial

Status
colourGreen
titleUP

mpp3_batch

kcs

Status
colourYellow
titlew/o SCRATCH

Status
colourYellow
titlew/o SCRATCH

mpp3_inter
teramem_inter
ivymuc

Status
colourYellow
titlew/o SCRATCH

Status
colourGreen
titleUP

Status
colourGreen
titleUP



Detailed node status: 

Details:

 


Submit an Incident Ticket for the Linux Cluster



Compute Cloud and other HPC Systems

 

Compute Cloud: (https://cc.lrz.de)

Status
colourGreen
titleUP

Open Nebula Coud (https://www.cloud.mwn.de)

Status
colourYellow
titleend of life

GPU Cloud (https://datalab.srv.lrz.de)

Status
colourGreen
titleUP

DGX-1

Status
colourGreen
titleup

DGX-1v

Status
colourGreen
titleUP

RStudio Server (https://www.rstudio.lrz.de)

Status
colourGreen
titleUP







Details:



Submit an Incident Ticket for the Compute Cloud



Messages of the Day

see also: Aktuelle LRZ-Informationen / News from LRZ


Messages for SuperMUC

 Scheduled Maintenance:

November 27, 2019, at 8:00 am

Important: Please speedily migrate data to SuperMUC-NG! 
skx-arch.supermuc.de is not yet available before early January, 2020





Messages for Linux Cluster

 SCRATCH/GPFS on CoolMUC-2

Today (from morning until early afternoon), the SCRATCH file system was not available. Within that timeframe, jobs may have crashed. SCRATCH file system is available againwas made available again.

Short lasting outages of SCRATCH have been observed today on CoolMUC-2 and hosted cluster systems as well.

 SCRATCH unavailable on CoolMUC-3

To avoid file system crashes, we have decided to unmount SCRATCH from all systems associated with CoolMUC-3 for now. We expect to revert this measure again at the next scheduled maintenance .

 End of service for NAS systems

NAS paths will be taken offline at the beginning of January, 2020. Please contact the Service Desk for outstanding data migration issues.

 Maintenance

November 27, 2019, at 8:00 am

https://www.lrz.de/aktuell/ali00807.html

: HOME directory path will change

You will find all HOME data in the new DSS HOME area, data migration will be performed by LRZ (unless you are specifically notified that you need to perform HOME data migration yourself). For emergency recoveries, the legacy NAS area (pointed to by the HOME_LEGACY variable) will remain available in read-only mode until the end of the year.

Following action is required on your part:  Make necessary adjustments to (job) scripts and configuration data to account for the changes in path names. LRZ strongly recommends using relative path names because this minimizes the required work. 

Examples: 

NAS PROJECT path is mounted read-only

between and  

DSS PROJECT now available on HPC systems:

Following action is required on your part:

Migrate data from the legacy NAS area (pointed to by the PROJECT_LEGACY variable) to the new DSS area. LRZ strongly advises to get rid of unneeded data sets, and/or archive data sets to tape.

Step-by-step procedure for migration:

  1. On any cluster login node, issue the command
    dssusrinfo all
    This will list paths to accessible containers, as well as quota information etc.
  2. Edit your shell profile and set the PROJECT and/or WORK variable to a
    suitable path value based on the above output, typically one of the DSS
    paths with your account name appended to it.
  3. Use the cp or rsync or tar command to migrate your data from
    PROJECT_LEGACY to the new storage area.
  4. If your scripts use absolute path names instead of the PROJECT or
    WORK variable, they need appropriate updates

https://www.lrz.de/aktuell/ali00788.html

User e-Mail notification of DSS PROJECT link

Following actions are required on your part:

  1. Confirm the e-Mail invitation to validate your access,
  2. After the Linux Cluster maintenance (see below), store path information in an environment variable on the Cluster (e.g. by setting the PROJECT variable in ~/.bashrc).

One this is done, migrating data from NAS PROJECT to DSS PROJECT can start

Please read the change description on how to handle the significant changes to the Linux cluster configuration performed end of September, 2019




Messages for Cloud and other HPC systems

The OpenNebula Compute Cloud was decommissioned on

                                        




More Links

Children Display