User Tools

Site Tools


project_proposals:daisy_nfv

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
Last revision Both sides next revision
project_proposals:daisy_nfv [2016/03/23 02:37]
Zhijiang Hu [Key Project Facts]
project_proposals:daisy_nfv [2016/03/23 09:38]
Zhijiang Hu [Testability:]
Line 7: Line 7:
   * In Daisy4nfv project, we will support the installation of OPNFV release. It will support deployment of OPNFV full stack, with different flavors of configuration,​ on both bare-metal servers and virtual machines. We will also working closely with genesis and escalator project together to provide a complete improvement solutions for both installing and upgrading for opnfv.   * In Daisy4nfv project, we will support the installation of OPNFV release. It will support deployment of OPNFV full stack, with different flavors of configuration,​ on both bare-metal servers and virtual machines. We will also working closely with genesis and escalator project together to provide a complete improvement solutions for both installing and upgrading for opnfv.
   * The unique values that Daisy4nfv will bring to the OPNFV community includes the following: ​   * The unique values that Daisy4nfv will bring to the OPNFV community includes the following: ​
-  ​* Abstract and provides necessary information for upgrader(escalator) to do upgrading efficiently and accordingly. Thus, set as a example of how the escalator, genesis and installer can work together to bring more value to the end user. +      ​* Abstract and provides necessary information for upgrader(escalator) to do upgrading efficiently and accordingly. Thus, set as a example of how the escalator, genesis and installer can work together to bring more value to the end user. 
-  * Building blocks ​+  * Building blocks
 {{ :​project_proposals:​daisy_nfv.jpg |}} {{ :​project_proposals:​daisy_nfv.jpg |}}
  
-  ​Daisy consists ​of four main building blocks: ​Daisy-DashboardDaisy-Core, Daisy-Cupric ​and Daisy-Registry. Daisy-Dashboard is the web interface. Daisy-Core is the core logic which equips RESTful API for both northbound Interface(Daisycloud-Dashboard) and southbound Interface(Daisycloud-cupric)Daisy-Cupric takes the responsbility ​to do power control ​as well as discovery ​of target nodes. Daisy-Registry is the database.+      ​“Information Provider” is a plug-in ​of  Daisy Installer ​, and it will be used as a bridge between installer and upgraderData changed in Daisy which related to upgrading will be passed based on a publication to itLater, upgrader can query such information from Information Provider.  
 + 
 +      * By generalizing “What to provide” and “How ​to provide” to a more common layer, such as genesis, a loose coupling design ​of installer and upgrader can be achieved. 
  
-  * “Configuration for Daisy@nfv” is the specific configuration or patch that added by Daisy@nfv project to let Daisy to support deploying opnfv stack to target environment. ​ 
-  * “Registry Plugin for Daisy@nfv” is also unique for opnfv. It is a plugin of the “Daisy Registry” module, and it will be used as a bridge between installer and Escalator. When data is changed in Daisy Registry which related to upgrading, it will be passed based on a notification to Daisy@nfv. Later, Escalator can query such information from Daisy@nfv module directly or indirectly. Indirectly means Daisy@nfv should populate data to a more general layer such as Genesis, then Escalator only have to talk to Genesis to get what it needs. Thus a loose coupling design of installation and upgrading can be achieved. 
  
  
Line 35: Line 36:
  
   * Local lab rsources are used for integration and testing for upstream Daisy project.   * Local lab rsources are used for integration and testing for upstream Daisy project.
-  * Will colaborate with related opnfv project (releng/​functest) to provide testability for all Daisy@nfv ​based artifacts.+  * Will colaborate with related opnfv project (releng/​functest) to provide testability for all Daisy4nfv ​based artifacts.
  
 ==== Documentation:​ ==== ==== Documentation:​ ====
Line 50: Line 51:
  
     * Zhijiang Hu(ZTE) : hu.zhijiang@zte.com.cn     * Zhijiang Hu(ZTE) : hu.zhijiang@zte.com.cn
-    * Jing Sun (ZTE) : sun.jing22@zte.com.cn +
-    * Yao Lu (ZTE) : lu.yao135@zte.com.cn+
  
  
 **Names and affiliations of any other contributors** **Names and affiliations of any other contributors**
  
 +    * Jing Sun (ZTE) : sun.jing22@zte.com.cn
 +    * Yao Lu (ZTE) : lu.yao135@zte.com.cn
 ==== Planned deliverables:​ ==== ==== Planned deliverables:​ ====
  
-  * Daisy@nfv ​Installer based on Daisy open source for OPNFV stacks +  * Daisy4nfv ​Installer based on Daisy open source for OPNFV stacks 
-  * Daisy@nfv ​- Documentation (ODL / ONOSFW versions)+  * Daisy4nfv ​- Documentation (ODL / ONOSFW versions)
  
 ==== Proposed Release Schedule: ==== ==== Proposed Release Schedule: ====
Line 68: Line 70:
 ===== Key Project Facts ===== ===== Key Project Facts =====
  
-** Project Name: ** Daisy@nfv ​(daisy) \\+** Project Name: ** Daisy4nfv ​(daisy) \\
 ** Repo name: ** daisy \\ ** Repo name: ** daisy \\
 ** Lifecycle State: ** Proposal \\ ** Lifecycle State: ** Proposal \\
 ** Primary Contact: ** hu.zhijiang@zte.com.cn \\ ** Primary Contact: ** hu.zhijiang@zte.com.cn \\
 ** Project Lead: ** Zhijiang (ZTE) : hu.zhijiang@zte.com.cn \\ ** Project Lead: ** Zhijiang (ZTE) : hu.zhijiang@zte.com.cn \\
-** Jira Project Name: ** Daisy@nfv ​\\+** Jira Project Name: ** Daisy4nfv ​\\
 ** Jira Project Prefix: ** [Daisy] \\ ** Jira Project Prefix: ** [Daisy] \\
 ** mailing list tag ** [Daisy] \\ ** mailing list tag ** [Daisy] \\
Line 79: Line 81:
  
     * Zhijiang Hu(ZTE) : hu.zhijiang@zte.com.cn \\     * Zhijiang Hu(ZTE) : hu.zhijiang@zte.com.cn \\
-    * Jing Sun (ZTE) : sun.jing22@zte.com.cn \\ +
-    * Yao Lu (ZTE) : lu.yao135@zte.com.cn \\+
  
  
project_proposals/daisy_nfv.txt · Last modified: 2016/03/23 09:58 by Zhijiang Hu