How openstack/devstack works
Main Components
a) Core Infrastructure Layer:
• Stack Management Scripts (stack.sh, unstack.sh)
• Configuration Management (local.conf, stackrc)
• User Management System (stack user, tempest user)
b) Service Components:
• OpenStack Core Services:
• Nova (Compute)
• Neutron (Networking)
• Keystone (Identity)
• Glance (Image)
• Cinder (Block Storage)
• Horizon (Dashboard)
• Swift (Object Storage)
• Placement
c) Plugin Architecture:
• Neutron Plugins
• Nova Plugins
• Cinder Plugins/Backends
d) Support Systems:
• Database Layer (MySQL/PostgreSQL)
• Message Queue
• Apache Server
• Authentication (LDAP support)
┌─ DevStack Orchestration Layer ─────────────────────┐
• ┌─ Configuration ─┐ ┌─ Deployment Scripts ──────┐ │
• local.conf │ │ - stack.sh │ │
• stackrc │ │ - unstack.sh │ │
• ┘ └────────────────────────────┘ │
• Infrastructure Services ────────────────────────┐ │
• ┌─ Database ─┐ ┌─ Message Queue ┐ ┌─ Apache ──┐ │ │
• MySQL │ │ RabbitMQ │ │ Web Server│ │ │
• ┘ └───────────────┘ └───────────┘ │ │
• OpenStack Core Services ────────────────────────┤ │
• ┌─ Control Plane ─────────────────────────────┐ │ │
• Keystone │ Glance │ Nova API │ Neutron API │ │ │
• ┘ │ │
• ┌─ Storage Services ──────────────────────────┐ │ │
• Cinder │ Swift │ Block Storage Backends │ │ │
• ┘ │ │
• ┘
Key Elements to Highlight
• Blue: Core OpenStack services
• Green: Infrastructure services
• Orange: DevStack management components
• Purple: Plugin systems
• Configuration flow from local.conf to services
• API communications between services
• Storage access patterns
Important Relationships
• How stack.sh orchestrates the entire deployment
• Plugin architecture and extension points
• Demonstrate the relationship between core services
• How authentication flows through the system
Implementation Details
• Use standardized symbols for databases, APIs, and services
• Clear labels for each component
• Configuration file locations and relationships
• Required vs optional components
Deployment Flow
A separate section showing the deployment sequence: