From: "Thompson, David" <dthompson2@worcester.edu>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: "Ricardo Wurmus" <rekado@elephly.net>,
"Yasuaki Kudo" <yasu@yasuaki.com>, Phil <phil@beadling.co.uk>,
"Ludovic Courtès" <ludo@gnu.org>,
"Benjamin Slade" <beoram@gmail.com>,
help-guix <help-guix@gnu.org>
Subject: Re: Enterprise Guix Hosting?
Date: Wed, 31 Aug 2022 08:54:32 -0400 [thread overview]
Message-ID: <CAJ=Rwfb6PYjGhqfaDHrDLAd2fgCWD0QDs=BxQ1sONLgVt0+jHQ@mail.gmail.com> (raw)
In-Reply-To: <877d2oljvl.fsf@laura>
Hi Olivier,
On Wed, Aug 31, 2022 at 7:42 AM Olivier Dion <olivier.dion@polymtl.ca> wrote:
>
> On Wed, 31 Aug 2022, "Thompson, David" <dthompson2@worcester.edu> wrote:
> > Hey that's a real nice starting point for a container management tool!
> > So maybe there should be a system service to manage containers and
> > then a 'docker compose'-like tool for declaratively specifying
> > containers and their network bridging configuration that is a client
> > of the service?
>
> I think that a container composer à la `docker compose' but with
> Guile/Guix is easily done. Managing containers locally is trivial and a
> little web interface could be done to view/manager your contrainers.
> The service could even be a home-service.
>
> From there, a more mature container orchestrator that can scale
> to multiple nodes could be made. Competing with Kubernetes. Of course
> at that level things are not trivial anymore.
Just thinking about making something on the level of Kubernetes makes
me want to hide under a desk, but that is certainly more in line with
the subject of this email thread. :)
So who's going to start selling Guix Enterprise subscriptions? It
would be a lot of fun. You could have Guix Solution Architects and
other fun corporate titles!
- Dave
next prev parent reply other threads:[~2022-08-31 12:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via
2022-07-30 16:20 ` Phil
2022-07-30 23:18 ` Yasuaki Kudo
2022-07-31 0:42 ` Benjamin Slade
2022-07-31 11:01 ` Phil
2022-08-09 20:37 ` Ludovic Courtès
2022-08-09 22:24 ` Yasuaki Kudo
2022-08-14 9:53 ` Phil
2022-08-14 22:03 ` Yasuaki Kudo
2022-08-15 20:50 ` Phil
2022-08-25 18:37 ` Olivier Dion via
2022-08-26 6:40 ` Yasuaki Kudo
2022-10-12 9:55 ` Ade Malsasa Akbar
2022-10-12 10:18 ` Olivier Dion via
2022-08-26 7:24 ` Ricardo Wurmus
2022-08-31 1:42 ` Thompson, David
2022-08-31 6:33 ` Ricardo Wurmus
2022-08-31 10:46 ` [EXT] " Thompson, David
2022-08-31 11:42 ` Olivier Dion via
2022-08-31 12:54 ` Thompson, David [this message]
2022-09-05 19:38 ` Ludovic Courtès
2023-01-23 15:34 ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Giovanni Biscuolo
2023-01-23 16:48 ` Przemysław Kamiński
2023-01-23 17:59 ` Wojtek Kosior via
2022-09-05 19:42 ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03 ` zimoun
2022-10-08 16:23 ` Phil
2022-10-10 7:58 ` zimoun
2022-10-10 10:30 ` (
2022-10-10 10:49 ` zimoun
2022-10-10 19:35 ` Phil
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='CAJ=Rwfb6PYjGhqfaDHrDLAd2fgCWD0QDs=BxQ1sONLgVt0+jHQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=beoram@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
--cc=phil@beadling.co.uk \
--cc=rekado@elephly.net \
--cc=yasu@yasuaki.com \
/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).