[tahoe-dev] revived: proposal to change the default to K=H=N=1
erpo41 at gmail.com
erpo41 at gmail.com
Mon Jan 14 19:53:34 UTC 2013
A configuration wizard sounds like a great solution. It could even ask for
the introducer furl first to find the size of the grid and suggest sane
defaults automatically.
Thanks,
Eric
On Jan 14, 2013 8:03 AM, "Paul Rabahy" <prabahy at gmail.com> wrote:
> I would be willing to put in some time to make a CLI to allow the user to
> pick how they want it setup the first time a client is launched. I think it
> would have a few preset options and a way for the user to setup custom
> values.
>
> For example:
> Welcome to Tahoe-LAFS. You need to pick the level of redundancy for this
> client. If you would like to modify these values after they are set, you
> will need to edit tahoe.cfg. Please see /docs/running.rst for more
> information.
> 1. No redundancy. (Good for testing)
> 2. Like RAID-1. (Every share will be placed on 2 servers)
> 3. Like RAID-5. (Every share can handle a failure of 1 server)
> 4. Highly Redundant. (Good for use on the Public Test Grid)
> 5. Custom (Enter your own values for K, H, and N)
> Enter a value. [1]
>
> This seems like a reasonable place for me to get my feet wet with Tahoe
> development. I believe that this will make the initial setup process easier
> for beginners, and won't make it any more difficult for advanced users.
>
>
> On Mon, Jan 14, 2013 at 8:34 AM, Greg Troxel <gdt at ir.bbn.com> wrote:
>
>>
>> How about if a system with H=1 also prints a warning on starting a node,
>> and maybe on a few other operations?
>>
>>
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>
>>
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130114/3c01bf80/attachment.html>
More information about the tahoe-dev
mailing list