User Tools

Site Tools


doctor:project_proposal

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doctor:project_proposal [2014/11/28 11:31]
Ashiq Khan [Planned deliverables]
doctor:project_proposal [2014/12/05 06:48] (current)
Ashiq Khan [Proposed Release Schedule:]
Line 1: Line 1:
-*** UNDER DEVELOPMENT *** 
- 
 ==== Fault Management and Maintenance:​ ==== ==== Fault Management and Maintenance:​ ====
  
Line 9: Line 7:
 ==== Project description:​ ==== ==== Project description:​ ====
  
-This project aims at developing requirements for Network Functions Virtualisation ​Infrastructur ​(NFVI) fault detection and notification through the norhtbound ​interface of Virtualised Infrastructure Manager (VIM). Such notification would be sent to Virtualised Network Function Manager (VNFM) or the NFV Orchestrator (NFVO). NFVI faults include fault in compute, network and storage resources, as well as other elements of NFVI e.g. hypervisor. Faults in all elements in NFVI shall be handled in a step-by-step fashion.+This project aims at developing requirements for Network Functions Virtualisation ​Infrastructure ​(NFVI) fault detection and notification through the northbound ​interface of Virtualised Infrastructure Manager (VIM). Such notification would be sent to Virtualised Network Function Manager (VNFM) or the NFV Orchestrator (NFVO). NFVI faults include fault in compute, network and storage resources, as well as other elements of NFVI e.g. hypervisor. Faults in all elements in NFVI that affects the proper functioning of the VNFs in question ​shall be handled in a step-by-step fashion.
 In addition, requirements on VIM and its northbound interface for NFVI maintenance operation would also be developed, as its similarities with fault detection/​notification feature. ​ In addition, requirements on VIM and its northbound interface for NFVI maintenance operation would also be developed, as its similarities with fault detection/​notification feature. ​
  
-The ultimate goal of this project is to realize an NFVI fault management and maintenance framework for telecom VNFs. Relevant fault events,​their detection and recovery procedure, notification mechanism e.g. publish-subsribe ​model and other necessary features to realize the framework would be studied and requirements would be produced for relevant upstream projects. This project considers OpenStack as VIM.+The ultimate goal of this project is to realize an NFVI fault management and maintenance framework for telecom VNFs. Relevant fault events, their detection and recovery procedure, notification mechanism e.g. publish-subscribe ​model and other necessary features to realize the framework would be studied and requirements would be produced for relevant upstream projects. This project considers OpenStack as VIM.
  
 ==== Scope: ==== ==== Scope: ====
  
   * ''​Describe the problem being solved by project''​   * ''​Describe the problem being solved by project''​
- +    ​* lack of fault detection, notification and recovery mechanism in OpenStack 
-    ​*lack of fault detection, notification and recovery mechanism in OpenStack +    * OpenStacks inability in receiving and executing maintenance instructions
-    *OpenStacks inability in receiving and executing maintenance instructions+
       * Requirements shall be produced to solve the problems above       * Requirements shall be produced to solve the problems above
  
Line 33: Line 30:
       - VIM collects/​detects relevant fault information about NFVI elements       - VIM collects/​detects relevant fault information about NFVI elements
       - VIM informs VNFM/NFVO who owns affected virtual resources e.g. VM       - VIM informs VNFM/NFVO who owns affected virtual resources e.g. VM
-      - VIM receives recovery instruction on affected ​virual ​resources+      ​- VIM tries to recover automatically (for selected types of faults) 
 +      ​- VIM receives recovery instruction on affected ​virtual ​resources
       - VIM receives maintenance instruction NFVI elements       - VIM receives maintenance instruction NFVI elements
  
Line 39: Line 37:
     * In scope     * In scope
       * OpenStack as VIM       * OpenStack as VIM
-      * NFVI fault items that affect the proper functioning of Evolved Packet Core (EPC) VNFs +      * NFVI fault items that affect the proper functioning of VNFs e.g. Evolved Packet Core (EPC) 
-      * Nothbound ​interfaces of VIM +      * Northbound ​interfaces of VIM
     * Out of scope     * Out of scope
       * VNFM/NFVO side implementation       * VNFM/NFVO side implementation
Line 48: Line 45:
   * ''​Describe how the project is extensible in future''​   * ''​Describe how the project is extensible in future''​
     * Newer fault events would be incorporated as they become relevant  ​     * Newer fault events would be incorporated as they become relevant  ​
