oxidecomputer / oxidecomputer/maghemite
Enhance DDM to publish sled-agent information for use by reconfigurator
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
When a new rack is setup via the multirack join service, its sled-agents will be started. But they will be sitting idle waiting for Reconfigurator to tell them what to do. Reconfigurator must have some mechanism to learn about the new rack and new sled-agents so that it can talk to them and start services. This information is not yet in DNS, so we need a secondary path. We discussed using a separate DDM object for announcing information about sled-agents at a JSON blob. This issue represents that strategy.
Contributor guide
No contributing guide indexed for this repository
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 tracing how DDM objects are published and consumed, then follow the multirack join service and Reconfigurator paths named in the issue. The work is done when sled-agent information for a newly joined rack is published as the agreed JSON-backed DDM object and Reconfigurator can use that secondary path to discover the agents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100