[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#36404] [PATCH 0/6] Add 'guix deploy'.

From: Ludovic Courtès
Subject: [bug#36404] [PATCH 0/6] Add 'guix deploy'.
Date: Mon, 01 Jul 2019 14:48:47 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)

Hello Jakob & all!

address@hidden (Jakob L. Kreuze) skribis:

> This patch provides the basis for 'guix deploy', implementing what I've
> referred to as the "simple case" in my progress reports: in-place
> updates to machines (physical or virtual) whose name and IP address we
> know well. Do note that these commits depend on Ludovic's implementation
> of 'remote-eval'.[1]


> There's certainly more to be done with this -- the GSoC period is far
> from over, and I'm hoping to use that time to implement more complex
> use-cases such as automatically provisioning virtual machines in the
> cloud. I'm submitting a patch series now per the recommendation of my
> mentors to break the project into a few chunks to submit over the
> duration of the summer.

That’s an impressive achievement!  I’m all for integrating patches
piecemeal, and it’s great that you’ve managed to have sizable chunks

> Quite a bit has changed since my last email about this.[2] For one,
> GOOPS is no longer used. Machine declarations now look just like any
> other sort of declaration in Guix.

Neat.  I prefer it this way, at least for consistency.

If for some reason this turns out to make extensibility more cumbersome,
like Chris wrote, we can rediscuss it.  My feeling is that we can make
do without GOOPS _and_ without reimplementing GOOPS mechanisms in a poor
way, but if that’s not the case, we can adjust.

> (list (machine
>        (system %system)
>        (environment 'managed-host)
>        (configuration (machine-ssh-configuration
>                        (host-name "localhost")
>                        (identity "./id_rsa")
>                        (port 2222)))))
> #+END_SRC scheme
> There are a number of other differences here as well. For one, the SSH
> configuration now has an 'identity' field for specifying a private key
> to use when authenticating with the host. Any key management scheme you
> might have set up in '~/.ssh/config' will also work if the 'identity'
> field is omitted.
> The 'environment' field is where we declare how machines should be
> provisioned. In this case, the only type of provisioning that's been
> implemented is 'managed-host' -- the "simple case" of in-place updates
> to a machine that's already running GuixSD. The parameters for
> provisioning are given in the form of an environment-specific
> configuration type. In the example, this is 'machine-ssh-configuration',
> which describes how 'guix deploy' should make an SSH connection to the
> machine. I'm sure you can imagine something along the lines of a
> 'machine-digitalocean-configuration', describing some parameters for a
> droplet.


I’ll take a closer look and to comment on the other issues you raise,
but so far this looks very nice!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]