From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: How do I support building a guix package over multiple machines in a cloud environment?
Date: Mon, 2 Dec 2019 22:00:49 -0500 [thread overview]
Message-ID: <CAFkJGRf2bFhp0_qo-peTXtj=8_jKxwf0FCkc2f9mn5eKZz-p4w@mail.gmail.com> (raw)
In-Reply-To: <87a78a9u22.fsf@elephly.net>
Thank you for the reply.
I'm not prepared to sink in the development time to get native
spanning to cloud instances, but thank you for the information. This
probably puts the nail in the coffin for using guix for my coworker's
work but I'm still interested if only for my own projects.
On Mon, Dec 2, 2019 at 6:39 PM Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Hi Josh,
>
> I would not use the GWL to automate *building* software in a distributed
> fashion across separate nodes. There are tools that have been designed
> specifically for distributed compilation of software that would be more
> appropriate here.
>
> 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.
>
> Currently, I’m on parental leave and don’t really get to do any hacking
> for a few months. 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.
>
> ~~ Ricardo
>
> [1]: https://git.elephly.net/?p=software/guile-aws.git;a=summary
>
next prev parent reply other threads:[~2019-12-03 3:01 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 [this message]
2019-12-03 11:03 ` zimoun
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='CAFkJGRf2bFhp0_qo-peTXtj=8_jKxwf0FCkc2f9mn5eKZz-p4w@mail.gmail.com' \
--to=joshua.r.marshall.1991@gmail.com \
--cc=gwl-devel@gnu.org \
--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).