[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2794: move controlport/logport to a separate Tub (and separate port)

[Tahoe-LAFS]

#2794: move controlport/logport to a separate Tub (and separate port)
----------------------------+------------------------
 Reporter:  warner          |          Owner:  warner
     Type:  task            |         Status:  new
 Priority:  normal          |      Milestone:  1.13.0
Component:  code-nodeadmin  |        Version:  1.11.0
 Keywords:                  |  Launchpad Bug:
----------------------------+------------------------
 (splitting this out of #2491)

 Currently, the "controlport" and logport both use the same Tub as
 everything else (which, since we landed the #2759 one-Tub-per-server
 change, means "the same Tub as the storage server"). We want to not open a
 listening port unless we're running a storage server, and we're requiring
 the operator to tell us what the externally-visible location of that
 server is (rather than attempting to determine an IP address
 automatically), so the controlport/logport should be moved to a separate
 Tub.

 This new control/log Tub should allocate a port (unless one is explicitly
 configured in tahoe.cfg) and should advertise a location of 127.0.0.1
 (unless overridden in tahoe.cfg). That will enable both the automated
 tests like check_memory.py, and the common `flogtool tail
 NODEDIR/private/logport.furl` idiom.

 If folks want to debug their nodes from a distant machine, they'll need to
 set tahoe.cfg to provide a `location` for their logport, so `logport.furl`
 will get a real hostname/ipaddr, instead of 127.0.0.1

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