[tahoe-dev] Debian packages?

[Olivier Schwander]

Le 20 Apr 2011 07:06, Greg Troxel a écrit:
> 
> bertagaz at ptitcanardnoir.org writes:
> 
> > One of the feedback might be to make tahoe ran like a system service
> > (started by an initscript), and be a bit more compliant regarding the
> > FHS, i.e having its configuration in /etc/tahoe/, storage in
> > /var/lib/tahoe/, etc... So far it seems the only change in tahoe that
> > might help is having a configurable storedir.
> 
> That makes sense, but a few points:
> 
>   Re: FHS: there are other conventions on BSD (hier(7)) and I'm sure
>   other rules in other places.  It's certainly fair to adjust tahoe
>   while packaging for FHS on Debian, but I wanted to caution that this
>   should lead to configuration options that Debian can use, not "fixing"
>   tahoe to be FHS-compliant.  It sounds very much like that's what you
>   meant.

If we want to run tahoe system-wide, we need to respect Debian
convention such as config in /etc/tahoe, persistent data in
/var/lib/tahoe, etc.

>   There can be multiple nodes on a single machine.  They might be
>   running under different uids.  A user running a storage node  on a
>   multi-user machine should probably have the storage used count towards
>   that uid's quotas/accounting.

Yes, you may run multiple tahoe instances using different user id but I
think it's still a good idea to provide a system wide installation, with
a specific user and specific data and config dirs (if you look at apache
for example, you are still able to run your own custom apache with a
custom config, even if the package provide a system-wide configuration).

>   I'm not sure what you mean by configurable storedir.  Do you mean
>   splitting storage and node config?   People have been talking about
>   that.  There could be a storage_dir= key added in the config file
>   pretty easily.

This seems good enough, yes.

>   People often put nodes on removable disks.  The node directory has the
>   identity of the node, and it can be brought up on another machine.
>   So there is merit in keeping node config and node storage together.
>   But, people may want to do it differently.

Or you may just put the two directories on the removable disk, I don't
see the problem.

>   In packaging tahoe for NetBSD/pkgsrc, the only thing that's bothering
>   me (that's a packaging issue) is starting up the node at boot.  I am
>   thinking of a variable that's a list of pairs, sort of like
>   (semantically):
> 
>     (('tahoes "/n1/TAHOES/foo-n1-pubgrid")
>      ('gdt "/home/gdt/.tahoe-pubgrid))
> 
>   A nit is that users should perhaps be able to configure a node to be
>   permanent and have the startup process do it for them, but editing
>   /etc/rc.conf once privileged doesn't seem hard.

With a tahoe user and an init.d script, it is straightforward to
automate the launch of the node at boot time. If users want to run it on
their own, it is their problem to launch the node (using cron's @reboot
directive, or whatever they want).

Regards,

Olivier