sig_hpc/wiki
5
0
Fork 0
generated from sig_core/wiki-template
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: sig_hpc:6e8daa328a07ac57d4e7b7711fc8793c64b04b15
Branches Tags
sig_hpc:main
sig_hpc:gh-pages
sig_hpc:meeting/2024-02-22
sig_hpc:meeting-nov15
sig_hpc:init-pages
sig_hpc:setup
..
compare: sig_hpc:6bc29dce9ed96ccf378c3a416f54840877d7ad0d
Branches Tags
sig_hpc:gh-pages
sig_hpc:main
sig_hpc:meeting/2024-02-22
sig_hpc:meeting-nov15
sig_hpc:init-pages
sig_hpc:setup

2 Commits
6e8daa328a ... 6bc29dce9e

Author SHA1 Message Date
Sherif Nagy
6bc29dce9e Merge pull request 'Fixing type and adding old action items' (#4) from init-pages into main
All checks were successful
mkdocs build / build (push) Successful in 40s
Details 
Reviewed-on: #4
 2023-05-18 20:20:07 +00:00
Sherif Nagy
e31cf98718
Fixing type and adding old action items 2023-05-18 21:15:04 +01:00
2 changed files with 13 additions and 3 deletions
Show Stats Expand all files Collapse all files

4
docs/events/meeting-notes/2023-04-20.md
View File

@ -57,12 +57,12 @@ actually have to leave now, but, if we make some sort of toolkit, it has to be q
## Remarks: ## Remarks:
* A point raised, should be rebuild some packages that area already in Epel or not and if we shall have a higher priority on our repo or not * A point raised, should be rebuild some packages that area already in Epel or not and if we shall have a higher priority on our repo or not
* We need to think more about conflicts with other SIGs like luster and sig storage * We need to think more about conflicts with other SIGs like lustre and sig storage
## Action items: ## Action items:
* List of applications “Thread on MM to post pkgs” * List of applications “Thread on MM to post pkgs”
* Building blocks which are each pkg as a building block such as luster, openHPC, slurm, etc… * Building blocks which are each pkg as a building block such as lustre, openHPC, slurm, etc…
* Reach out to other communities “Greg” * Reach out to other communities “Greg”
* Reaching out for different sites that uses Rocky for HPC “Stack will ping few of them and others as well -Group effort-” * 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 * Reaching out to hardware vendors

12
docs/events/meeting-notes/2023-05-04.md
View File

@ -13,7 +13,7 @@
## Package lists ## Package lists
* Slurm - Epel * Slurm - Epel
* Apptainer - Epel * Apptainer - Epel
* Luster - luster.org , no server for el9 * Lustre - lustre.org , no server for el9
* Warewulf - HPCNG github only el8 * Warewulf - HPCNG github only el8
* Easybuild * Easybuild
* OpenHPC * OpenHPC
@ -51,3 +51,13 @@ Stack: They hope at some point they are able to test all sigs and working on get
* Greg reach out for OpenHPC - done * Greg reach out for OpenHPC - done
* Sherif: check about fourms * Sherif: check about fourms
## Old business:
* List of applications “Thread on MM to post pkgs” - We have an idea now of which packages we need to build -
* Building blocks which are each pkg as a building block such as lustre, openHPC, slurm, etc… - We have an idea of what we need to do -
* 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 -
* Meeting will be bi-weekly “Tantive Thursday 9:00PM UTC” - Agreed -
* Documentations - Wiki is in place but still need some work -