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

Deployed 843bbbc with MkDocs version: 1.4.3

Browse Source
This commit is contained in:
2023-06-19 10:08:59 +00:00
parent 2ecd1723a9
commit 5e8c24917f
13 changed files with 56 additions and 56 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
404.html
View File

@ -445,7 +445,7 @@
<li class="md-nav__item">
<a href="/HPC.rocky.page/events/meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
about/index.html
View File

@ -459,7 +459,7 @@
<li class="md-nav__item">
<a href="../events/meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
contact/index.html
View File

@ -466,7 +466,7 @@
<li class="md-nav__item">
<a href="../events/meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
events/index.html
View File

@ -466,7 +466,7 @@
<li class="md-nav__item">
<a href="meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
events/meeting-notes/2023-04-20/index.html
View File

@ -532,7 +532,7 @@
<li class="md-nav__item">
<a href="../2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

24
events/meeting-notes/2023-05-04/index.html
View File

@ -525,7 +525,7 @@
<li class="md-nav__item">
<a href="../2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>
@ -595,18 +595,18 @@
* sstack
</code></pre>
<h2 id="discussions">Discussions:<a class="headerlink" href="#discussions" title="Permanent link">&para;</a></h2>
<p>Greg: suggesting to have our own slurm, apptainer, singulatory, Warewulf
Greg: We can reach to DDN about anything related to Luster
Sherif: Suggesting to start building packages
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
Greg: asked how HPC centre prefer to manage / or already managing their slurm setup
Few members mentioned one of the following two methods:
<p>Greg: suggesting to have our own slurm, apptainer, singulatory, Warewulf</p>
<p>Greg: We can reach to DDN about anything related to Luster</p>
<p>Sherif: Suggesting to start building packages</p>
<p>Nick: To build the community we need to start looking into documentation and forums</p>
<p>Stack: we need to be careful and have strong justification for rebuilding stuff that exists in Epel</p>
<p>Greg: asked how HPC centre prefer to manage / or already managing their slurm setup</p>
<p>Few members mentioned one of the following two methods:
* Keep upgrading on minor version of slurm
* Keep upgrading on minor version of slurm then a major upgrade in a scheduled maintains window</p>
<p>Greg and Nick: adding major-minor version in package name something like python2/3
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</p>
<p>Greg and Nick: adding major-minor version in package name something like python2/3</p>
<p>Sherif: Asking about Testing methodology with testing team</p>
<p>Stack: They hope at some point they are able to test all sigs and working on getting OpenQA build for this</p>
<h2 id="action-items">Action items:<a class="headerlink" href="#action-items" title="Permanent link">&para;</a></h2>
<pre><code>* Start building slurm
* Start building apptainer
@ -631,7 +631,7 @@ Stack: They hope at some point they are able to test all sigs and working on get
<small>
Last update:
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">May 18, 2023</span>
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">June 19, 2023</span>
</small>

20
events/meeting-notes/2023-05-18/index.html
View File

@ -532,7 +532,7 @@
<li class="md-nav__item">
<a href="../2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>
@ -587,15 +587,15 @@
* Sherif
</code></pre>
<h2 id="discussions">Discussions:<a class="headerlink" href="#discussions" title="Permanent link">&para;</a></h2>
<p>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
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: Are we going to focus on 8 and 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"
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</p>
<p>Chris: Are we willing to support all openHPC stack or just the modules and how we imagine achieving this?</p>
<p>Jeremy: Clear a bit of distro related stuff from openHPC would be great such as automake / autoconf</p>
<p>Stack: We need to have a base line so people can start use rocky on HPC and make Rocky accessible</p>
<p>Chris: A Demo / technical talk in 4 weeks</p>
<p>Chris: Are we going to focus on 8 and 9?</p>
<p>Stack and Chris, would be great if we can focus on 9</p>
<p>Sherif: I hope we can do both but with 9 in the spotlight "this needs to be a SIG decision"</p>
<p>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</p>
<p>Chris: so far testing on Rocky as the only supported EL distro</p>
<h2 id="action-items">Action items:<a class="headerlink" href="#action-items" title="Permanent link">&para;</a></h2>
<pre><code>* 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"

24
events/meeting-notes/2023-06-01/index.html
View File

@ -539,7 +539,7 @@
<li class="md-nav__item">
<a href="../2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>
@ -591,17 +591,17 @@
* Chris Simmons
</code></pre>
<h2 id="discussions">Discussions:<a class="headerlink" href="#discussions" title="Permanent link">&para;</a></h2>
<p>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 look into adding more release packages such as intel compiler
Brain storm ideas about optimizing binaries
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
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
Greg: make sure you have the provide type
Chris: also make sure that downgrade works
Greg and Chris, we can also contribute to openHPC documentation</p>
<p>Getting toolchains outside of openHPC such as automake</p>
<p>Greg: We need to talk if we need to have a generic SIG for toolchains</p>
<p>Greg: We need to look into adding more release packages such as intel compiler</p>
<p>Brain storm ideas about optimizing binaries</p>
<p>David: What would be the interest of having a light weight kernel for HPC</p>
<p>Jeremy: mentioning intel light weight kernel https://github.com/intel/mos</p>
<p>Chris: asking if there is any benchmark, hard numbers between shipped kernel and light weight kernel, so far, nothing solid</p>
<p>Sherif: Slurm now is build but not in standard path and we agreed we are going to move standard path </p>
<p>Greg: make sure you have the provide type</p>
<p>Chris: also make sure that downgrade works</p>
<p>Greg and Chris, we can also contribute to openHPC documentation</p>
<h2 id="action-items">Action items:<a class="headerlink" href="#action-items" title="Permanent link">&para;</a></h2>
<pre><code>* Get a list of packages from Jeremy to pick up from openHPC
* Greg / Sherif talk in Rocky / RESF about generic SIG for common packages such as chaintools

28
events/meeting-notes/2023-06-15/index.html
View File

@ -21,7 +21,7 @@
<title>SIG/HPC meeting 2023-06-01 - SIG/HPC Wiki</title>
<title>SIG/HPC meeting 2023-06-15 - SIG/HPC Wiki</title>
@ -73,7 +73,7 @@
<div data-md-component="skip">
<a href="#sighpc-meeting-2023-06-01" class="md-skip">
<a href="#sighpc-meeting-2023-06-15" class="md-skip">
Skip to content
</a>
@ -107,7 +107,7 @@
<div class="md-header__topic" data-md-component="header-topic">
<span class="md-ellipsis">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</span>
</div>
@ -463,12 +463,12 @@
<label class="md-nav__link md-nav__link--active" for="__toc">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
<span class="md-nav__icon md-icon"></span>
</label>
<a href="./" class="md-nav__link md-nav__link--active">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
@ -587,7 +587,7 @@
<h1 id="sighpc-meeting-2023-06-01">SIG/HPC meeting 2023-06-01<a class="headerlink" href="#sighpc-meeting-2023-06-01" title="Permanent link">&para;</a></h1>
<h1 id="sighpc-meeting-2023-06-15">SIG/HPC meeting 2023-06-15<a class="headerlink" href="#sighpc-meeting-2023-06-15" title="Permanent link">&para;</a></h1>
<h2 id="attendees">Attendees:<a class="headerlink" href="#attendees" title="Permanent link">&para;</a></h2>
<pre><code>* Chris Simmons
* Nick Eggleston
@ -599,14 +599,14 @@
* Sherif
</code></pre>
<h2 id="discussions">Discussions:<a class="headerlink" href="#discussions" title="Permanent link">&para;</a></h2>
<p>Chris gave a quick demo about openHPC / presentation
Jeremy sent the packages
Greg: asked how the SIG's slurm is compatible with openHPC
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 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
Sherif mentioned, forums category is now in place https://forums.rockylinux.org/c/sig/hpc/61</p>
<p>Chris gave a quick demo about openHPC / presentation </p>
<p>Jeremy sent the packages</p>
<p>Greg: asked how the SIG's slurm is compatible with openHPC</p>
<p>Sherif needs to look at openHPC slurm packages</p>
<p>Chris we need to look on how to build easybuild and look into how to improve it</p>
<p>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</p>
<p>Chris provided https://github.com/holgerBerger/hpc-workspace which now a part of openHPC</p>
<p>Sherif mentioned, forums category is now in place https://forums.rockylinux.org/c/sig/hpc/61</p>
<h2 id="action-items">Action items:<a class="headerlink" href="#action-items" title="Permanent link">&para;</a></h2>
<pre><code>* Sherif to look int openHPC slurm spec file
* We need to get lists of centres and HPC that are moving to Rocky to make a blog post and PR

2
index.html
View File

@ -502,7 +502,7 @@
<li class="md-nav__item">
<a href="events/meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
packages/index.html
View File

@ -466,7 +466,7 @@
<li class="md-nav__item">
<a href="../events/meeting-notes/2023-06-15/" class="md-nav__link">
SIG/HPC meeting 2023-06-01
SIG/HPC meeting 2023-06-15
</a>
</li>

2
search/search_index.json
View File

File diff suppressed because one or more lines are too long

BIN
sitemap.xml.gz
View File

Binary file not shown.