Slurm Support: Difference between revisions

From HPCWIKI
Jump to navigation Jump to search
(Add categories: Linux, Reference)
(Fix: remove --- horizontal lines (7 removed))
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Slurm Support ==
{{Status
|status=Draft
|owner=Knowledge Agent
|last_update=2026-07-16
|review=Pending
}}
 
{{TOC}}
 
== Overview ==
 
Slurm Support에 대한 기술 문서입니다.
 
=== Summary ===
 
* 무엇인가? - Slurm Support
* 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
* 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시
 
 
== Purpose ==
 
이 문서가 존재하는 이유
 
* Goal: Slurm Support에 대한 기술 정보 제공
* Scope: Slurm Support의 개념, 사용법, 설정
* Non-goals: 다른 주제로의 확장
 
 
== Key Concepts ==
 
{| class="wikitable"
! Concept
! Description
! Related
|-
| Slurm Support
| HPC/서버 환경에서 중요한 기술 개념
| [[Linux]], [[Server]]
|}
 
 
== Detailed Explanation ==
 
* '''HPCMATE Co., LTD''' provides thermal optimized HPC, GPGPU hardware and HPC cluster solutions and covers frontline customer [[support]] as a authorized system integration partner of SchedMD.
* '''HPCMATE Co., LTD''' provides thermal optimized HPC, GPGPU hardware and HPC cluster solutions and covers frontline customer [[support]] as a authorized system integration partner of SchedMD.
* '''SchedMD''' is the core company behind the Slurm [[workload]] manager. The owners and employees of SchedMD have written over 90% of the Slurm code base. SchedMD also reviews and integrates contributions from others, distributes the Slurm code base and maintains the canonical version of Slurm.
* '''SchedMD''' is the core company behind the Slurm [[workload]] manager. The owners and employees of SchedMD have written over 90% of the Slurm code base. SchedMD also reviews and integrates contributions from others, distributes the Slurm code base and maintains the canonical version of Slurm.
=== What does Support include? ===
HPCMATE and SchedMD offers '''Level 3 Slurm support''', see the “Overview of Slurm Support". HPCMATE covers all level of Slurm support with direct supported by SchedMD especially for Level 3 Slurm support. When your cluster encounters a Level 3 Slurm workload manager issue or bug, then a support contract allows you to submit the issue to the HPCMATE and SchedMD team for successful resolution. When you submit the request we ask for the following information in order to ensure timely issue resolution.
HPCMATE and SchedMD offers '''Level 3 Slurm support''', see the “Overview of Slurm Support". HPCMATE covers all level of Slurm support with direct supported by SchedMD especially for Level 3 Slurm support. When your cluster encounters a Level 3 Slurm workload manager issue or bug, then a support contract allows you to submit the issue to the HPCMATE and SchedMD team for successful resolution. When you submit the request we ask for the following information in order to ensure timely issue resolution.
# The steps or script to reproduce to issue or bug.
# The steps or script to reproduce to issue or bug.
# A copy of your Slurm configuration files.
# A copy of your Slurm configuration files.
After we review the issue the engineering team
After we review the issue the engineering team
# Generates a fix, this can be anything from a configuration change to a patch.
# Generates a fix, this can be anything from a configuration change to a patch.
Line 14: Line 55:
# Submits the final resolution to the client. and for inclusion in the Slurm tree.
# Submits the final resolution to the client. and for inclusion in the Slurm tree.
Slurm support also includes configuration assistance for each supported cluster. This assistance is valuable when the cluster is initially being configured to use Slurm or when the cluster needs to be modified as requirements change. For each supported cluster you will be able to review your cluster requirements, operating environment and the organizational goals for the machine with a Slurm engineer and work with the engineer to optimize the configuration to your needs. Slurm support also will allow you to receive detailed answers directly from the Slurm Development team when you encounter complex Slurm questions.
Slurm support also includes configuration assistance for each supported cluster. This assistance is valuable when the cluster is initially being configured to use Slurm or when the cluster needs to be modified as requirements change. For each supported cluster you will be able to review your cluster requirements, operating environment and the organizational goals for the machine with a Slurm engineer and work with the engineer to optimize the configuration to your needs. Slurm support also will allow you to receive detailed answers directly from the Slurm Development team when you encounter complex Slurm questions.
=== Why should I sign up? ===
High performance computers typically come with expectations of high utilization from the end users and management in order to ensure a strong return on the investment. When bug or complex technical issue is encountered it can take days or even weeks to resolve the issue in house. However, when your system is covered by a support contract you can reach out to the Slurm engineering experts to get help resolving these complex issues.
High performance computers typically come with expectations of high utilization from the end users and management in order to ensure a strong return on the investment. When bug or complex technical issue is encountered it can take days or even weeks to resolve the issue in house. However, when your system is covered by a support contract you can reach out to the Slurm engineering experts to get help resolving these complex issues.
=== What should I expect? ===
You should expect to make comments like this anytime you get to work with the Slurm engineering team.
You should expect to make comments like this anytime you get to work with the Slurm engineering team.
* James Cuff, Assistant Dean for Research Computing at Harvard
* James Cuff, Assistant Dean for Research Computing at Harvard
Line 23: Line 61:
**Patch within a day (on aSaturday!) In prod this morning!
**Patch within a day (on aSaturday!) In prod this morning!
**https://twitter.com/jamesdotcuff/status/392325342351732736
**https://twitter.com/jamesdotcuff/status/392325342351732736
* Colin McMurtrie, Head of Systems, Swiss National Supercomputing Centre
* Colin McMurtrie, Head of Systems, S... [내용 계속]
**"When we embarked upon our mission to port SLURM to our Cray XT and XE systems, we discovered firsthand the high quality software engineering that has gone into the creation of this product. From its very core SLURM has been designed to be extensible and flexible. Moreover, as our work progressed, we discovered the high level of technical expertise possessed by SchedMD who was very quick to respond to our questions with insightful advice, suggestions and clarifications. In the end we arrived at a solution that more than satisfied our needs. The project was so successful we have now migrated all our production science systems to Slurm, including our 20 cabinet Cray XT5 system. The ease with which we have made this transition is testament to the robustness and high quality of the product but also to the nofuss installation and configuration procedure and the high quality documentation. We have no qualms about recommending SLURM to any facility, large or small, who wish to make the break from the various commercial options available today"
 
 
== Best Practices ==
 
