oxidecomputer / oxidecomputer/omicron

NTP: Tracking Issue

Open
#2,219 0 comments 0 reactions 1 assignee View on GitHub

@citrus-it is already working on this.

Since May 10, 2023.

api bootstrap services nexus Sled Agent wicket
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

See: RFD 34

  • #2220
    • #2221
    • #2222
  • #2223
  • NTP: On Scrimlet: Also spin up zone running NTP server. It's probably the same daemon, but this one acts as a server too.
    • See also: #2218
    • #2224
  • #2225
    • #2226
    • #2227
  • #2228
    • #2269
  • TBD: How are we bootstrapping the address discovery here? Probably want to use an AZ-wide subnet (similar to DNS) and post up the Scrimlet services on a well-known address. Either way: Gimlet daemons (as clients) need to be able to find and access the Scrimlet daemons (servers) to synchronize with them.
  • https://github.com/oxidecomputer/omicron/issues/2310
  • https://github.com/oxidecomputer/omicron/issues/2311

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.