oxidecomputer / oxidecomputer/opte
Time synchronization servers should come from the `VpcCfg`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
Similar to #270, we don't have any public API for setting the servers used for time synchronization protocols (NTP, SNTP, PTP, maybe others?). We need to add this into the oxide_vpc::VpcCfg object and consume that where it's needed. (That's currently just DHCPv6 replies.)
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 by locating the oxide_vpc::VpcCfg definition and the code that generates DHCPv6 replies. Trace how time-synchronization server settings are currently selected, then determine how NTP, SNTP, PTP, and other applicable protocols should consume the new configuration. Done means VpcCfg exposes the servers and DHCPv6 replies use them, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100