Skip to content
This repository was archived by the owner on Feb 24, 2026. It is now read-only.

workshop-notes-template.md

Latest commit

 

History

History
457 lines (330 loc) · 9.49 KB

workshop-notes-template.md

File metadata and controls

457 lines (330 loc) · 9.49 KB

HoloPort Workshop Notes & Report

Moss on HolOS + Edge Node

Workshop Date: [Date] Location: Sensorica Laboratory, Montreal Facilitator(s): [Names] Attendees: [List]

Workshop Metadata

Field Value
Start Time
End Time
Actual Duration
HoloPort Units Available
Participant Laptops
Network Type [WiFi/Ethernet/Both]

Pre-Workshop Status

Equipment Check

  • HoloPorts tested and functional
  • HolOS ISO downloaded and flashed to USB
  • HolOS installed on demo HoloPorts
  • USB drives prepared (2-3)
  • Moss installers downloaded (macOS, Windows, Linux)
  • Network verified at venue
  • Bootstrap server reachable: curl -I https://bootstrap.holo.host
  • Signal server reachable: curl -I https://signal.holo.host
  • UDP ports 16384-32768 verified open
  • Bandwidth measured: [____] Mbps

Pre-Workshop Issues Encountered

Issue Resolution Time Spent

Workshop Timeline Notes

Part 1: Installing HolOS on HoloPort (45-90 min)

Target Start Time: | Actual Start Time: | Completion Time: | Time Taken: |

Steps & Status

Step Status Notes Time
ISO download + USB flash
BIOS configuration
Installation (~60 sec)
First boot + updates
Network verification
Edge Node container check

Successes

Issues Encountered

Issue Solution Workaround?

Part 2: Verifying Edge Node Container (15-30 min)

Start Time: | Completion Time: | Time Taken: |

Commands Executed

# System status
systemctl status edgenode
# Result:

# Logs
journalctl -u edgenode -f
# Result:

# Holochain process
ps aux | grep holochain
# Result:

Container Status

  • Container running
  • Conductor process active
  • Logs showing no errors
  • Network connectivity confirmed

Successes

Issues Encountered

Issue Solution Workaround?

Part 3: Installing Moss (30-45 min)

Start Time: | Completion Time: | Time Taken: |

Installation Method

  • Method 1: Direct installation on client devices
  • Method 2: Running Moss on Edge Node (server mode)

Client Devices Installation

Device OS Version Status Notes

Edge Node Configuration (if applicable)

# Config file created
cat > ~/moss-config.yaml << 'EOF'
---
self_hosted_happs:
  - app_id: moss
    version: "0.15.0"
    # URL:
EOF

# happ-config load result:
happ-config list

Successes

Issues Encountered

Issue Solution Workaround?

Part 4: Multi-Node Network Setup (60-120 min)

Start Time: | Completion Time: | Time Taken: |

Nodes Configured

Node ID Device Type Role Status IP Address
1 HoloPort Always-on server
2 Laptop Client
3 [Device] Client

Network Configuration

  • All nodes on same network
  • Bootstrap server reachable from all nodes
  • Signal server reachable from all nodes
  • UDP ports verified (if possible)

Peer Discovery Test

# Test results from each node
# Node 1:
# Node 2:
# Node 3:

DHT Sync Timing

  • Initial peer discovery: [____] minutes (expected: 1-2 min)
  • Full DHT synchronization: [____] minutes (expected: 1-2 min)
  • Nodes declaring "full arc": [____] minutes (expected: ~2 min)

Successes

Issues Encountered

Issue Solution Workaround? Used Alternative

Part 5: Demo Flow (45-60 min)

Start Time: | Completion Time: | Time Taken: |

1. Opening Demo (10 min)

  • Multiple devices opened Moss simultaneously
  • New group/workspace created
  • All devices see same group

Notes:

2. Real-Time Collaboration (10 min)

Slate (Collaborative Drawing):

  • Both users draw simultaneously
  • Zero-latency sync demonstrated
  • State preserved after close/reopen

Notes:

Notebooks (Shared Documents):

  • New Markdown document created
  • Multi-device editing tested
  • Conflict-free editing shown

Notes:

3. Communication Tools (10 min)

Vines (P2P Chat):

  • Channel created
  • Encrypted messages sent
  • Real-time appearance verified

KanBan Boards:

  • Project board created
  • Tasks added and cards moved
  • Team coordination demonstrated

Notes:

4. Infrastructure Explanation (10-15 min)

  • HoloPort Edge Node shown
  • docker stats edgenode demonstrated
  • docker logs edgenode --tail 50 shown

Talking points covered:

  • Small device serves entire group's data
  • No monthly hosting fees
  • No vendor lock-in
  • Data lives where group chooses
  • More nodes = redundancy

Notes:

Demo Successes

Demo Issues

Issue Impact Solution

Troubleshooting Log

External Service Status

Service Test Command Status Notes
Bootstrap curl -I https://bootstrap.holo.host
Signal curl -I https://signal.holo.host
TURN [if tested]

Issues Summary

Time Issue Severity Resolution Time to Fix
🟡 Low / 🔴 High

Workarounds Used

  • hc sandbox (single machine simulation)
  • Multiple Docker containers
  • Single-node demo + conceptual explanation
  • Direct Moss on laptops (no HoloPorts)
  • Pre-recorded demo video
  • Other: _______________

Backup Options Used

If any backup options were deployed, document here:

Which backup was activated?

  • Test Moss directly on laptops
  • Docker on laptop Edge Node
  • Pre-recorded success case video
  • Other

Why was it needed?

How did it perform?

Participant Feedback

Overall Reaction

Questions Asked

Question Answer Given Topic Area

Technical Understanding

Concept Understanding Level Notes
P2P architecture
DHT and gossip
Edge Node purpose
Agent-centric data
No central servers

Post-Workshop Summary

What Worked Well

What Didn't Work

Time Management

Part Planned Actual Variance
Part 1: HolOS Install 45-90 min
Part 2: Edge Node Verify 15-30 min
Part 3: Moss Install 30-45 min
Part 4: Multi-Node Setup 60-120 min
Part 5: Demo Flow 45-60 min
Total 4-5 hours

Technical Issues Summary

Critical Issues (Blocking)

Issue Root Cause Resolution Prevention

Minor Issues (Non-blocking)

Issue Root Cause Resolution Prevention

Lessons Learned

Preparation

During Workshop

Content

Equipment

Recommendations for Future Workshops

Technical Improvements

Process Improvements

Documentation Updates Needed

Action Items

Immediate (within 1 week)

  • Share workshop photos/documentation
  • Follow up with specific participant questions
  • Update any documentation based on issues found
  • Report technical issues to Edge Node/Moss teams

Short-term (within 1 month)

  • Plan follow-up session for advanced topics
  • Gather more detailed feedback from attendees
  • Create workshop highlight reel
  • Document any workarounds for community

Long-term

  • Production deployment planning
  • Monthly meetups for ongoing users
  • Advanced workshops (developing hApps)

Appendix

Screenshots/Photos

Network Configuration Details

# Venue network specs
# IP ranges, subnet mask, gateway
# Firewall rules (if known)

# HoloPort network configuration
ip addr show

# Routing table
ip route show

System Logs (Key Sections)

# Edge Node startup logs
journalctl -u edgenode --since "start time" --until "end time"

# Holochain conductor logs
# From: ~/.local/share/holochain/conductor/logs/conductor.log

Configuration Files Used

# moss-config.yaml

External Resources Referenced

Report completed: [Date] Report prepared by: [Name] Share with: [Holo Forum, Sensorica team, etc.]