generated from sig_core/wiki-template
init-pages #8
@ -29,17 +29,25 @@
|
|||||||
## Discussions:
|
## Discussions:
|
||||||
|
|
||||||
Greg: suggesting to have our own slurm, apptainer, singulatory, Warewulf
|
Greg: suggesting to have our own slurm, apptainer, singulatory, Warewulf
|
||||||
|
|
||||||
Greg: We can reach to DDN about anything related to Luster
|
Greg: We can reach to DDN about anything related to Luster
|
||||||
|
|
||||||
Sherif: Suggesting to start building packages
|
Sherif: Suggesting to start building packages
|
||||||
|
|
||||||
Nick: To build the community we need to start looking into documentation and forums
|
Nick: To build the community we need to start looking into documentation and forums
|
||||||
|
|
||||||
Stack: we need to be careful and have strong justification for rebuilding stuff that exists in Epel
|
Stack: we need to be careful and have strong justification for rebuilding stuff that exists in Epel
|
||||||
|
|
||||||
Greg: asked how HPC centre prefer to manage / or already managing their slurm setup
|
Greg: asked how HPC centre prefer to manage / or already managing their slurm setup
|
||||||
|
|
||||||
Few members mentioned one of the following two methods:
|
Few members mentioned one of the following two methods:
|
||||||
* Keep upgrading on minor version of slurm
|
* Keep upgrading on minor version of slurm
|
||||||
* Keep upgrading on minor version of slurm then a major upgrade in a scheduled maintains window
|
* Keep upgrading on minor version of slurm then a major upgrade in a scheduled maintains window
|
||||||
|
|
||||||
Greg and Nick: adding major-minor version in package name something like python2/3
|
Greg and Nick: adding major-minor version in package name something like python2/3
|
||||||
|
|
||||||
Sherif: Asking about Testing methodology with testing team
|
Sherif: Asking about Testing methodology with testing team
|
||||||
|
|
||||||
Stack: They hope at some point they are able to test all sigs and working on getting OpenQA build for this
|
Stack: They hope at some point they are able to test all sigs and working on getting OpenQA build for this
|
||||||
|
|
||||||
## Action items:
|
## Action items:
|
||||||
|
@ -12,15 +12,24 @@
|
|||||||
|
|
||||||
## Discussions:
|
## Discussions:
|
||||||
Chris: Are we willing to support all openHPC stack or just the modules and how we imagine achieving this?
|
Chris: Are we willing to support all openHPC stack or just the modules and how we imagine achieving this?
|
||||||
|
|
||||||
Jeremy: Clear a bit of distro related stuff from openHPC would be great such as automake / autoconf
|
Jeremy: Clear a bit of distro related stuff from openHPC would be great such as automake / autoconf
|
||||||
|
|
||||||
Stack: We need to have a base line so people can start use rocky on HPC and make Rocky accessible
|
Stack: We need to have a base line so people can start use rocky on HPC and make Rocky accessible
|
||||||
|
|
||||||
Chris: A Demo / technical talk in 4 weeks
|
Chris: A Demo / technical talk in 4 weeks
|
||||||
|
|
||||||
Chris: Are we going to focus on 8 and 9?
|
Chris: Are we going to focus on 8 and 9?
|
||||||
|
|
||||||
Stack and Chris, would be great if we can focus on 9
|
Stack and Chris, would be great if we can focus on 9
|
||||||
|
|
||||||
Sherif: I hope we can do both but with 9 in the spotlight "this needs to be a SIG decision"
|
Sherif: I hope we can do both but with 9 in the spotlight "this needs to be a SIG decision"
|
||||||
|
|
||||||
Stack: Question, if we start moving openHPC within HPC sig are they going support more distros, we don't want to break packages for other EL distros
|
Stack: Question, if we start moving openHPC within HPC sig are they going support more distros, we don't want to break packages for other EL distros
|
||||||
|
|
||||||
Chris: so far testing on Rocky as the only supported EL distro
|
Chris: so far testing on Rocky as the only supported EL distro
|
||||||
|
|
||||||
|
|
||||||
## Action items:
|
## Action items:
|
||||||
* Get a demo / technical talk after 4 weeks "Sherif can arrange that with Chris"
|
* Get a demo / technical talk after 4 weeks "Sherif can arrange that with Chris"
|
||||||
* 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"
|
* 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"
|
||||||
|
@ -9,15 +9,25 @@
|
|||||||
|
|
||||||
## Discussions:
|
## Discussions:
|
||||||
Getting toolchains outside of openHPC such as automake
|
Getting toolchains outside of openHPC such as automake
|
||||||
|
|
||||||
Greg: We need to talk if we need to have a generic SIG for toolchains
|
Greg: We need to talk if we need to have a generic SIG for toolchains
|
||||||
|
|
||||||
Greg: We need to look into adding more release packages such as intel compiler
|
Greg: We need to look into adding more release packages such as intel compiler
|
||||||
|
|
||||||
Brain storm ideas about optimizing binaries
|
Brain storm ideas about optimizing binaries
|
||||||
|
|
||||||
David: What would be the interest of having a light weight kernel for HPC
|
David: What would be the interest of having a light weight kernel for HPC
|
||||||
|
|
||||||
Jeremy: mentioning intel light weight kernel https://github.com/intel/mos
|
Jeremy: mentioning intel light weight kernel https://github.com/intel/mos
|
||||||
|
|
||||||
Chris: asking if there is any benchmark, hard numbers between shipped kernel and light weight kernel, so far, nothing solid
|
Chris: asking if there is any benchmark, hard numbers between shipped kernel and light weight kernel, so far, nothing solid
|
||||||
|
|
||||||
Sherif: Slurm now is build but not in standard path and we agreed we are going to move standard path
|
Sherif: Slurm now is build but not in standard path and we agreed we are going to move standard path
|
||||||
|
|
||||||
Greg: make sure you have the provide type
|
Greg: make sure you have the provide type
|
||||||
|
|
||||||
Chris: also make sure that downgrade works
|
Chris: also make sure that downgrade works
|
||||||
|
|
||||||
Greg and Chris, we can also contribute to openHPC documentation
|
Greg and Chris, we can also contribute to openHPC documentation
|
||||||
|
|
||||||
## Action items:
|
## Action items:
|
||||||
|
@ -1,4 +1,4 @@
|
|||||||
# SIG/HPC meeting 2023-06-01
|
# SIG/HPC meeting 2023-06-15
|
||||||
|
|
||||||
## Attendees:
|
## Attendees:
|
||||||
* Chris Simmons
|
* Chris Simmons
|
||||||
@ -13,12 +13,19 @@
|
|||||||
## Discussions:
|
## Discussions:
|
||||||
|
|
||||||
Chris gave a quick demo about openHPC / presentation
|
Chris gave a quick demo about openHPC / presentation
|
||||||
|
|
||||||
Jeremy sent the packages
|
Jeremy sent the packages
|
||||||
|
|
||||||
Greg: asked how the SIG's slurm is compatible with openHPC
|
Greg: asked how the SIG's slurm is compatible with openHPC
|
||||||
|
|
||||||
Sherif needs to look at openHPC slurm packages
|
Sherif needs to look at openHPC slurm packages
|
||||||
|
|
||||||
Chris we need to look on how to build easybuild and look into how to improve it
|
Chris we need to look on how to build easybuild and look into how to improve it
|
||||||
|
|
||||||
Chris and Greg talking about if there is any standard that explains how to build systems compatible with each others, openHPC does follow best practices from different entities
|
Chris and Greg talking about if there is any standard that explains how to build systems compatible with each others, openHPC does follow best practices from different entities
|
||||||
|
|
||||||
Chris provided https://github.com/holgerBerger/hpc-workspace which now a part of openHPC
|
Chris provided https://github.com/holgerBerger/hpc-workspace which now a part of openHPC
|
||||||
|
|
||||||
Sherif mentioned, forums category is now in place https://forums.rockylinux.org/c/sig/hpc/61
|
Sherif mentioned, forums category is now in place https://forums.rockylinux.org/c/sig/hpc/61
|
||||||
|
|
||||||
## Action items:
|
## Action items:
|
||||||
|
Loading…
Reference in New Issue
Block a user