[tahoe-lafs-trac-stream] [tahoe-lafs] #1843: rename (or alias) tahoe create-node to create-storage

[tahoe-lafs]

#1843: rename (or alias) tahoe create-node to create-storage
-----------------------------------+---------------------------
     Reporter:  ChosenOne          |      Owner:
         Type:  enhancement        |     Status:  new
     Priority:  normal             |  Milestone:  undecided
    Component:  code-frontend-cli  |    Version:  1.9.2
   Resolution:                     |   Keywords:  usability p2p
Launchpad Bug:                     |
-----------------------------------+---------------------------
Changes (by zooko):

 * keywords:  usability => usability p2p


Old description:

> Just now on IRC there was a discussion about creating a storage node. A
> new user was confused and couldn't wrap his head around the general setup
> of a tahoe grid.
>
> As zooko stated, tahoe isn't really sure about whether it's a p2p or a
> client-server protocol, since nodes can have multiple roles as of now.
>
> One outcome was the suggestion to have a "tahoe create-storage". This
> term would be less shallow and explicitly state what kind of node is
> created.

New description:

 Just now on IRC there was a discussion about creating a storage node. A
 new user was confused and couldn't wrap his head around the general setup
 of a tahoe grid.

 As zooko stated, tahoe isn't really sure about whether it's a p2p or a
 client-server protocol, since nodes can have multiple roles as of now.

 One outcome was the suggestion to have a "tahoe create-storage". This term
 would be less shallow and explicitly state what kind of node is created.

--

Comment:

 adding keyword {{{p2p}}} to tag tickets that have to do with the open
 question of "Is Tahoe-LAFS client-server or is it peer-to-peer?":
 [//pipermail/tahoe-dev/2012-July/007533.html]

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1843#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage