This is an old revision of the document!
Table of Contents
Pinpoint:
- Proposed name for the project:
Pinpoint - Proposed name for the repository:
pinpoint - Project Categories: Requirements
Project description:
- The overall goal of the Pinpoint project is to provide fault localization framework for NFVI and VIM layers focusing on network issues
- Fault localization target is to deduce the exact source of a failure from a set of observed failure indications while reducing the time spent on analyzing problems.
- Fault localization also identify performance bottlenecks easily revealing the true source of the various symptoms
- Fault localization is also known as fault isolation, alarm/event correlation, and root cause analysis (RCA).
Scope:
- Define the relevant APIs for fault localization system
- Define functional requirements for fault localization block
- Perform gap analysis on existing API, mainly on OpenStack components and SDN controllers
- Out of scope : Fault localization specific algorithm
- Future extensions: Fault localization for compute and storage, Extend for upper layers of NFV (alongside OPNFV evaluation)
Dependencies:
- The project has some relations to the: Doctor, Yardstick and bottleneck OPNFV projects as it may use some of their API
- The project is related to the: Neutron, Nova, Ceilometer and maybe some other OpenStack project as it may use some of their API
- The project is aligned with an activity in IETF LIME group to provide generic model for technology agnostic network OAM
Committers and Contributors:
- Names and affiliations of the committers
Adi Molkho (Huawei: adi.molkho@huawei.com) Mishael Wexler (Huawei: mishael.wexler@huawei.com)
- Names and affiliations of the contributers
Guodayong (Huawei: guodayong@huawei.com ) Adam Itshar (Huawei: adam.itshar@huawei.com) Zhouxingwang (Joe) (Huawei: zhouxingwang@huawei.com )
Planned deliverables
- 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.
Proposed Release Schedule:
- When is the first release planned?
- Will this align with the current release cadence
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name: Project Name (repo name)
Repo name:
Project Category:
Lifecycle State:
Primary Contact:
Project Lead:
Jira Project Name: Same as Project name
Jira Project Prefix: [10 Characters max [A-Z] ]
mailing list tag [Should match Jira Project Prefix]
Committers:
foo@bar.com
baz@qux.com
Link to TSC approval: Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html
Link to approval of additional submitters: Example http://meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-03-15.01.html
