[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3457: The separate introducer servers represent unnecessary complexity in an overall Tahoe-LAFS deployment

[Tahoe-LAFS]

#3457: The separate introducer servers represent unnecessary complexity in an
overall Tahoe-LAFS deployment
--------------------------+---------------------------
 Reporter:  exarkun       |          Owner:
     Type:  defect        |         Status:  new
 Priority:  normal        |      Milestone:  undecided
Component:  code-network  |        Version:  n/a
 Keywords:                |  Launchpad Bug:
--------------------------+---------------------------
 A useful Tahoe-LAFS deployment consists of:

 * one or more clients
 * one or more storage servers
 * one or more introduction mechanisms
   * zero or more introducer servers; or
   * zero or more static storage server configuration blobs for clients

 At least one client is required or no service is being consumed.  At least
 one storage server is required or not server is being offered.

 A client can be put in touch with a storage server either by:

   * receiving static configuration that gives it that storage server's
 storage announcement
   * receiving static configuration that lets it contact an introducer
 server; if the storage server is also configured to contact this
 introducer server then the introducer server will convey the storage
 server's announcement to the client.

 A deployment with no introducer servers has at least two advantages over a
 deployment with introducers:

   * it is operationally simpler in that it involves fewer pieces of long-
 running software to operate
   * it does not introduce a point of failure into the system between
 clients and storage servers (though since multiple introducers are
 supported it is possible to operate an collection of introducer servers to
 make sure use of these isn't a *single* point of failure in the system -
 at the cost of additional operational complexity).

 A deployment with one or more introducer servers has at least one
 advantage over a deployment with none:

   * a mechanism is provided to automatically inform clients of changes to
 the operating group of storage servers

 If we can provide the automatic client updates without operating any
 introducer servers then this would seem to be a clear win, picking up all
 of the advantages from both of the current deployment options.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3457>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage