{Ba,E}dge Computing Adding Compute to Conference Badges

Sr. Developer Advocate at HashiCorp for Infrastructure and Orchestration @ksatirli Kerim Satirli

Sr. Solutions Architect at HashiCorp and former Site Reliability Engineer @sofixa Adrian Todorov

computing that takes place at or near the physical location of the producer or consumer of data. point of presence mobile datacenter Similar: edge com·put·ing noun

computing that takes place on your conference or event badge, using a SBC and e-paper screen. noun badge com·put·ing

1 The Idea

Speaker Kerim Satirli

Speaker Kerim Satirli conference branding reusable frame low-powered screen

Nomad for job orchestration Raspberry Pi Zero 2 W battery shield

"Wearer" screen Speaker Kerim Satirli

PiDayConf "Nomad" screen "Baedge" screen Allocation: 1a2b3c4d Address: 192.168.0.246 Version: 1.7.5 Nomad Runtime PiDayConf Kerim Satirli Model: 2in7b Revision: v2 BAEDGE

2 The Problem(s)

2.1 Targeting

Problem: not all workers may be eligible for work

Software Support ▪ operating system (type and version) ▪ system-specific device fingerprinting ▪ driver and port availability Hardware Support ▪ CPU architecture and speed ▪ resource availability (disk / memory) ▪ security rating (ports exposed or sealed) Targeting Patterns

Uplinks ▪ wired or wireless (or both) ▪ fall-back uplinks and networks ▪ additional uplink methods Power ▪ hardwired or battery ▪ battery health (cycles, maintenance) ▪ battery percentage vs. required runtime Targeting Patterns, cont'd.

HashiCorp Nomad https:!"nomadproject.io/ Container Orchestration Deploy, manage, and scale containers in production with ease. Application Orchestration Deploy and manage legacy applications without the need to refactor or rewrite. Alternative to Kubernetes Deploy and scale containers without complexity. Multi-Orchestrator Pattern Deploy and scale containers with multiple orchestrators. Multi-OS Support Deploy to Linux, macOS, or Microsoft Windows. Edge Workload Management Globally scale edge deployments with a simple single-cluster topology.

job "baedge" { region = "baedges" datacenters = [“edge"] node_pool = "baedges" type = "system" namespace = "default" priority = 10 constraint { attribute = "${attr.kernel.arch}" value = "aarch64" } group "baedge" { constraint { attribute = "${meta.battery_level}" operator = ">" baedge.nomad.hcl Constraints

node_pool = "baedges" type = "system" namespace = "default" priority = 10 constraint { attribute = "${attr.kernel.arch}" value = "aarch64" } group "baedge" { constraint { attribute = "${meta.battery_level}" operator = ">" value = "33" } constraint { attribute = "${meta.battery_cycles}" operator = "<" value = "400" } constraint { attribute = "${meta.epaper_size}" value = "2in7b" baedge.nomad.hcl Constraints

value = "33" } constraint { attribute = "${meta.battery_cycles}" operator = "<" value = "400" } constraint { attribute = "${meta.epaper_size}" value = "2in7b" } constraint { attribute = "${meta.epaper_revision}" value = "V2" } ephemeral_disk { migrate = true size = 128 sticky = false } baedge.nomad.hcl Constraints

No content

runtime (h) battery capacity (mAh) power consumption (mW) =

runtime (h) = 4.92 h (under max. load)

Power-up? arstechnica.com/science/2023/05/researchers-craft-a-fully-edible-battery

2.2 Connectivity

Problem: not all workers may have healthy backhauls

local-first ▪ limit need for active uplinks ▪ gracefully degrade service ▪ architect for local operations reconnecting ▪ back-off and retry strategy ▪ support for network roaming ▪ alternate backhauls) Connectivity Patterns

data / system integrity ▪ data deduplication strategy ▪ forced updates ▪ manage device replacement lifecycle coverage ▪ continuously evaluate service ▪ map outages (time, physical location) ▪ expand coverage of network Connectivity Patterns, cont'd.

! reception okay'ish frequently disconnects

Connectivity Spectrum Scan (2.4 GHz) 09:12 10:24 11:36 12:48 14:00 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channels

No content

namespace = "default" priority = 10 node_pool = "baedges" constraint { attribute = "${attr.kernel.arch}" value = "aarch64" } group "baedge" { disconnect { ttl = "4h" stop_after = "2h" replace = true reconcile = "keep_original" } ephemeral_disk { migrate = true size = 128 sticky = false } network { mode = "host" baedge.nomad.hcl Disconnect

Observability https:!"grafana.local.workloads.io/

2.3 Applications

Problem: not all workloads may be built "agreeably" built like, well, "

flexible ▪ hot-reload config ▪ functional tiers tolerant ▪ gracefully degrade ▪ easy deployments Application Patterns

observable ▪ predict maintenance ▪ utilize digital twins mindfully replaceable ▪ data inheritance strategy ▪ modular SW / HW architecture Application Patterns, cont'd.

03 Prototyping

""" application """ import importlib import logging import os import platform import qrcode from PIL import Image, ImageDraw, ImageFont import helpers as hlp import config as cfg logging.basicConfig(level=cfg.app["logging"]["level"]) hlp.log_debug(!#name!#, 'detected platform: `' + platform.system() + '`') baedge.py

object: Object containing EPD library and configuration """ hlp.log_debug('initialize_screen', 'init function') try: epd = epd_library.EPD() hlp.log_debug('initialize_screen', 'initialize screen') epd.init() hlp.log_debug('initialize_screen', 'clear screen') epd.Clear() hlp.log_debug('initialize_screen', 'end function') return epd except IOError as e: hlp.log_exception('initialize_screen', e) return None def clear_screen(epd, sleep_screen=False): """ Clear contents on screen baedge.py

"SCaLE" screen

"Nomad" screen "Baedge" screen Allocation: 1a2b3c4d Address: 192.168.0.246 Version: 1.7.5 Nomad Runtime

Camera

This talk wasn't about conference badges.

This talk was about fault tolerance on the edge.

Demo Code github.com/workloads/baedge

Thank you speakerdeck.com/ksatirli