oxidecomputer / oxidecomputer/omicron
NTP: Figure out client & server configuration (e.g., handling of leap seconds)
Open
Nobody has claimed this yet.
Sled Agent
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Once we have a zone for the NTP daemon running (https://github.com/oxidecomputer/omicron/issues/2221), we'll want to be able to plumb configuration info to this daemon. TBD if this is calling an interface, reaching into the zone and tweaking a file, or something else.
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 reading issue #2221 to understand how the NTP daemon zone is created. Determine how client and server configuration, including leap-second handling, should reach the daemon; the work is done when the configuration mechanism and required behavior are defined.
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
- 20/100