[tahoe-dev] server selection Re: Node correlations - [Was] best practice for wanting to setup multiple tahoe instances on a single node

[Olaf TNSB]

On 18/01/2012 10:27 PM, "Greg Troxel" <gdt at ir.bbn.com> wrote:
>
> That seems ok to me (I'm a longtime Scheme fan), but it's amusing to see
> scheme as an extension language in a python program.

Yeah... See my comment to David-Sarah.  :)

> To make some progress with less work, I would suggest:
>
>  write a design document for expressing locations, and for an upload
>  policy that seeks to get geographic diversity.   (with the thought
>  that this will need redoing for the Grand Unified Upload Policy, but
>  that it's part of getting there rather than wasted)
>
>  implement the above in Python, trying to keep it separated from other
>  code  (with the thought that this is the first step towards a) being
>  useful and b) designing the (semantic) extension language interface
>  that will allow writing arbitrary policies)

Sounds like a reasonable approach.  My though of using something like JSON
is that we don't need to have a set of common location rules, just some way
of expressing and then getting attributes...but I think that's clear.

Thanks for the feedback.

Olaf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120119/a658d2b4/attachment.html>