From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>, guix-devel <guix-devel@gnu.org>
Subject: Re: Swineherd: Guix System container manager
Date: Wed, 13 Sep 2023 09:29:05 -0600 [thread overview]
Message-ID: <f88fcd20-51a9-e041-9670-2c12d5f2c421@gmail.com> (raw)
In-Reply-To: <87y1ha1lap.fsf@elephly.net>
On 9/13/23 3:06 AM, Ricardo Wurmus wrote:
> Hi there,
>
> you know the Shepherd: it is an elegant service manager looking after a
> herd of daemons. Since it can be extended with Guile, I decided to do
> just that to add an extra skill to the Shepherd, turning it into the
> Swineherd.
>
> The Swineherd is a manager of Guix System containers. It is implemented
> as a Shepherd service called “swineherd” that lets you manage Guix
> System containers as Shepherd services. These system container services
> implement a few common features to bring up bridge networking, execute
> commands inside the containers, peek at files, and get simple usage
> stats.
>
> Swineherd also provides an optional HTTP API server to launch, manage,
> and destroy containers through an HTTP client. This makes the Swineherd
> useful for building web applications that launch Guix System containers
> on demand. It comes with an Info manual describing the assumptions, the
> required setup, as well as the implemented commands and the HTTP API.
>
> The Swineherd was designed to be used with Shepherd on foreign distros,
> so it does not assume to be running on top of Guix System (for better or
> worse).
>
> You can find the code here:
>
> https://github.com/BIMSBbioinfo/swineherd
>
> Of course the Swineherd is also available as a Guix package called
> “swineherd”.
>
> If this tickles your interests I’d be very happy to hear your comments
> and incorporate patches to extend it beyond my original requirements.
This is really cool stuff! I'd love to see Guix continue to eat the
dev-ops space, which, in my opinion, loves to stack complexity on top of
complexity.
Can you share any ways you're currently using this?
Any plans/interest in hooking it into `guix deploy`?
next prev parent reply other threads:[~2023-09-13 15:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 9:06 Swineherd: Guix System container manager Ricardo Wurmus
2023-09-13 12:58 ` Simon Tournier
2023-09-14 6:42 ` Tanguy LE CARROUR
2023-09-14 9:19 ` Ricardo Wurmus
2023-09-13 15:29 ` Katherine Cox-Buday [this message]
2023-09-13 16:14 ` Thompson, David
2023-09-13 18:23 ` Ricardo Wurmus
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=f88fcd20-51a9-e041-9670-2c12d5f2c421@gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=guix-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.
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).