From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: gwl-devel@gnu.org
Subject: Re: Next steps for the GWL
Date: Wed, 12 Jun 2019 11:46:21 +0200 [thread overview]
Message-ID: <87a7en9lw2.fsf@mdc-berlin.de> (raw)
In-Reply-To: <87a7f5l6e1.fsf@mdc-berlin.de>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> My goals for the future (in no particular order) are as follows:
>
> * add support for running workflows from a file (without
> GUIX_WORKFLOW_PATH)
This is now implemented.
> * add support for executing processes in isolated environments
> (containers) — this requires a better understanding of process inputs.
A primitive version of this is also implemented now. Every generated
script supports containerization when GWL_CONTAINERIZE is set. (I don’t
expect users to set this manually, but to have a “driver” script that
sets it according to user configurations.)
This is one of the use cases that needs to be understood better. I
would like different execution backends to be available in the generated
job scripts without having to make this decision at preparation time. I
want developers to be able to distribute workflow artifacts that are
flexible enough to execute the workflow in different ways, so I think
container support must be switchable at runtime.
--
Ricardo
prev parent reply other threads:[~2019-06-12 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 13:47 Next steps for the GWL Ricardo Wurmus
2019-06-03 15:16 ` zimoun
2019-06-03 16:18 ` Ricardo Wurmus
2019-06-06 11:07 ` zimoun
2019-06-06 12:19 ` Ricardo Wurmus
2019-06-06 13:23 ` Pjotr Prins
2019-06-06 3:19 ` Kyle Meyer
2019-06-06 10:11 ` Ricardo Wurmus
2019-06-06 10:55 ` zimoun
2019-06-06 11:59 ` Ricardo Wurmus
2019-06-06 13:44 ` Pjotr Prins
2019-06-06 14:06 ` Pjotr Prins
2019-06-06 15:07 ` Kyle Meyer
2019-06-06 20:29 ` Ricardo Wurmus
2019-06-07 4:11 ` Kyle Meyer
2019-06-12 9:46 ` Ricardo Wurmus [this message]
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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7en9lw2.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=gwl-devel@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).