oxidecomputer / oxidecomputer/maghemite
ddm-package: remove binaries from zone image
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
Per the following
- https://github.com/oxidecomputer/maghemite/pull/45
- https://github.com/oxidecomputer/omicron/issues/2633
The ddmd binary should be a part of the ramdisk and not a part of a zone image due to private OS interface consumption. Until ddmd is packaged on the ramdisk, we still need the binary in the zone image. However, once that happens, ddmd should be removed from the zone image. Here is what the image currently looks like.
$ tree
.
├── opt
│ └── oxide
│ └── mg-ddm
│ ├── bin
│ │ ├── ddmadm
│ │ └── ddmd
│ └── pkg
│ └── ddm_method_script.sh
└── var
└── svc
└── manifest
└── site
└── mg-ddm
└── manifest.xml
11 directories, 4 files
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 with the ddm package and zone-image build entry points, then read the linked maghemite pull request and omicron issue to determine whether ddmd is now packaged in the ramdisk. Once that prerequisite is satisfied, verify the image tree no longer contains ddmd while retaining ddmadm, ddm_method_script.sh, and the service manifest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100