I suspect there are quite a few people on this list and not the trac stream. I put my comments in trac to have their organized for later, but they sort of belong here too.
I particular, when I say the introducer should be persistent or remove nodes on disconnect, I mean that there should be an invariant about the current state that is preserved across restarts, more or less, so that the system has predictable and consistent behavior whether or not nodes have rebooted.
--- Begin Message ---#1997: Remove node feature -----------------------------+------------------------------ Reporter: luckyredhot | Owner: daira Type: enhancement | Status: new Priority: normal | Milestone: undecided Component: unknown | Version: 1.10.0 Resolution: | Keywords: node, introducer Launchpad Bug: | -----------------------------+------------------------------ Comment (by gdt): Several thoughts (for an ideal world) * There should be a command to run on a node to unregister it from the introducer. People can run this when decommissioning a node. * The fact that restarting the introducer cleans the nodes list is a bug. This should be persistent. If it isn't persistent, nodes should go away immediately on disconnect. * It makes sense to have nodes shown as OK/green, DOWN/red (for nodes that have been up in the last 7 days) and STALE/yellow (for nodes that have not been heard from in 7 days). I agree that hiding stale nodes, or putting them in a different section makes sense. DOWN nodes however should stay in order and be loudly pointed out. * There should be a command on the introducer to remove a node from the list (assuming it is not connected). In a multi-introducer world, this should propagate. * When a node is removed from the introducer, it should be automatically removed from client nodes. Just fixing this would help a lot. * Whatever we do, it should not depend on color displays or color vision, or vision at all, but be manifest in the text. (I have nodes with the missing css, and it's really hard to tell what's going on, which is probably a separate issue, and I know the css install is fixed.) -- Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1997#comment:4> tahoe-lafs <https://tahoe-lafs.org> secure decentralized storage _______________________________________________ tahoe-lafs-trac-stream mailing list tahoe-lafs-trac-str...@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-lafs-trac-stream
--- End Message ---
_______________________________________________ tahoe-dev mailing list tahoe-dev@tahoe-lafs.org https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
