oxidecomputer / oxidecomputer/omicron
NTP: Pushing upstream NTP configuration to virtual machines.
Open
Nobody has claimed this yet.
nexus
virtualization
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
See https://github.com/oxidecomputer/omicron/issues/2219 for fuller context.
This is blocked on https://github.com/oxidecomputer/omicron/issues/2225
- (MVP + 1): We'd like to use the per-sled NTP daemon as the VM's NTP server...
- (MVP): ... But if that's too much, we just need to plumb something - we can point them at the same NTP server used by the whole rack.
- Related; we really just need to be consistent about "which NTP server we use" - they can differ with details like implementation of leap second smearing, which could result in inconsistent time if desynchronized.
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 issues #2219 and #2225, since this issue points to them for context and says the work is blocked. Identify the intended NTP-server choice for virtual machines and the required plumbing; done means VM time synchronization consistently uses the selected upstream NTP source.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100