How aenix-io/cozystack works
Main Components Identification
The system can be broken down into these major components:
a. Core Components:
• Control Plane (packages/core/platform)
• API Server (cmd/cozystack-api)
• Installer (packages/core/installer)
b. Service Components:
• Database Services (MySQL, PostgreSQL, Redis, etc.)
• Kubernetes Management
• Virtual Machine Management
• Storage Management
• Networking Services
• Monitoring & Metrics
┌─ Control Plane Layer ─────────────────────────┐
• API Server │
• Authentication & Authorization │
• Resource Management │
• ┘
• ↕
┌─ Service Management Layer ────────────────────┐
• ┌─ Infrastructure ─┐ ┌─ Platform Services ─┐ │
• Kubernetes │ │ - Databases │ │
• Virtual Machines│ │ - Message Queues │ │
• Storage │ │ - Caching │ │
• ┘ └──────────────────────┘ │
• ┘
• ↕
┌─ Infrastructure Layer ────────────────────────┐
• Bare Metal Servers │
• Networking │
• Storage Systems │
• ┘
Component Relationships
Following interactions:
• API Server → Service Controllers
• Service Controllers → Infrastructure Resources
• Monitoring System → All Components
• Authentication Flow → API Endpoints
Elements
a. Control Plane:
• API Server (cozystack-api)
• Authentication System (Keycloak)
• Resource Controllers
• Configuration Management
b. Service Management:
• Database Operators (MySQL, PostgreSQL, etc.)
• Kubernetes Management
• Virtual Machine Management
• Storage Management (Seaweedfs)
• Network Services (Ingress, Load Balancers)
c. Monitoring & Operations:
• Metrics Collection (Victoria Metrics)
• Logging System (Fluent Bit)
• Alert Management
• Dashboard System
Additional Details
Annotations for:
• API endpoints
• Security boundaries
• Data flow directions
• Scaling components
• High availability pairs
Implementation Notes
• Use standard architectural symbols
• Clear boundaries between components
• Scalable components
• Security zones
• Backup/recovery paths
• Monitoring points
This system design should reflect Cozystack's ability to:
• Transform bare metal servers into a cloud platform
• Provide REST API for service management
• Support multiple service types (Kubernetes, DBaaS, VMs)
• Handle security and monitoring
• Support both public and private cloud deployments