Ceilometer

Monitoring Network

Registered by fujioka yuuichi

This feature collects the network information(devices, connect statuses and statistices) via North Bound API from the SDN controller.

Blueprint information

Status:
Complete
Approver:
Julien Danjou
Priority:
Low
Drafter:
fujioka yuuichi
Direction:
Approved
Assignee:
fujioka yuuichi
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
Thierry Carrez
Completed by
Julien Danjou

Related branches

Sprints

Whiteboard

Comments:
* Great idea and good progress
* Do you think this is the right abstraction from a ceilometer perspective? How would it work if you don't use a SDN controller .... why not have a generic abstraction instead of flows, tables and switches? Why not add more neutron metrics?

Thank you.
Yes, I think it is enough. Because other meters seem raw data. e.g. "network.incoming.bytes".
I have not thought case that a SDN Controller is not used. I think the meters as defined by this bp should be collect through a SDN Controller. Because, If ceilometer talks to switches directory, It would make large maintenance cost.
When flows, tables and switches are collected, we can figure out some things. e.g. packet count between VMs.
Neutron metrics seem collecting. e.g. network, subnet, port, etc.. -- fujioka

Gerrit topic: https://review.openstack.org/#q,topic:bp/monitoring-network,n,z

Addressed by: https://review.openstack.org/60473
    (WIP)Implements monitoring-network

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.