unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org, Josh Marshall <joshua.r.marshall.1991@gmail.com>
Subject: Re: How do I support building a guix package over multiple machines in a cloud environment?
Date: Tue, 3 Dec 2019 12:03:47 +0100	[thread overview]
Message-ID: <CAJ3okZ3DNF_-oNt=V8_YHShqA4pcMZNS-EzdtYYuuzR_WdgzJA@mail.gmail.com> (raw)
In-Reply-To: <87a78a9u22.fsf@elephly.net>

Hi Ricardo,

On Tue, 3 Dec 2019 at 00:39, Ricardo Wurmus <rekado@elephly.net> wrote:

> The GWL is capable of running jobs in a distributed environment.  I
> started work on an AWS library for Guile[1], which would allow us to
> spawn EC2 instances as needed.  The library works in that it provides a
> DSL for interacting with AWS, but it needs testing, polishing, and
> integration into the GWL.

This is really great!
Let talk about that in the near future. :-)


> Currently, I’m on parental leave and don’t really get to do any hacking
> for a few months.

Take care! :-)

> I would be happy if someone else could take a look at
> the AWS library and its integration into the GWL; these tasks are not
> trivial, but there are only few unknowns and it really just requires
> time to implement the missing bits.

I will schedule some time to give a look at your library.
If you are coming at the Guix Days, we could discussed these tasks and
others. :-)


Cheers,
simon

  parent reply	other threads:[~2019-12-03 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 17:36 How do I support building a guix package over multiple machines in a cloud environment? Josh Marshall
2019-12-02 19:00 ` zimoun
2019-12-02 20:02   ` pjotr.public12
2019-12-02 20:16     ` Josh Marshall
2019-12-02 21:00       ` zimoun
2019-12-02 20:03   ` Josh Marshall
2019-12-02 20:59     ` zimoun
2019-12-02 23:39 ` Ricardo Wurmus
2019-12-03  3:00   ` Josh Marshall
2019-12-03 11:03   ` zimoun [this message]
2019-12-03 13:47     ` Pjotr Prins

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='CAJ3okZ3DNF_-oNt=V8_YHShqA4pcMZNS-EzdtYYuuzR_WdgzJA@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-devel@gnu.org \
    --cc=joshua.r.marshall.1991@gmail.com \
    --cc=rekado@elephly.net \
    /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).