[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1843: add `tahoe create-server`, define `create-node` to mean client+server (was: rename (or alias) tahoe create-node to create-storage)

[Tahoe-LAFS]

#1843: add `tahoe create-server`, define `create-node` to mean client+server
-----------------------------------+---------------------------
     Reporter:  ChosenOne          |      Owner:  warner
         Type:  enhancement        |     Status:  assigned
     Priority:  normal             |  Milestone:  1.12.0
    Component:  code-frontend-cli  |    Version:  1.9.2
   Resolution:                     |   Keywords:  usability p2p
Launchpad Bug:                     |
-----------------------------------+---------------------------
Changes (by warner):

 * owner:   => warner
 * status:  new => assigned
 * milestone:  undecided => 1.12.0


Comment:

 Ok, I'm repurposing this ticket to move us to `create-client` / `create-
 server` / `create-node`, where "node" is both client and server.

 `create-storage` is somewhat more precise, but we don't have any non-
 storage servers that might compete for the namespace:

 * the Introducer is a server, but `create-introducer` is a great name for
 that
 * same for stats-gatherer
 * I can imagine some non-storage servers we could build (repair service,
 check/verify service, rebalancing service), but I think we can use names
 like `create-repairer` and `create-rebalancer` for those

 And `create-server` is a clear parallel to `create-client`, and emphasizes
 the new client-server mindset we're moving to.

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