From: Ricardo Wurmus <rekado@elephly.net>
To: myglc2 <myglc2@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix on clusters and in HPC
Date: Wed, 26 Oct 2016 14:08:23 +0200 [thread overview]
Message-ID: <877f8vgvns.fsf@elephly.net> (raw)
In-Reply-To: <86vawh9lvw.fsf@gmail.com>
myglc2 <myglc2@gmail.com> writes:
> While SGE is dated and can be a bear to use, it provides a useful
> yardstick for HPC/Cluster functionality. So it is useful to consider how
> Guix(SD) might impact this model. Presumably a defining characteristic
> of GuixSD clusters is that the software configuration of compute hosts
> no longer needs to be fixed and the user can "dial in" a specific SW
> configuration for each job step. This is in many ways a good thing. But
> it also generates new requirements. How does one specify the SW config
> for a given job or recipe step:
>
> 1) VM image?
>
> 2) VM?
>
> 3) Installed System Packages?
>
> 4) Installed (user) packages?
At the MDC we’re using SGE and users specify their software environment
in the job script. The software environment is a Guix profile, so the
job script usually contains a line to source the profile’s
“etc/profile”, which has the effect of setting up the required
environment variables.
I don’t know of anyone who uses VMs or VM images to specify software
environments.
> Based on my experiments with Guix/Debian, GuixSD, VMs, and VM images it
> is not obvious to me which of these levels of abstraction is
> appropriate.
FWIW we’re using Guix on top of CentOS 6.8. The store is mounted
read-only on all cluster nodes.
> The most forward-thinking group that I know discarded their cluster
> hardware a year ago to replace it with starcluster
> (http://star.mit.edu/cluster/). Starcluster automates the creation,
> care, and feeding of a HPC clusters on AWS using the Grid Engine
> scheduler and AMIs. The group has a full-time "starcluster jockey" who
> manages their cluster and they seem quite happy with the approach. So
> you may want to consider starcluster as a model when you think of
> cluster management requirements.
When using starcluster are software environments transferred to AWS on
demand? Does this happen on a per-job basis? Are any of the
instantiated machines persistent or are they discarded after use?
~~ Ricardo
next prev parent reply other threads:[~2016-10-26 12:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 14:20 Guix on clusters and in HPC Ludovic Courtès
2016-10-18 14:55 ` Christopher Allan Webber
2016-10-18 16:04 ` Ludovic Courtès
2016-10-18 16:47 ` Roel Janssen
2016-10-19 11:11 ` Ricardo Wurmus
2016-10-21 12:11 ` Roel Janssen
2016-10-20 14:08 ` Ludovic Courtès
2016-10-21 9:32 ` Ricardo Wurmus
2016-10-26 11:51 ` Ludovic Courtès
2016-11-01 23:25 ` Ben Woodcroft
2016-11-02 16:03 ` Pjotr Prins
2016-11-04 22:05 ` Pjotr Prins
2016-11-05 2:17 ` Chris Marusich
2016-11-05 16:15 ` Roel Janssen
2016-11-08 12:39 ` Ludovic Courtès
2016-11-03 13:47 ` Ludovic Courtès
2016-10-19 7:17 ` Thomas Danckaert
2016-10-20 14:17 ` Ludovic Courtès
2016-10-25 2:56 ` myglc2
2016-10-26 12:00 ` Ludovic Courtès
2016-11-01 0:11 ` myglc2
2016-10-26 12:08 ` Ricardo Wurmus [this message]
2016-10-31 22:01 ` myglc2
2016-11-01 7:15 ` Ricardo Wurmus
2016-11-01 12:03 ` Ben Woodcroft
2016-11-03 13:44 ` Ludovic Courtès
2016-11-19 6:18 ` Ben Woodcroft
2016-11-21 14:07 ` Ludovic Courtès
2016-10-26 15:43 ` Eric Bavier
2016-10-26 16:31 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877f8vgvns.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.