Difference between revisions of "Application life-cycle"

From ScientificComputing
Jump to: navigation, search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>==Next quarterly change==
 
August 2017</noinclude>
 
 
 
<noinclude>==Introduction==</noinclude>
 
<noinclude>==Introduction==</noinclude>
Based on application experience on Brutus we offer, besides the currently '''supported''' versions, two new categories of modules for '''new''' and '''legacy''' versions. Due to dependencies between compilers, libraries and applications, changes to the applications and the corresponding modules need to be synchronized and will be done on a quarterly basis.
+
Based on application experience on Brutus we offer, besides the currently '''supported''' versions, two new categories of modules for '''new''' and '''legacy''' versions on the Euler cluster. Due to dependencies between compilers, libraries and applications, changes to the applications and the corresponding modules need to be synchronized.
  
 
<includeonly>====Life-cycle of an application====</includeonly><noinclude>==Life-cycle of an application==</noinclude>
 
<includeonly>====Life-cycle of an application====</includeonly><noinclude>==Life-cycle of an application==</noinclude>
Line 12: Line 9:
 
Applications that have passed all tests and are deemed ready for production (stable, bug-free, compatible with LSF, etc.) will be moved to the '''supported''' category in the next quarterly update.
 
Applications that have passed all tests and are deemed ready for production (stable, bug-free, compatible with LSF, etc.) will be moved to the '''supported''' category in the next quarterly update.
  
Applications that have become obsolete (no longer supported by the vendor, superseded by new versions with more functionality, etc.) will be moved to the '''legacy''' category in the next quarterly update. For these modules the HPC group can only provide '''limited support'''. Legacy modules are not visible by default. If you still need to use them, you will need to load the '''legacy''' module first:
+
Applications that have become obsolete (no longer supported by the vendor, superseded by new versions with more functionality, etc.) will be moved to the '''legacy''' category. For these modules the HPC group can only provide '''limited support'''. Legacy modules are not visible by default. If you still need to use them, you will need to load the '''legacy''' module first:
  
 
  module load legacy
 
  module load legacy
  
Applications that are known to be buggy, have become redundant or whose license have expired will be removed in the next quarterly update. If you still need to use them, please contact {{Cluster_support}}.
+
Applications that are known to be buggy, have become redundant or whose license have expired will be removed. If you still need to use them, please contact {{Cluster_support}}.
  
 
<includeonly>====User notification====</includeonly><noinclude>==User notification==</noinclude>
 
<includeonly>====User notification====</includeonly><noinclude>==User notification==</noinclude>
The HPC group updates the module categories on a '''quarterly''' basis (February, May, August, November). Therefore the '''Application life-cycle''' page contains a '''table''' listing all applications that are available on Brutus as well as the modifications that we plan to apply at the next quarterly change. The users will receive a reminder, '''one week''' prior to the update of the categories that will also contain information about the most important changes.
+
The HPC group updates the module categories on a regular basis. Therefore the '''Application life-cycle''' page contains a '''table''' listing all applications that are available on Euler as well as the modifications that we plan to apply at the next change. The users will receive a reminder, '''one week''' prior to the update of the categories that will also contain information about the most important changes.
  
 
<includeonly>====Application tables====</includeonly><noinclude>==Application tables==</noinclude>
 
<includeonly>====Application tables====</includeonly><noinclude>==Application tables==</noinclude>
We have listed all available modules on the different HPC clusters in separate tables, which also contain a special formatting that indicate actions taken in the next quarterly change
+
We have listed all available modules on the different HPC clusters in separate tables, which also contain a special formatting that indicate actions taken in the next change. Please note that the application table for Leonhard does not contain the different module categories as we have switched from manual installations to using the supercomputing package manager (SPACK) and also switched from environment modules to lmod modules.
  
*[[Brutus_applications|Modules on Brutus]]
+
*[[Euler_applications|Modules on Euler]]
  
*[[Euler_applications|Modules on Euler]]
+
*[[Leonhard_applications_and_libraries|Modules on Leonhard]]

Latest revision as of 11:15, 15 October 2018

Introduction

Based on application experience on Brutus we offer, besides the currently supported versions, two new categories of modules for new and legacy versions on the Euler cluster. Due to dependencies between compilers, libraries and applications, changes to the applications and the corresponding modules need to be synchronized.

Life-cycle of an application

Modules for new or experimental versions of an application/library/compiler first appear in the new module category, where we provide a partial support matrix. Specific compiler/library combinations can be requested by shareholders. New modules are not visible by default. If you would like to see which new versions are available or try them out, you will need to load the new module first:

module load new

Applications that have passed all tests and are deemed ready for production (stable, bug-free, compatible with LSF, etc.) will be moved to the supported category in the next quarterly update.

Applications that have become obsolete (no longer supported by the vendor, superseded by new versions with more functionality, etc.) will be moved to the legacy category. For these modules the HPC group can only provide limited support. Legacy modules are not visible by default. If you still need to use them, you will need to load the legacy module first:

module load legacy

Applications that are known to be buggy, have become redundant or whose license have expired will be removed. If you still need to use them, please contact cluster support.

User notification

The HPC group updates the module categories on a regular basis. Therefore the Application life-cycle page contains a table listing all applications that are available on Euler as well as the modifications that we plan to apply at the next change. The users will receive a reminder, one week prior to the update of the categories that will also contain information about the most important changes.

Application tables

We have listed all available modules on the different HPC clusters in separate tables, which also contain a special formatting that indicate actions taken in the next change. Please note that the application table for Leonhard does not contain the different module categories as we have switched from manual installations to using the supercomputing package manager (SPACK) and also switched from environment modules to lmod modules.