-    * Extemsible ​to fault management/​maintenance items relevant to ODL, KVM+    * Extensible ​to fault management/​maintenance items relevant to ODL, KVM
  
  
 ==== Testability:​ ''​(optional,​ Project Categories: Integration & Testing)''​ ==== ==== Testability:​ ''​(optional,​ Project Categories: Integration & Testing)''​ ====
 +N/A
  
-  * N/A (Integration with OPNFV is TBD based on development in upstream projects) +==== Documentation: ​''​(optional,​ Project Categories: Documentation)''​==== 
- +N/A
- +
-==== Documentation:​ ==== +
- +
-  * Requirements +
-  * Northbound interface/API specification +
-  * Functional blocks description+
  
 ==== Dependencies:​ ==== ==== Dependencies:​ ====
Line 66: Line 58:
   * ''​Identify similar projects is underway or being proposed in OPNFV or upstream project''​   * ''​Identify similar projects is underway or being proposed in OPNFV or upstream project''​
     * [[:​requirements_projects:​high_availability_for_vnfs|High availability for VNFs]]     * [[:​requirements_projects:​high_availability_for_vnfs|High availability for VNFs]]
 +
   * ''​Identify any open source upstream projects and release timeline.''​   * ''​Identify any open source upstream projects and release timeline.''​
-    * OpenStack ​L-release ​(Oct, 2015) +    * OpenStack (Oct, 2015)
-      * Based on this requirement study, blue prints would be prepared for OpenStack L-release.  +
-        * Based on progress, blue prints could already be submitted of Kilo.+
  
-  * ''​Identify any specific development be staged with respect to the upstream project and releases.''​ 
-    * TBD (possibility of a trunk version of OpenStack project). 
-  
   * ''​Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.''​   * ''​Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications.''​
     * ETSI NFV MANO GS     * ETSI NFV MANO GS
Line 82: Line 70:
  
   * Name of and affiliation of the maintainer:   * Name of and affiliation of the maintainer:
-    * Ashiq Khan (DOCOMO, khan@nttdocomo.com)  ​+   
   * Names and affiliations of the committers:   * Names and affiliations of the committers:
-    * Carlos Goncalves (NEC) +    ​* Ashiq Khan (DOCOMO, khan@nttdocomo.com)  
-    * Dirk Kutscher (NEC) +    ​* Carlos Goncalves (NEC, Carlos.Goncalves@neclab.eu
-    * Jarmo Virtanen (Nokia) +    * Dirk Kutscher (NEC, Dirk.Kutscher@neclab.eu
-    * Petri Kemppainen (Nokia) +    * Jarmo Virtanen (Nokia, jarmo.virtanen@nsn.com
-    * Ryota Mibu (NEC) +    * Petri Kemppainen (Nokia, petri.kemppainen@nsn.com
-    * Tapio Tallgren (Nokia) +    * Ryota Mibu (NEC, r-mibu@cq.jp.nec.com
-    * Tomi Juvonen (Nokia)+    * Tapio Tallgren (Nokia, tapio.tallgren@nsn.com
 +    * Tomi Juvonen (Nokia, tomi.juvonen@nsn.com)
     * Uli Kleber (Huawei, ulrich.kleber@huawei.com)     * Uli Kleber (Huawei, ulrich.kleber@huawei.com)
     * Zhangyu (Huawei, zhangyu11@huawei.com)     * Zhangyu (Huawei, zhangyu11@huawei.com)
 +    * Tommy Lindgren (Ericsson, tommy.lindgren@ericsson.com)
 +    * Palani Chinnakannan (Cisco, pals@cisco.com)
 +    * Peter Lee (ClearPath, plee@clearpathnet.com)
 +    * Serge Manning (Sprint, Serge.Manning@sprint.com)
 +
   * Any other contributors: ​   * Any other contributors: ​
-    * Palani Chinnakannan (Cisco) +
-    * Peter Lee (ClearPath) +
-    * Serge Manning (Sprint)+
  
  
 ==== 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.''​
-    * Documents (see '​Documentation'​ section)+    * Northbound interface/​API description ​
     * Implementation architecture and plan for OpenStack     * Implementation architecture and plan for OpenStack
  
Line 110: Line 102:
  
   * ''​When is the first release planned?''​   * ''​When is the first release planned?''​
-    * Items mentioned in '​Planned deliverable'​ section by March, 2015+    * March, 2015
   * ''​Will this align with the current release cadence''​   * ''​Will this align with the current release cadence''​
     * Yes.     * Yes.
- 
-[[:​requirements_projects:​doctor_fault_mangement_and_maintenance|Detailed project proposal]]. 
  
  
  
doctor/project_proposal.1417174287.txt.gz · Last modified: 2014/11/28 11:31 by Ashiq Khan