generated from sig_core/wiki-template
Compare commits
2 Commits
81f7428fa2
...
b76f5c001f
Author | SHA1 | Date | |
---|---|---|---|
b76f5c001f | |||
82873c9759 |
82
docs/events/meeting-notes/2023-07-27.md
Normal file
82
docs/events/meeting-notes/2023-07-27.md
Normal file
@ -0,0 +1,82 @@
|
|||||||
|
# SIG/HPC meeting 2023-07-27
|
||||||
|
|
||||||
|
## Attendees:
|
||||||
|
* Sherif
|
||||||
|
* Jeremy Siadal
|
||||||
|
* Stack
|
||||||
|
* Scott Groel
|
||||||
|
* Gregory Kurtzer
|
||||||
|
|
||||||
|
|
||||||
|
## Discussions:
|
||||||
|
Chris, talked about the slurm system unit bug in upstream
|
||||||
|
|
||||||
|
Sherif, asked about the openQA status
|
||||||
|
|
||||||
|
Stack, they are working on that and still improving it
|
||||||
|
|
||||||
|
Sherif, asked about the PMIX support and how to do it
|
||||||
|
|
||||||
|
Jeremy, it is a bit more complex than what it seems but worth doing
|
||||||
|
|
||||||
|
David, what is the added value from moving the PMIX to newer version
|
||||||
|
|
||||||
|
Jeremy, we need to look at the user base and see if this is needed
|
||||||
|
|
||||||
|
Stack, asks about PMIX and what it is
|
||||||
|
|
||||||
|
David, the extension for pmix is more needed when you implement on scale and performance is an issue within slurm
|
||||||
|
|
||||||
|
Greg, we can have pmix into the SIG, that's not a bad idea
|
||||||
|
|
||||||
|
Jeremy, we will also need runtime aspects of it
|
||||||
|
|
||||||
|
David, yes we will need both
|
||||||
|
|
||||||
|
Jeremy, mentioned a package they would like to have into SIG/HPC they will send it to us
|
||||||
|
|
||||||
|
Greg, will reach out to openPBS and cloud charly
|
||||||
|
|
||||||
|
## Action items:
|
||||||
|
* Sherif: Reach out to jose-d about pmix - Done, no feedback yet -
|
||||||
|
* Greg: to reach out to openPBS and clout charly
|
||||||
|
* Sherif: To update slurm32 to latest
|
||||||
|
|
||||||
|
## Old business:
|
||||||
|
|
||||||
|
## 2023-07-13:
|
||||||
|
* Sherif needs to update the wiki - Done
|
||||||
|
* Sherif to look into MPI stack
|
||||||
|
* Chris will send Sherif a link with intro
|
||||||
|
|
||||||
|
## 2023-06-29:
|
||||||
|
* Sherif release slurm23 sources - Done
|
||||||
|
* Stack and Sherif working on the HPC list
|
||||||
|
* Sherif email Jeremy, the slurm23 source URL - Done
|
||||||
|
|
||||||
|
## 2023-06-15:
|
||||||
|
* Sherif to look int openHPC slurm spec file - Pending on Sherif
|
||||||
|
* We need to get lists of centres and HPC that are moving to Rocky to make a blog post and PR
|
||||||
|
|
||||||
|
## 2023-06-01:
|
||||||
|
* Get a list of packages from Jeremy to pick up from openHPC - Done
|
||||||
|
* Greg / Sherif talk in Rocky / RESF about generic SIG for common packages such as chaintools
|
||||||
|
* Plan the openHPC demo Chris / Sherif - Done
|
||||||
|
* Finlise the slurm package with naming / configuration - Done
|
||||||
|
|
||||||
|
## 2023-05-18:
|
||||||
|
* Get a demo / technical talk after 4 weeks "Sherif can arrange that with Chris" - Done
|
||||||
|
* Getting a list of packages that openHPC would like to move to distros "Jeremy will be point of contact if we need those in couple of weeks" - Done
|
||||||
|
|
||||||
|
## 2023-05-04
|
||||||
|
* Start building slurm - On going, a bit slowing down with R9.2 and R8.8 releases, however packages are built, some minor configurations needs to be fixed -
|
||||||
|
* Start building apptainer - on hold -
|
||||||
|
* Start building singulartiry - on hold -
|
||||||
|
* Start building warewulf - on hold -
|
||||||
|
* Sherif: check about forums - done, we can have our own section if we want, can be discussed over the chat -
|
||||||
|
|
||||||
|
## 2023-04-20
|
||||||
|
* Reach out to other communities “Greg” - on going -
|
||||||
|
* Reaching out for different sites that uses Rocky for HPC “Stack will ping few of them and others as well -Group effort-”
|
||||||
|
* Reaching out to hardware vendors - nothing done yet -
|
||||||
|
* Statistic / public registry for sites / HPC to add themselves if they want - nothing done yet -
|
Loading…
Reference in New Issue
Block a user