Skip to content

define manifest contract - #108

Open
halfcyan wants to merge 16 commits into
mainfrom
cypress/manifest-contract
Open

define manifest contract#108
halfcyan wants to merge 16 commits into
mainfrom
cypress/manifest-contract

Conversation

@halfcyan

@halfcyan halfcyan commented Jul 31, 2026

Copy link
Copy Markdown
Member

Implements issue #98, defining the provider-neutral Odorobo VM manifest contract.

Included

  • VmManifest with explicit desired and observed state
  • CPU, memory, storage, network, placement, boot, cloud-init, and vsock fields
  • Contract validation for versions, resources, storage sources, boot disks, networks, cloud-init, and vsock
  • Explicit unknown-field rejection during deserialization
  • Provider ownership documentation for storage and networking resolution
  • Representative fixtures for minimal, storage-backed, networked, cloud-init, and vsock manifests
  • Serialization, round-trip, validation, and generated-schema tests

This is the base PR for the stacked Cloud Hypervisor abstraction in PR #119.

@halfcyan
halfcyan marked this pull request as ready for review August 1, 2026 22:49
Comment thread odorobo/src/manifest.rs Outdated
Comment thread odorobo/src/manifest.rs
@halfcyan halfcyan linked an issue Aug 17, 2026 that may be closed by this pull request
8 tasks
@TheHeroBrine422
TheHeroBrine422 dismissed their stale review August 24, 2026 22:29

realized i missed that it isnt using ByteSize

@TheHeroBrine422

Copy link
Copy Markdown
Contributor

Just realized I missed a review thing. we were using ByteSize for memory stuff to make conversions and comparisons easy. is there a reason we arent using it in this?

Comment thread odorobo/src/manifest.rs Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define the Odorobo VM manifest contract

2 participants