oxidecomputer / oxidecomputer/omicron
NTP: Updates to NTP configuration should be possible through Nexus API
Open
Nobody has claimed this yet.
api
nexus
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Although initial configuration should happen through Wicket -> RSS (https://github.com/oxidecomputer/omicron/issues/2218), subsequent NTP updates should be possible through the Nexus API.
This issue tracks integration of those operator endpoints.
Sub-components:
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 the linked issues 2226 and 2227, then review the Nexus API's operator-endpoint integration for NTP configuration updates. The work is done when subsequent NTP updates can be performed through the Nexus API, while initial configuration remains handled through Wicket → RSS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100