Довідник
Технічна довідка для публічної платформи OpenFactory. Console і API responses , source of truth для стану конкретної збірки.
Швидкі посилання
| Reference | Description |
|---|---|
| MCP integration | Connect MCP client to OpenFactory |
| Recipe schema | Canonical BuildRecipe fields |
| Assertion types | Executable VM-test assertions |
| ServiceNow integration | Optional, disabled-by-default ITSM hooks |
Build records мають окремі outcomes
Do not infer verification from image-build status alone. Build record tracks at least three distinct concerns:
| Concern | Typical values | Meaning |
|---|---|---|
| Image build | queued, planning, configured, building, finalizing, completed/built, failed | Whether image production reached terminal result |
| Tests | not_run, running, passed, failed, error, or skipped | Whether attached verification run executed and what it found |
| Certification | certified, uncertified, repairing, or another explicit gate state | Whether artifact met current certification contract |
Completed image with failed, errored, skipped, or absent tests is not certified image. Use all three fields when automating promotion or download decisions.
Build outputs
Outputs depend on build target and which stages completed. Record may provide ISO or disk image, normalized recipe, build logs, test evidence. Treat item as available only when build response supplies artifact metadata and download endpoint succeeds.
Zone 2 snapshots in VM management capture governed persistent overlay. They are not full libvirt memory-and-disk snapshots and not build artifacts.
Base images
Selectable versions change as upstream sources and OpenFactory adapters change. Use console current base-image picker or validated recipe response, not copied version list, when creating automation. See Base images for selection guidance and limitations.
Support
- Console: console.openfactory.tech
- Email: support@openfactory.tech