How intel/intel-inb-manageability works
Main Components
a) Agent Layer (Core Services):
• Dispatcher Agent (central coordinator)
• Configuration Agent
• Diagnostic Agent
• Telemetry Agent
• Cloud Adapter Agent
b) Communication Layer:
• MQTT Broker (messaging backbone)
• Protocol Buffers (for INBS communication)
c) External Interfaces:
• Cloud Services (Azure IoT Central, ThingsBoard)
• INBC Command Line Tool
• Docker Registry
• Package Repositories
d) Security Components:
• TPM Module
• AppArmor Profiles
• Signature Verification
Architectural Patterns to Highlight
a) Microservices Architecture:
• Agent as an independent service
• MQTT message paths between services
b) Plugin Architecture:
• Cloud adapter interfaces
• OTA update mechanisms (FOTA, SOTA, AOTA)
[Cloud Layer]
Azure IoT Central <-> ThingsBoard <-> Custom Cloud
• ↕
[Security Layer]
TPM | AppArmor | Signatures
• ↕
[Communication Layer]
MQTT Broker <-> Protocol Buffers
• ↕
[Agent Layer]
Cloud Adapter Agent
• ↕
Dispatcher Agent ←→ Configuration Agent
• ↕
Diagnostic Agent ←→ Telemetry Agent
• ↕
[System Layer]
Docker | OS | Firmware | BTRFS
Important Relationships
• Dispatcher Agent as the central coordinator
• MQTT broker as the communication backbone
• Bidirectional flows between agents
• Security layer spanning across components
• External interface connections
Implementation Details
• Version/update flows for FOTA/SOTA/AOTA
Additional Elements
• Manifest flow paths
• Telemetry data routes
• Configuration paths
• Security checkpoints
• Rollback paths