[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] Shepperd service and guixsd declarative configur
From: |
ng0 |
Subject: |
Re: [GNUnet-developers] Shepperd service and guixsd declarative configuration of gnunet |
Date: |
Fri, 08 Apr 2016 19:04:40 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
tg(x) <address@hidden> writes:
>> I don't think it make sense to integrate 'testbed', as that's really for
>> experiments by researchers and never a system service.
>
> It might be useful if you want to run your experiments on lots of Guix nodes.
I think I leave that to extend for others, currently my map is:
1. understand enough guile to understand some of the network
services we have
2. write a (user) serving basic service
3. expand this service to include all necessary options.
4. advanced -> testbed and other things if necessary/possible.
When we have "guix deploy" it might make sense to have a
testbed option.
>> Most of the "interesting" options you can also manipulate via
>> 'gnunet-setup', but that largely raises the question of how to enable
>> such a tool the Guix-way.
>
> Guix could provide a GUI for editing the system configuration
> at some point but I guess that's not a priority.
Exactly, as an gui for configuring the system in general is no
priority at this point.
Btw, i did not know that "*" was valid in email
uniforms. Fascinating.
> -tg
--
ng0