Component Matrix

PhotonCloud is intended to validate meaningful service combinations, not only a single all-on deployment. This page separates the compositions that are already exercised by the VM-cluster harness from the next combinations that still need dedicated automation.

Validated Control Plane

chainfire + flaredb + iam

Validated Network Provider Layer

prismnet
prismnet + flashdns
prismnet + fiberlb
prismnet + flashdns + fiberlb

These combinations justify the existence of the network services as composable providers rather than hidden internal subsystems.

Validated VM Hosting Layer

plasmavmc + lightningstor
plasmavmc + coronafs
plasmavmc + coronafs + lightningstor

This split keeps mutable VM volumes on CoronaFS and immutable VM images on LightningStor object storage.

Validated Kubernetes-Style Hosting Layer

k8shost + prismnet
k8shost + flashdns
k8shost + fiberlb
k8shost + prismnet + flashdns + fiberlb

Validated Edge And Tenant Services

apigateway + iam + prismnet
nightlight
creditservice + iam
deployer + iam + chainfire

Next Compositions To Automate

plasmavmc + prismnet
plasmavmc + prismnet + coronafs + lightningstor
nightlight + apigateway
creditservice + iam + apigateway

Validation Direction

The VM cluster harness now exposes:

nix run ./nix/test-cluster#cluster -- matrix
nix run ./nix/test-cluster#cluster -- fresh-matrix

fresh-matrix is the publishable path because it rebuilds the host-side VM images before validating the composed service scenarios.

1.6 KiB Raw Blame History