* 최신 버전 사용 권장
* 공식 문서 참고
* 테스트 환경에서 먼저 검증
 
 
== References ==
 
* [https://wiki.hpcmate.com Slurm Support]


== Overview of Slurm Support ==
* Level 1 Support (HPCMATE)
:Activities performed in response to an initial notification or awareness of a suspected problem.
# Problem and/or bug validation as a Slurm related issue.
# Review of a symptoms/solutions database for known resolutions.
# Research to determine if problem is already reported in a Slurm issue tracking database.
# Develop a complete and welldescribed report of the problem.


* Level 2 Support (HPCMATE)
== Related Pages ==
:Activities performed following the completion of Level 1 support if resolution is not achieved.
# Make best efforts to reproduce and diagnose the problem.
# Make best efforts to resolve or reduce severity of the problems.


* Level 3 Support (HPCMATE & SchedMD)
* [[Linux]]
:Activities following the completion of Level 1 and 2 support without successful resolution.
* [[Server]]
# Supply successful problem resolution such as a bug fix or configuration change, where problem is reproducible.
* [[Hardware]]
# Validate any fixes made by conducting regression testing.
* [[Network]]
# Develop additional test cases, where applicable, as a result of discovery of root cause.
# Communicate steps of action or resolution along with any code changes and testing results to client.
# Submit final resolution to the client and for inclusion in the Slurm tree.


== Severity Level and Response Commitments ==
When a problem or question is submitted the client will specify a severity level based upon the following criteria.
=== Severity 1 - Major Impact ===
A Severity 1 issue occurs when there is a continued system outage that affects a large set of end users. The system is down and nonfunctional due to Slurm problem(s) and no procedural workaround exists.
* Initial Response 2 Hours (During standard work hours)
* Status Updates Daily
* Work Schedule Continuous


=== Severity 2 – High Impact ===
[[Category:Server]]
A Severity 2 issue is a highimpact problem that is causing sporadic outages or is consistently encountered by end users with adverse impact to end user interaction with the system.
== Knowledge Graph ==
* Initial Response 1 Business Day
* Status Updates Weekly
* Work Schedule Workday


=== Severity 3 Medium Impact ===
Related
A Severity 3 issue is a mediumtolow impact problem that includes partial noncritical loss of system access or which impairs some operations on the system but allows the end user to continue to function on the system with workarounds.
* Initial Response 3 Business Day
* Status Updates Monthly
* Work Schedule Workday


=== Severity 4 – Minor Issues ===
→ [[Scheduler]]
A Severity 4 issue is a minor issue with limited or no loss in functionality within the customer environment. Severity 4 issues may also be used for recommendations for future product enhancements or modifications.
→ [[HPC]]
* Initial Response (during normal work hours) As available
→ [[Cluster]]
* Status Updates As available
* Work Schedule As available
[[Category:Linux]]


[[Category:Reference]]
[[Category:Reference]]

Latest revision as of 11:30, 17 July 2026

Template:Status

Template:TOC

Overview

Slurm Support에 대한 기술 문서입니다.

Summary

  • 무엇인가? - Slurm Support
  • 왜 필요한가? - HPC 및 서버 환경에서 필수 개념
  • 언제 사용하는가? - 서버 구성, 성능 튜닝, 문제 해결 시


Purpose

이 문서가 존재하는 이유

  • Goal: Slurm Support에 대한 기술 정보 제공
  • Scope: Slurm Support의 개념, 사용법, 설정
  • Non-goals: 다른 주제로의 확장


Key Concepts

Concept Description Related
Slurm Support HPC/서버 환경에서 중요한 기술 개념 Linux, Server


Detailed Explanation

  • HPCMATE Co., LTD provides thermal optimized HPC, GPGPU hardware and HPC cluster solutions and covers frontline customer support as a authorized system integration partner of SchedMD.
  • SchedMD is the core company behind the Slurm workload manager. The owners and employees of SchedMD have written over 90% of the Slurm code base. SchedMD also reviews and integrates contributions from others, distributes the Slurm code base and maintains the canonical version of Slurm.

HPCMATE and SchedMD offers Level 3 Slurm support, see the “Overview of Slurm Support". HPCMATE covers all level of Slurm support with direct supported by SchedMD especially for Level 3 Slurm support. When your cluster encounters a Level 3 Slurm workload manager issue or bug, then a support contract allows you to submit the issue to the HPCMATE and SchedMD team for successful resolution. When you submit the request we ask for the following information in order to ensure timely issue resolution.

  1. The steps or script to reproduce to issue or bug.
  2. A copy of your Slurm configuration files.

After we review the issue the engineering team

  1. Generates a fix, this can be anything from a configuration change to a patch.
  2. Validates the fix by conducting regression testing.
  3. Develops additional test cases, where applicable, as a result of discovery of root cause.
  4. Communicates steps of action or resolution along with any code changes and testing results to the client.
  5. Submits the final resolution to the client. and for inclusion in the Slurm tree.

Slurm support also includes configuration assistance for each supported cluster. This assistance is valuable when the cluster is initially being configured to use Slurm or when the cluster needs to be modified as requirements change. For each supported cluster you will be able to review your cluster requirements, operating environment and the organizational goals for the machine with a Slurm engineer and work with the engineer to optimize the configuration to your needs. Slurm support also will allow you to receive detailed answers directly from the Slurm Development team when you encounter complex Slurm questions. High performance computers typically come with expectations of high utilization from the end users and management in order to ensure a strong return on the investment. When bug or complex technical issue is encountered it can take days or even weeks to resolve the issue in house. However, when your system is covered by a support contract you can reach out to the Slurm engineering experts to get help resolving these complex issues. You should expect to make comments like this anytime you get to work with the Slurm engineering team.


Best Practices

  • 최신 버전 사용 권장
  • 공식 문서 참고
  • 테스트 환경에서 먼저 검증


References


Related Pages

Knowledge Graph

Related

→ Scheduler → HPC → Cluster

Retrieved from "http://wiki.hpcmate.com/index.php?title=Slurm_Support&oldid=3450"