[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2844: readiness status API for clients

[Tahoe-LAFS]

#2844: readiness status API for clients
-------------------------+-----------------------
     Reporter:  dawuud   |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  1.11.0
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by meejah):

 We just discussed this in Ops meeting Nov 29, and concluded:

  - we just need a "twisted" API for e.g. "spawn_client"
  - this takes the requested configuration and returns a Deferred
  - the Deferred either errbacks, or succeeds when the client is "ready"
  - to determine "readiness" we add an HTTP API
  - under the hood, the "spawn_client()" talks via the above HTTP API
 (polling until it connects)
  - the API has a /v0/ready or similar path, which only returns (ends the
 request) when the client is ready (i.e. a "put" will "probably" work --
 the client has connected to enough storage-servers)

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