Hyperpush: generic Docker-on-a-VM deployment baseline for frontend and meshable backend

[snowdamiz]

Outcome

Make Hyperpush easy to deploy anywhere with Docker on a generic VM, with a frontend container and a meshable backend cluster that can auto-mesh.

Scope

• Generic Docker-on-a-VM deployment target for the product
• Frontend container + meshable backend deployment model
• Runtime/bootstrap expectations for cluster formation
• The first truthful automatic deploy target for Hyperpush

Acceptance criteria

• A real Hyperpush deployment works on a generic VM with Docker
• The product deploy model is documented and repeatable
• Automatic deployment can truthfully target this platform when configured

Roadmap notes

• Domain: Hyperpush
• Track: Deployment
• Commitment: Committed
• Critical path: 1 + 7

Detailed acceptance criteria

• Product topology is explicit: frontend container plus meshable backend.
• The generic Docker VM reference deployment works.
• Cluster health and bootstrap verification exist for the product deployment path.

Initial sub-issues

• Hyperpush deployment: define frontend plus meshable backend topology #49 — Hyperpush deployment: define frontend plus meshable backend topology
• Hyperpush deployment: ship generic Docker VM reference deployment and cluster health verification #50 — Hyperpush deployment: ship generic Docker VM reference deployment and cluster health verification