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.
Edge to cloud simulation
A deterministic three-stage workflow that exposes computation, transfer time, placement, and cost in SimGrid.
Open walkthroughKubernetes real execution
A two-stage container workflow dispatched to a local Kind cluster with persistent data and observable activity logs.
Open walkthroughLocal direct execution
A single trusted host-local command that creates an observable output artifact on the daemon host.
Open walkthroughSLURM batch fixture
A disposable local check of AkôFlow's batch-script, status-sentinel, and artifact-evidence path.
Open walkthrough30 GB network fan-out
A data-intensive workflow for studying parallel transfers, shared bandwidth, and fan-in across three machines.
Open walkthrough100 activities on 50 cores
A reproducible parallel workload for checking core-level placement, queueing, and scheduler scalability.
Open walkthroughHow to use a showcase
- Choose a scenario and download its checked-in YAML files.
- Follow the Desktop tab to import and inspect each object visually, or the API tab to submit the same files.
- Generate or register a plan, start the run, and wait for a terminal status.
- 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
| Scenario | Files | What it demonstrates |
|---|---|---|
| Edge–cloud simulation | examples/simulation | Complete environment, topology, workflow, plan, and execution request |
| 30 GB fan-out | examples/simulation/30gb-fanout | Shared links, parallel transfers, and fan-in |
| 50-core fan-out | examples/simulation/50core-fanout | Per-core placement and parallel capacity |
| Kubernetes with Kind | examples/kind | Local real execution, namespace access, and requests |
| Local direct | examples/local/direct-hello | A trusted host-local command and observed filesystem artifact |
| SLURM batch fixture | examples/slurm/local-fixture | Reproducible local validation of the SLURM adapter's batch submission and artifact path |
| Remote connections | examples/connections | SSH-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.
| Infrastructure | Files | Scope and next step |
|---|---|---|
| SLURM cluster | examples/slurm | A 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. |