From: "Thompson, David" <dthompson2@worcester.edu>
To: Carlos Sosa <gnusosa@gnusosa.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix "ops"
Date: Thu, 28 May 2015 12:10:24 -0400 [thread overview]
Message-ID: <CAJ=RwfaCeRDCOu_EVqp8P1CqXeAFtOBFdpL2D557KRrFaNodXQ@mail.gmail.com> (raw)
In-Reply-To: <87a8wpj1s4.fsf@gnusosa.net>
On Wed, May 27, 2015 at 2:47 PM, Carlos Sosa <gnusosa@gnusosa.net> wrote:
> David Thompson <dthompson2@worcester.edu> writes:
>
>> Thinking out loud here: Maybe 'guix deploy' can kick off the
>> provisioning for all machines first, and afterwards the OS configs can
>> be altered to include the correct /etc/hosts file.
>
> I like the idea of `guix deploy` with a minor change where we add
> `guix deploy machine`, but can that be a command that calls separate
> steps like `guix provision machine` and then `guix set-config machine`
> or something similar. My intention with that, is that if the command
> `guix set-config machine` fails at least `guix deploy machine` worked
> and you can SSH to that machine or debug why did the OS configs
> failed. To deploy all of our machines in #machines-list we can do
> `guix deploy` where it defaults to `guix deploy all`. I guess this
> hints more on the usability perspective, but I think provisioning the
> OS and the configuration provision should be separate tasks. I will
> try to develop that soon. I know a patch says more than words. :)
I intend to have several subcommands for 'guix deploy' that perform
various subsets of the deployment "phases". I don't think your
use-case for "set-config" phase makes sense, because the entire system
is configured in a single operation. The system would have to boot a
valid GuixSD configuration at least once in order for SSH access to be
available. Now, a re-deploy (similar to 'guix system reconfigure')
may fail, and that could be rolled back in case of problems.
>> I threw out OpenStack because it's a self-hostable, free software VM
>> platform. I'm open to any other platforms that will exercise the full
>> range of capabilities that 'guix deploy' needs to be useful.
>
> I've been using LXC - https://en.wikipedia.org/wiki/LXC to work around
> with Guix and play with substitutes and offloading. It's been pretty
> straight forward and clean, I don't know if that would be something to
> consider.
Cool. I'd be interested in reading the steps you took to deploy a
GuixSD system with LXC. FYI, I'm (slowly) working on a pure Guile
container implementation for inclusion in Guix in the future.
- Dave
next prev parent reply other threads:[~2015-05-28 16:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 23:38 Guix "ops" David Thompson
2015-04-30 15:25 ` Ludovic Courtès
2015-04-30 16:53 ` David Thompson
2015-05-01 14:48 ` Ludovic Courtès
2015-05-04 23:51 ` Carlos Sosa
2015-05-05 2:00 ` David Thompson
2015-05-05 7:57 ` Ludovic Courtès
2015-05-07 3:02 ` Christopher Allan Webber
2015-05-22 14:59 ` David Thompson
2015-05-22 16:06 ` Ludovic Courtès
2015-05-22 16:24 ` David Thompson
2015-05-27 18:47 ` Carlos Sosa
2015-05-28 16:10 ` Thompson, David [this message]
2015-05-27 19:41 ` Ludovic Courtès
2015-05-28 16:13 ` Thompson, David
2015-07-09 18:27 ` OpenStack and GuixOps (was: Re: Guix "ops") Christopher Allan Webber
2015-07-10 2:18 ` Ian Denhardt
2015-07-10 17:24 ` OpenStack and GuixOps Ludovic Courtès
2015-06-01 15:18 ` Guix "ops" Pjotr Prins
2015-06-01 16:49 ` Thompson, David
2015-06-01 19:35 ` Guix deploy (and replace Puppet/Chef) Pjotr Prins
2015-07-10 16:37 ` Guix "ops" Christopher Allan Webber
2016-10-16 23:36 ` Christopher Allan Webber
2016-10-17 14:51 ` Ludovic Courtès
2016-10-19 21:10 ` Christopher Allan Webber
2016-10-20 13:29 ` Ludovic Courtès
2016-10-20 17:01 ` Christopher Allan Webber
2016-10-20 19:41 ` Ludovic Courtès
2019-02-11 13:31 ` It's time to build "guix deploy" Christopher Lemmer Webber
2019-02-11 14:02 ` Pjotr Prins
2019-02-11 14:47 ` Christopher Lemmer Webber
2019-02-11 18:11 ` Amirouche Boubekki
2019-02-11 14:57 ` Christopher Lemmer Webber
2019-02-11 15:25 ` Pjotr Prins
2019-02-11 16:58 ` Thompson, David
2019-02-11 20:49 ` Ricardo Wurmus
2019-02-13 19:04 ` Giovanni Biscuolo
2019-02-14 7:14 ` swedebugia
2019-02-14 8:17 ` Pjotr Prins
2019-02-14 15:35 ` Giovanni Biscuolo
2019-02-14 16:55 ` Pjotr Prins
2019-02-14 14:17 ` Giovanni Biscuolo
2019-02-17 8:41 ` swedebugia
2019-02-17 15:42 ` Giovanni Biscuolo
2019-02-12 13:34 ` Christopher Lemmer Webber
2019-02-12 14:53 ` Thompson, David
2019-03-09 23:29 ` building " Thompson, David
2019-03-10 17:42 ` Ludovic Courtès
2019-03-11 14:41 ` Christopher Lemmer Webber
2019-03-12 13:08 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfaCeRDCOu_EVqp8P1CqXeAFtOBFdpL2D557KRrFaNodXQ@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=gnusosa@gnusosa.net \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.