drakkar-lig / drakkar-lig/walt-python-packages
Better inform the user about nodes' bootup status
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Old raspberry pi boards may take a little while for booting (a few minutes).
The experimental hybrid boot feature may also incur much longer boot times when the image is booted for the first time and must be copied to the node's disk.
If we change the walt-init log stream and send more formalized boot status updates, we could then inform the user better:
- by adding
no: bootingto the possible values of columnBootedofwalt node show-- this would be printed after we get a first sign of the node's bootup procedure (walt-initlog line?register_device()call?walt-server-httpdquery?) - by indicating the current bootup step of remaining nodes in
walt node wait(off/early-boot,walt init,hybrid-mode: copying OS,OS init; orat various stages of bootupwhen relevant)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the walt node show and walt node wait command paths, then inspect the walt-init log stream, register_device(), and walt-server-httpd query mentioned in the issue. Done means formal boot-status updates support no: booting and expose the requested stages, including hybrid-mode OS copying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100