This is an old revision of the document!
data collection of failure prediction
opnfv-fp-dc
(Requirements)
Failure prediction is an important step of a failure prevention system, which could be deployed to help the NFV system avoid the operational failure in the real time environment.
Core technology of failure prediction is big data, it requires different kinds of data as enough as possible. The data come from log files, real time parameters of hardware and software, environment parameter, etc.
For failure prediction, the first step should focus on data collection. Failure predictor can get data from a list of softwares: Ceilometer of Openstack, OSS, VNFM and others. In OPNFV first release, we need to identify which kind of data are needed and analyses the gap of Ceilometer.
Failure prediction has been studied in ETSI NFV ISG, and there also has developed some general requirements, which should be the initial input for this topic in OPNFV.
For example, in NFV GS Draft ETSI GS NFV-REL 001 (v1.0.0, 2014-11), failure prediction has collected several requirements have been captured as below:
While Fault Management topic shall also be one of the important issues in ETSI NFV Phase 2, so it is possible that such requirements for fault prediction would be updated or enriched during the period of this OPNFV project, if it happens, then the updated part will be captured as well in this project.
While considering the upstream projects, there also have existed some projects in this area, e.g. - the Ceilometer project in OpenStack for system resource monitoring; - the new project proposal “Time Series Data Repository (TSDR)” in OpenDaylight for ODL system monitoring.
However, they do not cover all specific requirements in the OPNFV environment. Therefore our first task is to investigate the gaps between those upstream projects, other OpenStack components and the OPNFV requirements. After that, we plan to deliver some documents on the VIM northbound API, implementation architecture and plan. Finally, we need to realize the failure prediction framework.
Describe the problem being solved by project: As a requirements category project, it plans to solve the problem as following:
Specify any interface/API specification proposed: Additional interface specifications:
Specify testing and integration:
Identity a list of features and functionality will be developed:
Identify what is in or out of scope. So during the development phase, it helps reduce discussion: In scope:
Out of scope
Describe how the project is extensible in future: The achievements of this project will be used as the input for next stage, e.g. Integration & Testing, and Collaborative Development.
Specify testing and integration like interoperability, scalability, high availablity
Identify similar projects is underway or being proposed in OPNFV or upstream project
Identify any open source upstream projects and release timeline.
Identify any specific development be staged with respect to the upstream project and releases.
Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.
Names and affiliations of the committers:
Any other contributors: TBD
Described the project release package as OPNFV or open source upstream projects.
If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.
When is the first release planned?
Will this align with the current release cadence