requirements_projects:data_collection_of_failure_prediction
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
requirements_projects:data_collection_of_failure_prediction [2015/02/16 08:14] Linghui Zeng [Data Category:] |
requirements_projects:data_collection_of_failure_prediction [2015/03/20 22:45] (current) Aric Gardner |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Data Collection: ==== | + | ==== Failure Prediction: ==== |
| * Proposed name for the project: ''data collection for failure prediction'' | * Proposed name for the project: ''data collection for failure prediction'' | ||
| - | * Proposed name for the repository: ''collector'' | + | * Proposed name for the repository: ''prediction'' |
| * Project Categories: ''(Requirements)'' | * Project Categories: ''(Requirements)'' | ||
| Line 30: | Line 30: | ||
| ==== Architecture: ==== | ==== Architecture: ==== | ||
| - | The failure prevention system includes a data collector, a failure predictor and a failure management module. It is shown in the following figure. | + | The whole failure prediction system is made up of a data collector, a failure predictor and a failure management module, which is shown in the following figure. |
| {{ :requirements_projects:collector2.png?300 |}} | {{ :requirements_projects:collector2.png?300 |}} | ||
| - | The data collector consists of Ceilometer and Monasca which can be extended to plugin some other data collectors, e.g. zabbix, nagios, cacti. The predictor analyses data collected by the data collector and send notifications to Doctor module. Doctor module could handle this failure notifications. | + | The data collector consists of Ceilometer and Monasca which can be extended to plugin some other open source data collectors, e.g. Zabbix, Nagios, Cacti. Based on real-time analytics techniques and machine learning techniques, the failure predictor analyses the data gathered by the data collector to automatically determine whether a failure will happen. If a failure is judged, then the failure predictor sends failure notifications to the failure management module (e.g. the Doctor module), which could handle these notifications. |
| - | + | ||
| - | In OPNFV release 1, we limit the scope of this project to the data collector. | + | |
| + | In OPNFV release 2, we limit the scope of this project to the data collector. | ||
| ==== Scope: ==== | ==== Scope: ==== | ||
| __Describe the problem being solved by project:__ | __Describe the problem being solved by project:__ | ||
| As a requirements category project, it plans to solve the problem as following: | As a requirements category project, it plans to solve the problem as following: | ||
| - | * The current OpenStack version Juno is not able to totally realize the data collection of failure prediction management. Based on this, this project is to solve this problem by analyzing the gaps between OPNFV failure prediction and ETSI NFV REL GS, OpenStack Ceilometer project and Monasca project. | + | * The Ceilometer and Monasca projects in OpenStack Juno Release could not collect data as much as possible for a failure prediction system in the OPNFV environment. Due to this drawback, this project is to solve this problem by analyzing the gaps between them. |
| __Specify any interface/API specification proposed:__ | __Specify any interface/API specification proposed:__ | ||
| Line 56: | Line 55: | ||
| __Identify what is in or out of scope. So during the development phase, it helps reduce discussion:__ | __Identify what is in or out of scope. So during the development phase, it helps reduce discussion:__ | ||
| In scope: | In scope: | ||
| - | * Considering the ETSI NFV REL GS version 1.0.0 (2014-11) as one of the input. The conclusion for failure prediction in ETSI NFV REL phase 2.0 before the project’s deadline, will also be considered. | + | * Monasca and Ceilometer as the data collector |
| - | * The ongoing discussion and conclusion of the upstream projects (i.e. Monasca, Ceilometer), before this OPNFV failure prediction’s deadline, shall be considered as parts of the input. | + | * Failure that could be predicted by the failure predictor |
| + | * Data category for failure prediction | ||
| * VIM northbound interfaces | * VIM northbound interfaces | ||
| - | * The user stories of failure prediction | ||
| - | * The monitoring functionality of hypervisors (e.g. KVM, XEN) | ||
| Out of scope | Out of scope | ||
| - | * The ongoing discussion for failure prediction after this OPNFV failure prediction deadline will not be captured in it, e.g. for the ETSI NFV REL phase 2.0, related upstream projects. | ||
| - | * General software design framework for this project. | ||
| * An engine for analyzing collected data and predicting failure. | * An engine for analyzing collected data and predicting failure. | ||
| Line 93: | Line 89: | ||
| * ETSI NFV draft REL GS (v1.0.0, 2014-11) | * ETSI NFV draft REL GS (v1.0.0, 2014-11) | ||
| * ETSI GS NFV REL004 | * ETSI GS NFV REL004 | ||
| + | |||
| + | |||
| + | ===== Key Project Facts ===== | ||
| + | |||
| + | ** Project Creation Date: ** \\ | ||
| + | ** Project Category: ** \\ | ||
| + | ** Lifecycle State: ** Incubation \\ | ||
| + | ** Primary Contact: ** linghui.zeng@huawei.com \\ | ||
| + | ** Project Lead: ** linghui.zeng@huawei.com \\ | ||
| + | ** Jira Project Name: ** Data Collection for Failure Prediction \\ | ||
| + | ** Jira Project Prefix: ** PREDICTION \\ | ||
| + | ** Mailing list tag: ** [prediction] \\ | ||
| + | |||
| ==== Committers and Contributors: ==== | ==== Committers and Contributors: ==== | ||
| + | |||
| Names and affiliations of the committers: | Names and affiliations of the committers: | ||
| * Hai Liu, hai.liu@huawei.com | * Hai Liu, hai.liu@huawei.com | ||
| Line 106: | Line 116: | ||
| ==== Planned deliverables ==== | ==== Planned deliverables ==== | ||
| Described the project release package as OPNFV or open source upstream projects. | Described the project release package as OPNFV or open source upstream projects. | ||
| + | * Potential failure needed to be handled | ||
| * Data category required for failure prediction | * Data category required for failure prediction | ||
| * System capability requirement (e.g. disk space needed) and performance requirement (e.g. how many data needs to be collected per second) | * System capability requirement (e.g. disk space needed) and performance requirement (e.g. how many data needs to be collected per second) | ||
| Line 114: | Line 125: | ||
| ==== Proposed Release Schedule: ==== | ==== Proposed Release Schedule: ==== | ||
| When is the first release planned? | When is the first release planned? | ||
| - | * March, 2015. | + | * May, 2015. |
| Will this align with the current release cadence | Will this align with the current release cadence | ||
| * Yes | * Yes | ||
| - | |||
requirements_projects/data_collection_of_failure_prediction.1424074478.txt.gz · Last modified: 2015/02/16 08:14 by Linghui Zeng
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
