oxidecomputer / oxidecomputer/omicron
Finish designing instance DNS
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
I'm converting this from a TODO here:
so that we don't lose track of it. The plumbing of DNS host domain and search list options down to the guest is otherwise completed, so this specifically tracks the work related to choosing which DNS servers we advertise to guests; construct their search list; and handle those DNS request from the guests via OPTE.
Contributor guide
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 at the TODO in nexus/src/app/instance.rs around line 1204, then trace the existing DNS host-domain and search-list plumbing to the guest. The remaining scope concerns selecting advertised DNS servers, constructing the search list, and handling guest DNS requests via OPTE. Done requires a defined and implemented design for those three areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100