From: Devan <mail@dvn.me>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Orchestration working group (before: Guix orchestration notes)
Date: Sun, 4 Mar 2018 03:18:39 +0100 [thread overview]
Message-ID: <20180304021839.j7ittjuexbzdjtuj@kowloon> (raw)
In-Reply-To: <20180301161855.GA6170@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Hi all,
Pjotr Prins transcribed 0.6K bytes:
> Hi Chris,
>
> That was a lengthy writeup, thanks :). I think the first step is to
> think in terms of (container/VM) provisioning. Then build that up towards
> orchestration and workflows.
I agree. I think a good start would be figuring out ways to
essentially replace what you can do with Dockerfiles. Which to me
mainly means having the ability to arbitrarily copy files into, and
further manipulate the tarballs made from using `guix pack`.
This would already allow us to build useful container images without
having to pull in random blob layers, which is the current state of
affairs with docker. These could then be orchestrated with the many
existing tools, and it would be a big step forward in reproducability
and security for that ecosystem.
> There is some overlap with the HPC
> working group, but I think we ought to have one on
> orchestration/provisining/work flows. I am quite keen to have
> something in place in the coming year. I.e., roll out firing up of
> software combinations in isolated environments. Let's keep discussing
> and build up a web page for that.
>
> My first provisioning step is to start up a Guix container on a server
> somewhere through a REST API and fire up a script that can run in the
> container.
That all sounds like good ideas to me.
> Pj.
Devan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-04 2:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 4:37 Guix orchestration notes Chris Marusich
2018-03-01 16:18 ` Orchestration working group (before: Guix orchestration notes) Pjotr Prins
2018-03-04 2:18 ` Devan [this message]
2018-03-04 20:42 ` Chris Marusich
2018-03-27 18:27 ` Guix orchestration notes Thompson, David
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180304021839.j7ittjuexbzdjtuj@kowloon \
--to=mail@dvn.me \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).