oxidecomputer / oxidecomputer/maghemite
mgd: emit a portfile to make testing multiple daemons on the same machine easier
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
The omicron testing strategy involves running a large pile of mgd daemons at once. These daemons all listen on different ports, and the omicron test code sifts through mgd log files to determine the port. Things would be much simpler if mgd just wrote out a portfile with the listening port number in it.
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 locating the mgd daemon startup and port-binding entry point, then inspect the omicron test code that currently reads mgd log files to find ports. Done means mgd writes a portfile containing its listening port so tests running multiple daemons no longer need to parse logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100