From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Guix on clusters and in HPC Date: Wed, 19 Oct 2016 13:11:02 +0200 Message-ID: <87twc8sify.fsf@elephly.net> References: <87r37divr8.fsf@gnu.org> <8737jteh8z.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47799) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwomN-0004lT-7Q for guix-devel@gnu.org; Wed, 19 Oct 2016 07:11:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwomM-0000lR-9i for guix-devel@gnu.org; Wed, 19 Oct 2016 07:11:27 -0400 In-reply-to: <8737jteh8z.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Roel Janssen Cc: Guix-devel Roel Janssen 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”). ~~ Ricardo