OpenCHAMI Weekly Digest

A solid week across fabrica, metadata-service, and ochami — including the first ochami v0.6.1 patch and a fresh fabrica v0.4.0 release that lines up with the kubebuilder-style versioning work.

Highlights

  • fabrica v0.4.0 ships kubebuilder-style versioning: fabrica v0.4.0 is the first release to incorporate the kubebuilder-style versioning landed via PR #27. The shape of fabrica’s resource API is now closer to Kubernetes conventions.
  • metadata-service catches up to fabrica’s pre-release: metadata-service PR #4 by alexlovelltroy upgrades to the new fabrica pre-release and addresses legacy compatibility — a coordinated bump across the two repos.
  • Lowercase resources work cleanly in fabrica: fabrica PR #32 from bmcdonald3 fixes a usability papercut: adding a lower-case resource now just works. Paired with PR #33 which corrects the example-4 documentation.
  • ochami v0.6.1 with power-status display: ochami v0.6.1 lands PR #58 — power status is now visible directly from the CLI.
  • magellan documentation, log messages, and tests: magellan PR #126 from davidallendj bundles a wave of correctness improvements: bug fixes, clearer log output, updated docs, and new regression tests.
  • Profile-based cloud-init metadata explored: metadata-service PR #3 experiments with a profile query parameter for cloud-init metadata handlers. Closed for now; pattern likely to resurface.
  • JSON/YAML input for magellan collect: New feature request magellan #128 — let collect accept JSON or YAML input so it composes with other tooling.
  • fabrica package generation feature closed: fabrica #26 from jacobsalmela on generating api packages for existing modules resolved this week.

New & Notable PRs

Issues to Watch

Releases

Contributor Thanks

  • alexlovelltroy — coordinated the fabrica + metadata-service version bump.
  • bmcdonald3 — the fabrica DX fixes (lowercase resources, example docs) make the framework friendlier.
  • cjh1 — power status in the CLI lands in v0.6.1.
  • davidallendj — magellan correctness sweep with regression coverage.

What’s next?

  • Pick up magellan #128 to round out tooling interop.
  • Watch for follow-up fabrica releases that fully shake out the kubebuilder transition.
  • Continue propagating the fabrica v0.4 patterns into downstream services beyond metadata-service.

Proposed Blog Titles

  1. “Kubebuilder-Style Versioning Comes to fabrica v0.4.0”
  2. “ochami v0.6.1 Brings Power Status to Your Terminal”
  3. “Inside magellan’s Recent Quality Sweep: Logs, Tests, and Docs”
  4. “Coordinated Releases: How metadata-service Catches Up With fabrica”