feat: edgenode-flower — Holochain + Flower SuperNode variant#139
Draft
evangineer wants to merge 2 commits into
Draft
feat: edgenode-flower — Holochain + Flower SuperNode variant#139evangineer wants to merge 2 commits into
evangineer wants to merge 2 commits into
Conversation
…rNode Introduces a new Docker image variant (`edgenode-flower`) that runs a Holochain conductor alongside a Flower SuperNode, connected by a Python conductor API bridge (`fl-bridge`). The bridge installs the FL hApp at startup, manages the Flower SuperNode process, and records a ContributionRecord to a local JSONL audit log after each FL round. Audit trail commitment to the participant's Holochain source chain is scaffolded with TODOs pending FL hApp zome deployment. Supports three deployment modes via FLOWER_DEPLOYMENT_MODE: - overlay: Flower connects to an existing SuperLink; bridge audits only - augmented: governance ratification checks before strategy changes apply - decentralized: full Holochain round coordination (scaffolded) New files: - docker/Dockerfile.flower - docker/fl-bridge/bridge.py + requirements.txt - docker/logrotate.d/flower.conf - docker/s6-overlay-flower/ (s6 service tree mirroring s6-overlay-harvester) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…erLink scaffold and README
Aligns implementation with revised pollen PRD (one-edgenode-per-machine topology):
bridge.py:
- Add FL_CLIENT_APP_MODULE + FL_CLIENT_APP_URL; pip-installs ClientApp at
startup and passes --clientapp to flwr supernode
- Add FL_MACHINE_NAME; participant.json and ContributionRecord now carry
both machine-level and org-level identity fields
- Rename build_supernode_cmd -> build_flower_cmd returning (cmd, role);
add _build_superlink_cmd scaffold for Mode C aggregator role
- start_flower_process returns (proc, role); run_bridge_loop logs to
flower-{role}.log so supernode and superlink output are separated
- install_client_app() runs before conductor wait so pip install errors
surface early
Dockerfile.flower:
- Add FL_CLIENT_APP_MODULE, FL_CLIENT_APP_URL, FL_MACHINE_NAME,
FLOWER_SUPERLINK_PORT ENV declarations with inline documentation
- EXPOSE 9093 for SuperLink gRPC (Mode C aggregator role)
- Clarify comment block distinguishing machine vs org identity vars
README.flower.md:
- New: deployment modes table, quick start, full env var reference,
multi-machine federation example, port table, data volume layout,
s6 service table, and relationship to pollen hApp
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
edgenode-flowerDocker image variant that bundles a Holochain conductor with a Flower SuperNode, connected by a Python conductor API bridge (fl-bridge)edgenode-harvesterarchitecture: s6-overlay process supervision, same/datavolume layout, samehapp_tool/happ_config_fileinstall machineryNew files
docker/Dockerfile.flowerflwr, replaces log-harvester withfl-bridgedocker/fl-bridge/bridge.pyContributionRecordper rounddocker/fl-bridge/requirements.txtflwr>=1.13.0docker/logrotate.d/flower.conffl-bridge.logandflower-supernode.logdocker/s6-overlay-flower/setup,conductor,fl-bridge,logrotate-cronDeployment modes (FLOWER_DEPLOYMENT_MODE)
overlay(implemented) — Flower SuperNode connects to an existing SuperLink viaSUPERLINK_URL; bridge records a local JSONL audit trail at/data/flower/contributions.jsonlaugmented(scaffolded) — governance ratification checks before strategy changes are relayed to the SuperNodedecentralized(scaffolded) — full Holochain round coordination with no external SuperLinkKey environment variables
Quick start (overlay mode)
docker build -f docker/Dockerfile.flower -t edgenode-flower docker/ docker run --name edgenode-flower -dit \ -v $(pwd)/holo-data:/data \ -p 4444:4444 -p 4445:4445 -p 9091:9091 \ -e SUPERLINK_URL=grpcs://your-superlink:9093 \ -e FLOWER_INSECURE=true \ -e FL_ORG_NAME=my-org \ edgenode-flowerKnown gaps / TODOs
ContributionRecordvia Holochain app WebSocket — pending FL hApp zome deployment (local JSONL is the current fallback)augmentedmode governance checks — requires FL hAppgovernancezomedecentralizedmode designated-aggregator address resolution from DHTflwr supernodeoutputrun_harvester_tests.shpattern)Test plan
docker build -f docker/Dockerfile.flower docker/succeeds foramd64andarm64upstateFL_HAPP_URLunset: bridge logs warning and idles without crashingSUPERLINK_URLset and a running SuperLink: Flower SuperNode connects and a round completes;contributions.jsonlcontains a record🤖 Generated with Claude Code