BoF: Technical Deep Dive on Challenges getting to the Enterprise E...
summary
Deployable patterns and hard rules: build a known hardware “north star” node, tear one down to inventory ports and Redfish IDs, and use Podman and Ansible operator to run an edge controller as a container that performs health checks, operator-driven config, and store‑and‑forward. Examples: a four‑node HA cluster pattern (lose one node and keep service), K3s/Argo for GitOps, Rocky Linux bootstraps, Nexus/Harbor CDN, console cables for serial recovery. Data strategy favors ephemeral edge retention, business data egress, and aggressive pruning when storage fills. Three‑nook/four‑node clusters and a 6‑week, 700‑hour prototype prove it works.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04Hardware constraints edge computing
- 9:09Integrating automating equipment
- 15:46Data strategies edge trade-offs
- 24:11Lessons early edge strategies
- 32:24Security surprises edge insights
- 41:43Open source stack hardware edge
- 53:20Future edge emerging tech
- 57:59Getting started edge projects
- 1:00:25Closing remarks
related talks
30mApplication Modernization Using Cloud Strangler Pattern and DevOps Best Practices
18mArchitecting Resilient Cloud Native Applications: A Practical Guide to Deployment and Runtime
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
01h 04mLaunching patterns for containers - it's more than just scheduling
27mThere and Back Again
30mContainers and Next Gen Infrastructure Ecosystem
31mDeploying Microservice Architectures with Cloud Foundry
19mKube Me This! Kubernetes Ideas and Best Practices