ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-05-20 17:53:01 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

decisions

Browse Source
This commit is contained in:
meejah 2020-11-16 01:23:37 -07:00
parent f6f53ad165
commit 885f72ff2b
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/managed-grid.rst
View File

@ -212,7 +212,7 @@ Enrolling a Client: CLI
tahoe add-grid-manager (PROPOSED) tahoe add-grid-manager (PROPOSED)
````````````````````````````````` `````````````````````````````````
DECIDE: this command hasn't actually been written yet. (Note: this command hasn't actually been written yet).
This takes two arguments: ``name`` and ``public-identity``. This takes two arguments: ``name`` and ``public-identity``.
@ -336,15 +336,6 @@ Put the key printed out above into Alice's ``tahoe.cfg`` in section
example_name = pub-v0-vqimc4s5eflwajttsofisp5st566dbq36xnpp4siz57ufdavpvlq example_name = pub-v0-vqimc4s5eflwajttsofisp5st566dbq36xnpp4siz57ufdavpvlq
DECIDE:
- should the grid-manager be identified by a certificate? exarkun
points out: --name seems like the hint of the beginning of a
use-case for certificates rather than bare public keys?).
- (note the "--name" thing came from a former version of this
proposal that used CLI commands to add the public-keys -- but the
point remains, if there's to be metadata associated with "grid
managers" maybe they should be certificates..)
Now, re-start the "alice" client. Since we made Alice's parameters Now, re-start the "alice" client. Since we made Alice's parameters
require 3 storage servers to be reachable (``--happy=3``), all their require 3 storage servers to be reachable (``--happy=3``), all their
uploads should now fail (so ``tahoe put`` will fail) because they uploads should now fail (so ``tahoe put`` will fail) because they