Neutron Network Statistics
This is a proposal to add statistics for networking related resources to Neutron including the Neutron APIs and required underlying instrumentation. Specifically, the current APIs, https:/
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Peter Erik Mellquist
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
Another proposal is being discussed in the context of bug 1475736
---------------
This is a proposal to add statistics for networking related resources to Neutron including the Neutron APIs and required underlying instrumentation. Specifically, the current APIs, https:/
Data Model and API Ideas
Read networking stats
-------
GET /networks/
Here we have a network which is comprised of zero or more subnets which can be shared or exclusive to a tenant. Stats provide an overall statistics view of the network including all subnets within.
Status : [up,down,error]
Usage : [sum of Tx and Rx packets]
ReceivedRate : [Rate of data received in kB/sec]
TransmittedRate : [Rate of data transmitted in kB/sec]
PacketTx : [total # of packets transmitted since reset]
PacketRx : [total # of packets received in since reset]
Clear stats
-------
POST /networks/
Reset all the counters.
{
action:reset
}
Subnet
-------
GET /subnets/
GET /subnets/
Port
-------
GET /ports/{port-id}
GET /ports/
Router
-------
GET /routers/
GET /routers/
Floating IP
-------
GET /floatingips/
GET /floatingips/
Other
-------
GET /otherQuantumOb
Additonal Notes
-------
* read only, a way to reset them, a way to sample over a period
* how are things running, how to I calculate performance, how can i see faults, traffic monitoring
* based on SNMP( router, rmon ), Netconf, sFlow, Vswitch counters TBD although source is not exposed, it is abstracted. Community would propose and review for each object type.
* schemas needed, these will need to evolve over time
* not extensions, common metrics
* performance, counters, faults ( FCAPS F and P )
Status: up, down, error
Summary Usage (KBps)
Rx, Tx ( bytes, packets)
ReceivedRate, TransmittedRate KBps)
errRX, errTx