How openstack/networking-baremetal works
Main Components
a. Core Components:
• ML2 Plugin Layer (networking_baremetal/plugins/ml2)
• Baremetal Mechanism Driver (baremetal_mech.py)
• Ironic Neutron Agent (networking_baremetal/agent)
• Device Drivers Layer (networking_baremetal/drivers)
• OpenConfig Interface (networking_baremetal/openconfig)
b. External Systems to Show:
• OpenStack Neutron
• OpenStack Ironic
• Physical Network Infrastructure
• Bare Metal Servers
Component Relationships
• Top Layer: OpenStack Services (Neutron, Ironic)
• Middle Layer: networking-baremetal components
• Bottom Layer: Physical Infrastructure
Key Flows
a. Control Flow:
• ML2 Plugin → Baremetal Mechanism Driver
• Mechanism Driver → Ironic Neutron Agent
• Agent → Device Drivers
• Device Drivers → Physical Network Infrastructure
b. Data Flow:
• Network Configuration Updates
• Port Status Changes
• VLAN/LACP Configuration
• OpenConfig Interface Communications
Specific Implementation Details
• Rectangle: Core services (Neutron, Ironic)
• Hexagon: Plugin components
• Diamond: Device drivers
• Rounded Rectangle: Physical infrastructure
Important Subsystems
a. OpenConfig Implementation:
• Interfaces
• LACP
• VLAN
• Network Instance
b. Device Driver Architecture:
• Base Driver
• NetConf Implementation
• OpenConfig Integration
Integration Points
With special connectors:
• Neutron ML2 Plugin Integration
• Ironic API Communication
• Message Queue Connections
• Physical Network Management
Additional Elements
Annotations for:
• Configuration Management
• Error Handling Paths
• Monitoring Points
• High Availability Components
Formatting Guidelines: