Infrastructure Blueprints

Infrastructure Blueprints

CONCEPT:AU-OS.deployment.infrastructure-blueprint-library — Infrastructure Blueprint Library

Reusable Docker Compose / Swarm stack definitions for company software. Each blueprint includes resource requirements, DNS configuration, and KG topology registration metadata.

📦 Available Blueprints

🚀 Deployment Flow

1. Select blueprint from catalog
2. Check host capacity (availableMemoryMB, availableCPU)
3. Deploy via portainer-mcp create_standalone_stack
4. Register DNS record via technitium-dns-mcp
5. Create CompanySoftware node in KG
6. Create DeploymentBlueprint → CompanySoftware edge
7. Create CompanySoftware → InfrastructureHost edge

📁 Blueprint File Layout

infrastructure-blueprints/
├── SKILL.md              # This file
└── company-software/
    ├── erpnext.yaml
    ├── akaunting.yaml
    ├── twenty-crm.yaml
    ├── docassemble.yaml
    ├── orangehrm.yaml
    └── docuseal.yaml

🔧 Blueprint YAML Format

Each blueprint follows this schema:

name: erpnext
description: Full-featured open-source ERP system
category: accounting
version: "15.0"
requires:
  memory_mb: 2048
  cpu_cores: 2.0
  gpu: false
dns_rewrite: erp.knuckles.team
mcp_server: null  # or 'erpnext-mcp' if available
stack_file: |
  version: "3.8"
  services:
    app:
      image: frappe/erpnext:v15
      ...

🤖 Agent Usage Guide

• Use portainer-mcp create_standalone_stack to deploy
• Use technitium-dns-mcp add_record for DNS
• Use graph-os graph_write to register in KG topology
• Check host capacity before deployment via portainer-mcp docker_get_system_df