Back to Research
akoflow / connections-hybrid-local-cloud-profile

Hybrid local to GCP — portable local profile

Import into Desktop
Import version

Choose import version

akoflow::o/akoflow/connections-hybrid-local-cloud-profile:v2

Run the original two-activity producer/consumer fixture on local Docker; verify actual file handoff and receipt contents. GCP/Kind placements remain separate optional reference configurations and are not measured by this local profile.

Public experiment
Published workflow2 activitiesRead only

Loading workflow canvas…

Drag the canvas to pan · Scroll to zoom · Select an activity to inspect its definition
README

Hybrid local to GCP: portable local profile

Execute the original producer/consumer file-content checks in two Docker activities on one local host. The local profile verifies actual file handoff and receipt content. It does not measure GCP provisioning, Kubernetes placement, or cross-cloud networking.

The original cloud placement definition remains available as a separate historical version in Hub. It requires the GCP/Kind setup from the documentation. The words cloud consumed in the receipt are an inherited fixture label, not evidence that a cloud VM was used.

Activities and data

  1. produce writes the original synthetic fixture akoflow-local-to-gcp to handoff.txt.
  2. AkôFlow materializes this declared dependency into the consumer workspace.
  3. consume checks the exact bytes and writes receipt.txt. Each activity records its successful completion after the content checks pass.

The fixture is generated inline; no external dataset, account or secret is needed for this local profile.

Local execution

Install Go 1.23+ for the standalone command, or use AkôFlow Desktop/server with Docker. From this directory:

./prepare.sh && ./run.sh && ./validate.sh

For the daemon, import environment.yaml, scope.yaml, topology.yaml, and the digest-pinned YAML returned by Hub. Build a plan and execute it locally. Review the runtime configuration before choosing any original cloud placement variant.

Public Hub version and measured execution

Open this workflow and its results · Documentation

Import into AkôFlow Desktop

Create workflow → Import from Hub → paste this immutable URI:

akoflow://hub/publications/a057adf4-35da-4f7f-95c1-2a28651c66cd/versions/2

The URI imports the workflow definition. Build or pull the public image and register the companion environment.yaml, scope.yaml, and topology.yaml from this source bundle before planning a local execution. No hosted account, GPU or cloud capacity is required for this CPU profile.

Image: busybox@sha256:73aaf090f3d85aa34ee199857f03fa3a95c8ede2ffd4cc2cdb5b94e566b11662.

Actual homeserver results

Run hubv1-showcase-hybrid-local-cloud-profile-local-20e3b38d5e-run-20261115t062433.257379903 completed 2/2 activities in 1.382106065750122 seconds. These are measured Docker-backed computations, not simulated timing. The captured manual plan uses placeholder predicted timings; those predictions are not benchmark measurements. Use the observed execution metrics for performance analysis. Cost is the configured local compute cost and excludes electricity and hardware.

Download the native experiment capture. The Hub Results tab includes the same plan, attempts, metrics and logs.

Inputs and outputs

Input fixtures and their generation code are in this bundle's data/ and scripts/ directories; inspect them together with the workflow definition and bundle configuration for profile assumptions. Fixtures are generated by the included code unless a bundle identifies an upstream dataset. No repository-wide LICENSE file is currently present: inspect the bundle and upstream terms before redistributing source or data; publication here does not grant additional rights. Outputs expected from this workflow:

  • handoff.txt
  • receipt.txt

Download the actual validated output files.

Images from this validated execution

Measured activity runtimes

Illustrated walkthrough

The following reference screenshots come from the documentation walkthrough. The current measured run is recorded separately above.

Images & executables

Software referenced by the published workflow.

OCI

busybox@sha256:73aaf090f3d85aa34ee199857f03fa3a95c8ede2ffd4cc2cdb5b94e566b11662

Used by produce, consume.

Execution environment

Configuration from the original capture.

showcase-hybrid-local-cloud-profile local Docker

CPU-only local execution; no remote capacity is provisioned

Version showcase-hybrid-local-cloud-profile-v1

Local Docker hostmachine
4 CPU cores8 GiB memory

Execution runtimes

Local Docker host · local · execution

RECORDED OBSERVATIONS

What actually ran

Workflow v2 · Original execution identifiers and measured values.

Executions

1 records
executionstatusalgorithmduration Secondsrecorded Cost USD
hubv1-showcase-hybrid-local-cloud-profile-local-20e3b38d5e-run-20261115t062433.257379903completedmanual1.3821060

Executions record

Complete original fields from the recorded snapshot.

REPRODUCIBILITY

Workflow versions

Inspect immutable definitions, compare changes and download a version.

Published versions

2 records
versionmessagepublishedresultsDetails
v2Official showcase: measured homeserver execution using a public immutable imageNov 15, 20261
v1Original cloud placement reference; cloud infrastructure execution is not claimed by this local profileNov 15, 20260

Published versions record

Complete original fields from the recorded snapshot.

Experiment results

All published executions across workflow versions. Open an execution to inspect its recorded data.

All experiment results

1 records
executionworkflow Versionstatusmodeduration Secondsrecorded Cost USD
hubv1-showcase-hybrid-local-cloud-profile-local-20e3b38d5e-run-20261115t062433.257379903v2completedreal1.3821060657501220

All experiment results record

Complete original fields from the recorded snapshot.