Rename SFQM --> telemetry4nfv OR Barometer
The ability to monitor the Network Function Virtualization Infrastructure (NFVI) where VNFs are in operation will be a key part of Service Assurance within an NFV environment, in order to enforce SLAs or to detect violations, faults or degradation in the performance of NFVI resources so that events and relevant metrics are reported to higher level fault management systems. If fixed function appliances are going to be replaced by virtualized appliances the service levels, manageability and service assurance needs to remain consistent or improve on what is available today. As such, the NFVI needs to support the ability to monitor:
- Traffic monitoring and performance monitoring of the components that provide networking functionality to the VNF, including: physical interfaces, virtual switch interfaces and flows, as well as the virtual interfaces themselves and their status, etc.
- Platform monitoring including: CPU, memory, load, cache, themals, fan speeds, voltages and machine check exceptions, etc.
All of the statistics and events gathered must be collected in-service and must be capable of being reported by standard Telco mechanisms (e.g. SNMP), for potential enforcement or correction actions. In addition, this information could be fed to analytics systems to enable failure prediction, and can also be used for intelligent workload placement.
The output of the project will provide interfaces to support monitoring of the NFVI. The project will start off with developing plugins for collectd (a system statistics collection daemon) to enable the collection of platform stats and events and relay gathered information to fault management applications or the VIM. The scope is limited to collecting/gathering the events and stats and relaying them to a relevant endpoint. The project will not enforce or take any actions based on the gathered information.
The project will work with functest to test the provided functionality.
- Architecture Specification
- Release Notes
- Configuration guide
- User guide
- The relevant upstream project for this contribution is collectd.
- The project will work with the Doctor project and the VES project from a feature perspective to provide both projects with NFVI metrics and events.
- The project will work with Releng, Octopus, OPNFV docs, Fuel and functest for each release.
- For the integration and test requirements, there is a dependency on currently available Pharos hardware
Planned Deliverables: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=57&view=detail&selectedIssue=SFQM-37
Project plan per the milestones described at Danube.
|(MS0) Open Intent to Participate||Done|
|(MS1) Planning complete (scenarios or deliverables defined)||Done|
|(MS2) Detailed test case descriptions communicated to test project teams||11/22/16|
|(MS3) Installer integration with OpenStack completed||11/30/16|
|(MS4) Infrastructure updates completed||12/6/16|
|(MS5) Scenario integration and Feature Freeze completed||1/13/17|
|(MS6) Test cases implemented, preliminary documentation completed, and stable branch open||1/26/17|
|(MS7) Stable branch window close||3/10/17|
|(MS8) Formal test execution completed||3/20/17|
|(MS9) JIRA issues assigned to release closed or deferred||3/22/17|
|(MS10) Documentation completed||3/24/17|
(MS11) Release Danube 1.0
(MS12) Release Danube 2.0
|(MS13) Release Danube 3.0||6/8/17|
Key Project Facts
Project Name: Barometer
Repo name: barometer
Primary Contact: Maryam Tahhan
Project Lead: Maryam Tahhan
Jira Project Name: Same as Project name
Jira Project Prefix: barometer
mailing list tag [barometer]
*Link to TSC approval: http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-10-25-05.00.html
Link to approval of additional submitters: