oxidecomputer / oxidecomputer/omicron
NTP: Configuration information for NTP should be transferred from RSS -> Nexus -> CRDB
Open
Nobody has claimed this yet.
database
nexus
Sled Agent
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
See: https://github.com/oxidecomputer/omicron/issues/2218
Once RSS has this information, it should pass it upward to Nexus (like the x.509 certs) so Nexus can store it in CRDB for future reference.
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 #2218 and tracing the existing x.509 certificate transfer from RSS to Nexus. Identify the RSS, Nexus, and CRDB entry points involved in storing NTP configuration; done means the configuration reaches Nexus and is persisted in CRDB for future reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100