oxidecomputer / oxidecomputer/omicron

schema-updater: use DNS

Open
#4,508 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Good for new hires nexus Update System
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

See: https://github.com/oxidecomputer/omicron/blob/ca9d90a79c2a7a9ffdca12a705d007d7f28ce61f/nexus/src/bin/schema-updater.rs#L34

If we could:

  • Infer the rack subnet (perhaps making the assumption we're in the Nexus zone)
  • Send a query using the DNS name, and a resolver pointing to the internal DNS server
  • ... then as a result, we could just send a request to "any available cockroachdb server" rather than a specific one.

This would improve the usability of this tool, as it wouldn't require a manual lookup of the CRDB address.

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.

Research direction

Start at nexus/src/bin/schema-updater.rs around line 34 and trace how the schema-updater currently selects the CockroachDB address. Determine how the rack subnet and internal DNS resolver are identified, then verify the tool can query the DNS name and contact any available CockroachDB server without a manual address lookup.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.