[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:                     |
-----------------------------------+---------------------------

Comment (by warner):

 I'm coming around to agree with this.

 Originally I thought of tahoe nodes as being a collection of services: one
 or more of (client, server, helper, key-generator, introducer), and others
 that we haven't invented yet. But we've refined that a bit:

 * "helper" is an optional add-on to a client (i.e. it doesn't make sense
 to have a helper without a client)
 * key-generator can hopefully go away (#2783)
 * introducer is a standalone thing, not shared with clients or servers

 I think it's useful to have client-only nodes, server-only nodes, and
 client+server nodes.

 So how about:

 * `tahoe create-client` makes a client-only node
 * `tahoe create-server` makes a server-only node
 * `tahoe create-node` makes a client+server node

 Soon, the forms that include servers will probably need additional
 arguments like `--location` or `--hostname` (see #2773), which are
 unnecessary for client-only nodes. Client-only nodes will not listen on
 any TCP ports, and don't need to advertise a hostname or IP address to
 anybody else.

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