Hi Jakob,
Jakob Schiotz writes:
> Sorry for being late in replying, the spam filter held your mail.
No problem.
>> On 6 Nov 2023, at 15.21, Loris Bennett wrote:
>>
>> Hi Jakob,
>>
>> Jakob Schiotz writes:
>>
>>> At our cluster, the different nodes mount the /home/modules folder
>>> from
Sorry for being late in replying, the spam filter held your mail.
> On 6 Nov 2023, at 15.21, Loris Bennett wrote:
>
> Hi Jakob,
>
> Jakob Schiotz writes:
>
>> At our cluster, the different nodes mount the /home/modules folder
>> from different file systems, so they each contain the modules
Dear Alan,
Regarding the deduplication, I assume you are talking about CVMFS.
Currently our software is in an XFS file system, where it seems
deduplication would have to be done in some sort of offline manner.
However, maybe I shouldn't worry about that too much as disk space isn't
much of a
Hi Jakob,
Jakob Schiotz writes:
> At our cluster, the different nodes mount the /home/modules folder
> from different file systems, so they each contain the modules for the
> appropriate architecture. The advantage is, that if a script or
> something else (like a Python venv) contains a path
At our cluster, the different nodes mount the /home/modules folder from
different file systems, so they each contain the modules for the appropriate
architecture. The advantage is, that if a script or something else (like a
Python venv) contains a path to a file in a module, it will always be
Dear Loris,
This is indeed to a large extent the same approach as EESSI. Our
filesystem layer has de-duplication so there is no need for us to make
the distinction in 3 and the resulting discussion (there's no cost to
multiple installations of the same thing). You should take a look at the
Hi,
We need to manage an heterogeneous cluster and I am looking at how to
organise building the software in this context. My current idea is the
following:
1. Software is created within the following directory tree
/nfs/easybuild/arch/x68_64/amd
.../amd/zen3
7 matches
Mail list logo
