Skip to main content

Workflow showcase

Start from a complete, runnable workflow instead of assembling isolated payloads. Every showcase includes the workflow graph, infrastructure inputs, planning data, execution request, expected evidence, and two equivalent paths: AkôFlow Desktop and API.

How to use a showcase

  1. Choose a scenario and download its checked-in YAML files.
  2. Follow the Desktop tab to import and inspect each object visually, or the API tab to submit the same files.
  3. Generate or register a plan, start the run, and wait for a terminal status.
  4. Compare planned and observed makespan, cost, activity placement, transfers, and provenance.

The files are the source of truth. Walkthroughs refer to them directly so the graphical path and API path exercise the same model.

Example file index

ScenarioFilesWhat it demonstrates
Edge–cloud simulationexamples/simulationComplete environment, topology, workflow, plan, and execution request
30 GB fan-outexamples/simulation/30gb-fanoutShared links, parallel transfers, and fan-in
50-core fan-outexamples/simulation/50core-fanoutPer-core placement and parallel capacity
Kubernetes with Kindexamples/kindLocal real execution, namespace access, and requests
Local directexamples/local/direct-helloA trusted host-local command and observed filesystem artifact
SLURM batch fixtureexamples/slurm/local-fixtureReproducible local validation of the SLURM adapter's batch submission and artifact path
Remote connectionsexamples/connectionsSSH-based PlaFRIM, Santos Dumont, and Kind connections

Infrastructure configuration references

These files model infrastructure inputs, but are not end-to-end showcases. In particular, they do not include a portable cluster, a submitted run, or observed execution evidence.

InfrastructureFilesScope and next step
SLURM clusterexamples/slurmA catalog for a partition, login node, shared storage, and runtime bindings. Pair it with an approved SLURM cluster and follow Connect an HPC and SLURM cluster before submitting a site-approved probe. The separate SLURM batch fixture validates only the local adapter path.