Mark/mesh-seed
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[Priority 2] Tailnet service discovery automation #7

New issue
Closed
opened 2026-03-10 20:45:42 +00:00 by Mark · 2 comments
Mark commented 2026-03-10 20:45:42 +00:00
Owner
Copy link

Auto-discover mesh services on tailnet.

Services to discover

  • forgejo.tail018ac4.ts.net
  • n8n.tail018ac4.ts.net
  • ldr.tail018ac4.ts.net
  • unstable.tail018ac4.ts.net (Redis, Ollama)

Implementation

  • Query Tailscale API for mesh-tagged nodes
  • DNS resolution for service endpoints
  • Auto-update registry with available services

See

  • IMMEDIATE_INTEGRATION.md (Action 4)
Auto-discover mesh services on tailnet. ## Services to discover - forgejo.tail018ac4.ts.net - n8n.tail018ac4.ts.net - ldr.tail018ac4.ts.net - unstable.tail018ac4.ts.net (Redis, Ollama) ## Implementation - Query Tailscale API for mesh-tagged nodes - DNS resolution for service endpoints - Auto-update registry with available services ## See - IMMEDIATE_INTEGRATION.md (Action 4)
Mark commented 2026-03-14 19:12:06 +00:00
Author
Owner
Copy link

Phase Dependency Mapping

Linked to Phase Tracker: #27 (Phase 0: Foundation MVP) / #29 (Phase 2: Federation)

Prerequisites:

  • Tailscale network configured
  • Basic mesh node operational

Blocks:

  • #19 (Multi-node mesh) - needs service discovery
  • Phase 2 federation features

Context: Bridges Phase 0 infrastructure → Phase 2 scaling
Priority: P1 (enables multi-node)

Acceptance Criteria:

  • Automatic node discovery via tailnet
  • Service registration/deregistration
  • Health checking across nodes
  • DNS resolution for mesh services
## Phase Dependency Mapping **Linked to Phase Tracker:** #27 (Phase 0: Foundation MVP) / #29 (Phase 2: Federation) **Prerequisites:** - Tailscale network configured - Basic mesh node operational **Blocks:** - #19 (Multi-node mesh) - needs service discovery - Phase 2 federation features **Context:** Bridges Phase 0 infrastructure → Phase 2 scaling **Priority:** P1 (enables multi-node) **Acceptance Criteria:** - Automatic node discovery via tailnet - Service registration/deregistration - Health checking across nodes - DNS resolution for mesh services
Mark closed this issue 2026-03-14 20:27:23 +00:00
Mark commented 2026-03-14 20:27:33 +00:00
Author
Owner
Copy link

✅ COMPLETED - Phase 2 Federation

Implementation Summary:

  • Tailscale API integration for node discovery
  • DNS resolution for service endpoints
  • Service type detection (Redis, Ollama, HTTP)
  • Health checks every 60 seconds
  • MeshLedger integration for service registry
  • Prunes stale services (>5 min no heartbeat)

Services Discovered:

  • forgejo.tail018ac4.ts.net
  • n8n.tail018ac4.ts.net
  • ldr.tail018ac4.ts.net
  • unstable.tail018ac4.ts.net (Redis, Ollama)

Usage:

# One-time scan
python substrate/tailnet_discovery.py --scan

# Continuous daemon
python substrate/tailnet_discovery.py --daemon

Files Changed:

  • substrate/tailnet_discovery.py (new)
  • tests/unit/test_tailnet_discovery.py (new)

Verification:

pytest tests/unit/test_tailnet_discovery.py -v
# Tests passing (DNS, health checks, discovery)

Closed as part of Phase 2 completion.

## ✅ COMPLETED - Phase 2 Federation **Implementation Summary:** - Tailscale API integration for node discovery - DNS resolution for service endpoints - Service type detection (Redis, Ollama, HTTP) - Health checks every 60 seconds - MeshLedger integration for service registry - Prunes stale services (>5 min no heartbeat) **Services Discovered:** - forgejo.tail018ac4.ts.net - n8n.tail018ac4.ts.net - ldr.tail018ac4.ts.net - unstable.tail018ac4.ts.net (Redis, Ollama) **Usage:** ```bash # One-time scan python substrate/tailnet_discovery.py --scan # Continuous daemon python substrate/tailnet_discovery.py --daemon ``` **Files Changed:** - substrate/tailnet_discovery.py (new) - tests/unit/test_tailnet_discovery.py (new) **Verification:** ```bash pytest tests/unit/test_tailnet_discovery.py -v # Tests passing (DNS, health checks, discovery) ``` **Closed as part of Phase 2 completion.**
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
mesh-seed#142-gate-verify-pass-07b1f89
Labels
Clear labels   
blocked:children

   
blocked:commit-ready-failed

   
blocked:depends-231

Depends on #231 (Discord Bot Foundation) landing first. Do not pick until #231 is closed.

  
blocked:depends-236

Depends on #236 (Phase 1) landing first. Do not pick until #236 is closed.

  
blocked:depends-237

Depends on #237 (Phase 2) landing first. Do not pick until #237 is closed.

  
blocked:depends-238

Depends on #238 (Phase 3) landing first. Do not pick until #238 is closed.

  
blocked:depends-239

Depends on #239 (Phase 4) landing first. Do not pick until #239 is closed.

  
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-research

   
blocked:needs-attention

Janitor escalated: pipeline terminated without producing expected changes. Human review required.

  
blocked:needs-decision

   
blocked:no-changes

   
blocked:no-procedure

   
blocked:preflight

Preflight check failed

  
blocked:verify-failed

   
bug

Something is broken

  
enhancement

New feature or request

  
feature-request

   
high-priority

Critical path items

  
in-progress

Issue is currently being worked on by a quickfix runner

  
lint-cleanup

Repo lint baseline is dirty

  
needs-decompose

   
needs-triage

   
ops-retry

   
ops-task

Operations task — install, configure, deploy, API calls

  
phase-5

Phase 5 Self-Building Infrastructure

  
quickfix

Pipe to opencode for direct fix

  
security/medium

Medium severity security issue

  
self-building

Autonomous code generation and self-improvement

  
triage-approved

Approved by triage — queued for fixer pipeline

No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/mesh-seed#7
No description provided.