Skip to content

feat(technology): place VMs on their virtualization platform - #255

Merged
ionos-landgraf-vin merged 1 commit into
mainfrom
feat/vm-placement
Nov 13, 2026
Merged

ionos-landgraf-vin merged 1 commit into
mainfrom
feat/vm-placement

Conversation

@ionos-landgraf-vin

Copy link
Copy Markdown
Collaborator

Closes #252

Summary

A VM node is placed on its platform through the service that hands out the VMs:

TechnologyNode (vm) -servedBy-> TechnologyService -suppliedBy-> TechnologySystemSoftware (hypervisor) -realizedBy-> TechnologyNode (hosts)

All three relations already exist, so no kind gets a new relation. The PR documents the chain and guards it in lint.

  • Warning (Linter::Structure#vm_without_platform): a vm node that is neither servedBy a service with a suppliedBy, nor realizedBy a TechnologyDevice (a VM on one machine, e.g. the isolated session of a secure workstation already in the examples).
  • No cycles:
    • Pure chain cycles (a hypervisor realized by its own guest) were already errors from validate_relation_cycles; now tested.
    • New error validate_virtualization_cycles: a cycle that mixes the chain with composedOf/aggregates (a host cluster composed of a VM that runs on it). Neither existing check saw it, because each leaves out the other's verbs. It reuses relation_graph/report_cycles (Tarjan) and only reports cycles that use both kinds of verb, so every cycle produces exactly one error.
    • The warning is a fixed two-hop lookup, so it cannot loop.
  • Example: Tech:RegionalCluster:Guests on Tech:Compute:VirtualMachines → Tech:ClusterPlatform:Hypervisor → Tech:RegionalCluster:Host. Tech:RegionalCluster:Hypervisor (a cluster composed of hosts) was typed vm and is now bare-metal.
  • Docs: a "Virtualization" section in the TechnologyNode/Service/SystemSoftware descriptions, plus a "Virtualization" section, rule 15 and a lint-table row in docs/modeling.md.

Out of scope: an inverse "hosts" label on the platform page (incoming relations show the raw verb everywhere).

Test plan

  • Full suite: 2783 runs, 0 failures; rubocop and steep clean
  • archsight lint -r examples/archsight: no errors, no modeling warnings
  • New tests: vm warning (no service, unsupplied service), accepted cases (platform, device, other node types), chain cycle reported once, mixed composedOf cycle reported once, pure composedOf cycle still reported once, nested virtualization accepted, example chain resolves both ways

🤖 Generated with Claude Code

A vm TechnologyNode is servedBy the TechnologyService that hands out the
VMs, which is suppliedBy the hypervisor, which is realizedBy its hosts.
All relations already existed; this documents the chain and guards it:

- lint warns about a vm with no platform (or no device it runs on)
- lint reports a cycle that mixes the chain with composedOf/aggregates
  (a platform containing its own guest), which neither the relation nor
  the hierarchy cycle check saw; pure cycles stay reported once
- example: guests on the regional cluster's compute service
- kind descriptions and a Virtualization section in the modeling guide

Closes #252

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ionos-landgraf-vin
ionos-landgraf-vin merged commit 7ca3d87 into main Nov 13, 2026
8 checks passed
@ionos-landgraf-vin
ionos-landgraf-vin deleted the feat/vm-placement branch November 13, 2026 08:37
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.

TechnologyNode: virtual nodes placed on a virtualization platform

1 participant