unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix on clusters and in HPC
Date: Fri, 21 Oct 2016 14:11:04 +0200	[thread overview]
Message-ID: <87lgxhrjfr.fsf@gnu.org> (raw)
In-Reply-To: <87twc8sify.fsf@elephly.net>


Ricardo Wurmus writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> * Network-aware guix-daemon
>>
>>   From a user's point of view it would be cool to have a network-aware
>>   guix-daemon.  In our cluster, we have a shared storage, on which we have
>>   the store, but manipulating the store through guix-daemon is now limited
>>   to a single node (and a single request per profile).  Having `guix' talk
>>   with `guix-daemon' over a network allows users to install stuff from
>>   any node, instead of a specific node.
>
> That’s on the list as
>
>       * client needs to be able to [[http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20381][connect remotely]] instead of using [[http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20381#5][‘socat’ hack]]
>
> I’m currently using the socat hack at the MDC with a wrapper to make it
> seamless for the users.
>
>> * Profile management
>>
>>   The abstraction of profiles is an awesome feature of FPM, but the user
>>   interface is missing.  We could do better here.
>>
>>   Switch the default profile
>>   (and prepend values of environment variables to the current values):
>>   $ guix profile --switch=/path/to/shared/profile
>
> This could be a wrapper doing essentially this:
>
>     bash  # sub-shell
>     source /path/to/shared/profile/etc/profile
>     …
>
>>   Reset to default profile (and environment variable values without the
>>   profile we just unset):
>>   $ guix profile --reset
>
> Using the above wrapper it would be equivalent to just:
>
>     exit  # exit the sub-shell
>
> Does this make sense or is more needed here?
> We’re using the above workflow at the MDC.  It’s a little verbose and
> requires users to keep track of the shell in which they are operating,
> but this basically works.  Would be nice to abstract this away and hide
> it behind a nicer user interface (e.g. “guix environment save” and “guix
> environment load”).

Well, I envisioned that `guix profile --switch' would actually change
the symlink `$HOME/.guix-profile' to another profile, so that it applies
to all shells you start after you provide the command.  But maybe `guix
environment' would be better suited anyway.

Kind regards,
Roel Janssen

  reply	other threads:[~2016-10-21 12:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18 14:20 Guix on clusters and in HPC Ludovic Courtès
2016-10-18 14:55 ` Christopher Allan Webber
2016-10-18 16:04   ` Ludovic Courtès
2016-10-18 16:47 ` Roel Janssen
2016-10-19 11:11   ` Ricardo Wurmus
2016-10-21 12:11     ` Roel Janssen [this message]
2016-10-20 14:08   ` Ludovic Courtès
2016-10-21  9:32     ` Ricardo Wurmus
2016-10-26 11:51       ` Ludovic Courtès
2016-11-01 23:25         ` Ben Woodcroft
2016-11-02 16:03           ` Pjotr Prins
2016-11-04 22:05             ` Pjotr Prins
2016-11-05  2:17               ` Chris Marusich
2016-11-05 16:15               ` Roel Janssen
2016-11-08 12:39               ` Ludovic Courtès
2016-11-03 13:47           ` Ludovic Courtès
2016-10-19  7:17 ` Thomas Danckaert
2016-10-20 14:17   ` Ludovic Courtès
2016-10-25  2:56 ` myglc2
2016-10-26 12:00   ` Ludovic Courtès
2016-11-01  0:11     ` myglc2
2016-10-26 12:08   ` Ricardo Wurmus
2016-10-31 22:01     ` myglc2
2016-11-01  7:15       ` Ricardo Wurmus
2016-11-01 12:03         ` Ben Woodcroft
2016-11-03 13:44           ` Ludovic Courtès
2016-11-19  6:18             ` Ben Woodcroft
2016-11-21 14:07               ` Ludovic Courtès
2016-10-26 15:43 ` Eric Bavier
2016-10-26 16:31   ` 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

  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=87lgxhrjfr.fsf@gnu.org \
    --to=roel@gnu.org \
    --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).