[Tahoe-LAFS] #2383: CLI option to automatically start and stop a node

[Lukas Pirl]

I just wanted to reply to a ticket but this comment got a 95.19% spam
rating?!

"""
All true. But how can we improve the usability for the "programmatic
ad-hoc use" (cron etc.)?
I think the ad-hoc-gateway-use case is valid (very low-resource or
production systems).

Latency (comment:11) is simply what one would have to accept when the
node is not permanently up. Inferences with interactive CLI use
(comment:12)… well, users would probably start and stop the node
manually anyways for interactive operations because they are not
expecting it to be up. So, the node should not stop automatically when
it wasn't started automatically. But yes, interactive users may
interrupt non-interactive operations then.

Another idea would be an idle timeout to let a gateway shutdown
automatically or a switch for `tahoe stop` that makes the node wait for
all queued operations to complete.
"""

Best,

Lukas

On 02/12/2015 04:40 AM, Tahoe-LAFS wrote:
> #2383: CLI option to automatically start and stop a node
> -----------------------------+-----------------------
>      Reporter:  lpirl        |      Owner:
>          Type:  enhancement  |     Status:  reopened
>      Priority:  normal       |  Milestone:  undecided
>     Component:  unknown      |    Version:  1.10.0
>    Resolution:               |   Keywords:
> Launchpad Bug:               |
> -----------------------------+-----------------------
> 
> Comment (by daira):
> 
>  Also, note that if you have a scheduled operation that automatically
>  starts and stops a node, then it had better be a different node than
>  you're using as your gateway for ad-hoc CLI commands. If it is the same
>  node then the scheduled operation will sometimes happen at the same time
>  as an ad-hoc one, causing random failures as the node is stopped. On the
>  other hand, using two nodes that both write to the same mutable objects
>  will introduce write coordination problems.
> 
> --
> Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2383#comment:12>
> Tahoe-LAFS <https://Tahoe-LAFS.org>
> secure decentralized storage
>