drakkar-lig / drakkar-lig/walt-python-packages
Replaying virtual nodes bootup
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Since commit d79221503149721c162b6d245da67ce470a79e3a serial output of nodes is recorded in /var/lib/walt/logs/vnodes, thus they can be replayed with scriptreplay.
It would be better to reuse the logging system for that, because /var/lib/walt/logs/vnodes is only accessible on walt server machine, and using them is not user-friendly.
Instead we could:
- let the server accept incoming log lines from a local unix socket (using it would avoid loading the network)
- let walt-virtual-node send log lines there, with logstream
serial, when virtual node is run on the server - add a command option
--replaytowalt log show. When used, walt client would follow delays between the first log line and the others. Using this option on logstreamserialwould allow to "replay" the bootup of a node.
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 by tracing the server logging path, walt-virtual-node execution on the server, and the walt log show command. Review how serial log lines and /var/lib/walt/logs/vnodes are currently handled, then define the Unix-socket and --replay behavior described in the issue. Done means virtual-node boot output can be replayed through the logging system without direct access to the server log directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100