[RFE] Add instrumentation to Neutron

Bug #1475736 reported by Ryan Moats
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Wishlist
Unassigned

Bug Description

In support of operators with more traditional network monitoring infrastructures, add the ability to collect statistics and status from Neutron.

In the first phase, the goal is to be able to fill in the data structures specified in the following RFCs:

2863 - Interfaces Group MIB [1]
4293 - Management Information Base for the Internet Protocol [2]

This stage focuses on collecting the information from components of the reference implementation, aggregating it so that it aligns with the neutron data model and presenting an interface that north bound systems can use to
consume the aggregated data.

Subsequent phases will be driven by operator feedback and requirements.

See the etherpad [3] for more details.

[1] https://tools.ietf.org/html/rfc2863
[2] https://tools.ietf.org/html/rfc4293
[3] https://etherpad.openstack.org/p/neutron-instrumentation

Tags: rfe-approved
Revision history for this message
Kyle Mestery (mestery) wrote :

Where do you plan to store all of these statistics? This could be a large amount of data for a decent sized OpenStack Neutron deployment.

Changed in neutron:
status: New → Confirmed
Ryan Moats (rmoats)
Changed in neutron:
assignee: nobody → Ryan Moats (rmoats)
Revision history for this message
Ryan Moats (rmoats) wrote :

The plan is to (if possible) just harvest available data from where it is currently kept as part of part II (interworking with Ceilometer) rather than provide any internal storage for it.

For data that isn't already available, the plan is to first scope the amount that has to be collected and then let that drive storage implementation.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/204282

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/213474

Revision history for this message
Li Ma (nick-ma-z) wrote : Re: Add instrumentation to Neutron

Any spec proposed for this rfe?

Revision history for this message
Ryan Moats (rmoats) wrote :

no - when this rfe was moved to Confirmed, the requirement was to write up the approach in a devref document - the current draft of which is in the parent commit (https://review.openstack.org/204282)

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

To be discussed at the next drivers meeting.

Changed in neutron:
status: In Progress → Triaged
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

We need to better decouple the protocol choice from the performance monitoring need, but this is a sensible thing to do.

tags: added: rfe-approved
removed: rfe
Changed in neutron:
status: Triaged → In Progress
Ryan Moats (rmoats)
description: updated
Changed in neutron:
status: In Progress → Triaged
status: Triaged → In Progress
importance: Undecided → Medium
Changed in neutron:
importance: Medium → Wishlist
Changed in neutron:
milestone: none → mitaka-1
Changed in neutron:
milestone: mitaka-1 → mitaka-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/204282
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1f329c5d012fa5d17dea5c48121c2820d70c9bb7
Submitter: Jenkins
Branch: master

commit 1f329c5d012fa5d17dea5c48121c2820d70c9bb7
Author: Ryan Moats <email address hidden>
Date: Tue Jul 21 16:52:56 2015 -0500

    Add instrumentation devref, Part I

    Presents what instrumentation is available from VIFs in Nova,
    Metering Lables and Rules, Linux Bridge, and OVS. Proposes
    mappings for structures defined in RFC 2863 and RFC 4293 and
    the method that will be followed for a data collection proof
    of concept.

    How to aggregate and consume these counters will be covered
    in future patch sets that extend this devref.

    Change-Id: I6c1ad0c4cf60d0069c5e057d77f75c12b04a020c
    Partial-bug: #1475736

Changed in neutron:
milestone: mitaka-2 → mitaka-3
Henry Gessau (gessau)
summary: - Add instrumentation to Neutron
+ [RFE] Add instrumentation to Neutron
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Changed in neutron:
milestone: mitaka-3 → none
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron-lib (master)

Reviewed: https://review.openstack.org/279159
Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=6d82b903b1663aeb3416d3693d7363ce15ca39ba
Submitter: Jenkins
Branch: master

commit 6d82b903b1663aeb3416d3693d7363ce15ca39ba
Author: RYAN D. MOATS <email address hidden>
Date: Thu Feb 11 10:20:13 2016 -0600

    Add Collector Agent type string

    Collector proof of concept [1] introduces a new agent type, which
    needs to be reflected here.

    [1] https://review.openstack.org/#/c/213474

    Change-Id: Ifddd095b99b29937c607979097487a32ceea75cd
    Partial-Bug: 1475736
    Signed-off-by: RYAN D. MOATS <email address hidden>

Changed in neutron:
status: In Progress → Incomplete
assignee: Ryan Moats (rmoats) → nobody
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Ryan Moats (<email address hidden>) on branch: master
Review: https://review.openstack.org/213474
Reason: Abandoning as I will not have time to work on this for the foreseeable future

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.