This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
project_proposals:daisy_nfv [2016/03/22 08:53] Zhijiang Hu [Testability:] |
project_proposals:daisy_nfv [2016/03/23 09:58] Zhijiang Hu [Documentation:] |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Project Name: ==== | ==== Project Name: ==== | ||
- | * Proposed name for the project: ''Daisy@nfv'' | + | * Proposed name for the project: ''Daisy4nfv'' |
* Proposed name for the repository: ''daisy'' | * Proposed name for the repository: ''daisy'' | ||
==== Project description: ==== | ==== Project description: ==== | ||
- | * Daisy@nfv is an installer project based on open source project daisy([[https://github.com/OpenDaisy]]), which provides automated deployment and management of OpenStack and other distributed systems. | + | * Daisy4nfv is an installer project based on open source project daisy([[https://github.com/OpenDaisy]]), which provides automated deployment and management of OpenStack and other distributed systems. |
- | * In Daisy@nfv 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 Daisy@nfv 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 consist of four main building blocks: Daisy-Dashboard, Daisy-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 upgrader. Data changed in Daisy which related to upgrading will be passed based on a publication to it. Later, 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. | ||
==== Scope: ==== | ==== Scope: ==== | ||
- | * Absorbing all of OPNFV's release cadence features through the genesis project. | + | * Absorbing OPNFV's release cadence features through the genesis project. |
* Working closely with genesis and escalator project together to provide a complete improvement solutions for both installation and upgrading. | * Working closely with genesis and escalator project together to provide a complete improvement solutions for both installation and upgrading. | ||
* Providing needed capabilities for the OPNFV CI pipeline, including: | * Providing needed capabilities for the OPNFV CI pipeline, including: | ||
* Build | * Build | ||
* Deployment | * Deployment | ||
- | * Needed hooks for low-level verification (tempest) | + | * Integration with test projects |
+ | * Needed hooks for low-level verification (Functest) | ||
* Needed hooks for high-level verification (Scenario testing) – Yardstick | * Needed hooks for high-level verification (Scenario testing) – Yardstick | ||
- | * Supporting Widely collaboration with integration of all open source SDN controllers, e.g ONOS, ODL etc | + | * Integration with SDN controllers |
- | * Making all code changes as upstream as possible into respective projects | + | * Supporting Widely collaboration with integration of all open source SDN controllers, e.g ONOS, ODL etc |
Line 33: | 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: ==== | ||
- | * TBD | + | * Presentations: |
+ | [[https://wiki.opnfv.org/_media/project_proposals/opnfv_technical_discussion_-_daisy_nfv_proposal.pptx]] | ||
+ | * API DOC TBD | ||
==== Dependencies: ==== | ==== Dependencies: ==== | ||
Line 48: | Line 53: | ||
* 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 66: | Line 72: | ||
===== 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: ** \\ | + | ** 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 77: | Line 83: | ||
* 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 \\ | + | |