Contributors
Overview
Control Plane Manager (CPMan) adds management capability to control plane in a way to provide higher availability and reliability for ONOS.
The features of CPMan are comprised of two parts: 1) control plane monitoring, 2) enhanced mastership management.
- Control plane monitoring: CPMan monitors various types of control plane metrics that include control message, system metrics.
We collect stats information for six types of control message and those are PACKET_IN, PACKET_OUT, FLOW_MOD, FLOW_REMOVED, STATS_REQUEST, STATS_REPLY.
We also collect stats information for four types of system metrics that include CPU, memory, disk I/O, network I/O.
Note that the monitoring granularity is 1 minute. - Enhanced mastership management: Work-In-Progress.
Architecture
Control message subsystem
This subsystem is used to aggregate and collect various types of control message from network devices. Followings are the components of the subsystem.
- ControlMessageProvider
- Collect and aggregate OpenFlow messages. Note that message aggregation relies on MetricsService.
- Abstract OpenFlow message into protocol agnostic control message type.
- ControlMessageManager
- Transfer the aggregated control message statistics to application layer.
- ControlMessageApplication
- Query and store control message statistics into Round-Robin-Database (RRD) through ControlPlaneMonitor service.
Following table shows the mapping between abstracted message type and OpenFlow message type.
| Abstracted Message Type | OpenFlow Message Type |
|---|
| INBOUND_PACKET | PACKET_IN |
| OUTBOUND_PACKET | PACKET_OUT |
| FLOW_MOD_PACKET | FLOW_MOD |
| FLOW_REMOVED_PACKET | FLOW_REMOVED |
| REQUEST_PACKET | STATS_REQUEST |
| REPLY_PACKET | STATS_REPLY |
Usage
TBD
Terminology
TBD
References