Integrate hero_coordinator for async job orchestration #24

New issue

Closed

opened 2026-02-09 21:06:25 +00:00 by mik-tf · 1 comment

mik-tf commented

2026-02-09 21:06:25 +00:00

Owner

Overview

Add background job processing for long-running operations like deployment provisioning, SLA monitoring, payment settlement, and notification delivery using hero_coordinator.

Hero Component

Binary: hero_coordinator
Purpose: Distributed task scheduling and orchestration
Location: lhumina_code/hero_coordinator/

Use Cases

Deployment Provisioning: Async VM/container creation after purchase
SLA Monitoring: Periodic health checks on active services
Payment Settlement: Scheduled escrow releases
Notification Delivery: Email/push notifications for order updates
Data Sync: Periodic sync between hero_osis and search indexes
Resource Monitoring: Node health and uptime tracking

Implementation Plan

Add hero_coordinator to Docker Compose stack
Define job types and their handlers
Implement job submission from marketplace handlers
Add job status tracking and retry logic
Create admin dashboard for job monitoring
Implement dead letter queue for failed jobs

Acceptance Criteria

Deployment orders trigger async provisioning jobs
SLA monitoring runs on schedule
Failed jobs retry with exponential backoff
Job status visible in provider dashboards

Dependencies

Requires Phase 1 complete
Complementary to #23 (payment integration)

## Overview Add background job processing for long-running operations like deployment provisioning, SLA monitoring, payment settlement, and notification delivery using `hero_coordinator`. ## Hero Component - **Binary**: `hero_coordinator` - **Purpose**: Distributed task scheduling and orchestration - **Location**: `lhumina_code/hero_coordinator/` ## Use Cases 1. **Deployment Provisioning**: Async VM/container creation after purchase 2. **SLA Monitoring**: Periodic health checks on active services 3. **Payment Settlement**: Scheduled escrow releases 4. **Notification Delivery**: Email/push notifications for order updates 5. **Data Sync**: Periodic sync between hero_osis and search indexes 6. **Resource Monitoring**: Node health and uptime tracking ## Implementation Plan 1. Add `hero_coordinator` to Docker Compose stack 2. Define job types and their handlers 3. Implement job submission from marketplace handlers 4. Add job status tracking and retry logic 5. Create admin dashboard for job monitoring 6. Implement dead letter queue for failed jobs ## Acceptance Criteria - [ ] Deployment orders trigger async provisioning jobs - [ ] SLA monitoring runs on schedule - [ ] Failed jobs retry with exponential backoff - [ ] Job status visible in provider dashboards ## Dependencies - Requires Phase 1 complete - Complementary to #23 (payment integration)