Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a --reboot-nodes flag to the CLI (Allow daemonisation) #119

Open
thclark opened this issue Mar 16, 2023 · 0 comments
Open

Add a --reboot-nodes flag to the CLI (Allow daemonisation) #119

thclark opened this issue Mar 16, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@thclark
Copy link
Contributor

thclark commented Mar 16, 2023

Feature request

Use Case

When you exit the gateway at an arbitrary time (eg the code crashes or container reboots), the nodes can be left in an unknown state, and require reboot to reset to a useable condition.

Current state

This prevents us from daemonising the installation of the gateway, requiring that we have to manually start each session via balena.

Proposed Solution

If the CLI had a --reboot-nodes flag, which executed a reboot of any connected nodes on start, this would allow us to address
the issue.

Hardware Aspects

I asked @tommasopolonelli "do we now/still have a method (a sequence of commands that we can send) to force a node to reset from remote commands?" Tommaso's response from teams:

"For sure would be an useful command, that unfortunately is not available at the moment"

So this would have to involve some development on the hardware side before we could implement from here. Note also The sequence would need to work for whatever state the node is in..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant