project_proposals:nfvreadyness
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project_proposals:nfvreadyness [2016/03/13 03:00] Prakash Ramchandran [Dependencies:] |
project_proposals:nfvreadyness [2016/03/15 16:59] (current) Georg Kunz |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| + | ====== Note ====== | ||
| + | |||
| + | **Outdated Wiki** | ||
| + | |||
| + | This project proposal has been renamed to NetReady. Please find the updated wiki here: [[https://wiki.opnfv.org/project_proposals/netready]] | ||
| + | |||
| + | **Outdated Wiki** | ||
| + | |||
| + | |||
| ==== Project Name: ==== | ==== Project Name: ==== | ||
| Line 18: | Line 28: | ||
| - | **Example NFV use cases** | + | === Example NFV use cases === |
| - | It is a fundamental goal of the proposed project to jointly define relevant NFV use cases in the first project phase. The following list comprises **examples** for an initial scope. This list is neither complete nor exclusive and will be reviewed and extended in the first phase of the project: | + | It is a goal of the proposed project to identify relevant NFV use cases and their requirements in the first phase of the project. The following list shows **examples** of potentially relevant use cases. This list is neither complete nor exclusive and will be reviewed and extended in the first phase of the project: |
| * L3 VPN | * L3 VPN | ||
| Line 27: | Line 37: | ||
| - | **Observations** | + | === Observations === |
| Initial observations reveal the following list of challenges when attempting to implement NFV-related use cases in the current Openstack networking architecture. A full list of challenges will be the result of a detailed gap analysis based on the requirements of the identified use cases and the current Openstack networking architecture. | Initial observations reveal the following list of challenges when attempting to implement NFV-related use cases in the current Openstack networking architecture. A full list of challenges will be the result of a detailed gap analysis based on the requirements of the identified use cases and the current Openstack networking architecture. | ||
| Line 50: | Line 60: | ||
| - | ** Phasing ** | + | === Phasing === |
| The planned stages of the project are the following: | The planned stages of the project are the following: | ||
| Line 66: | Line 76: | ||
| - Start evaluating selected alternatives as identified in 3.1 based on the strategy defined in 3.2 | - Start evaluating selected alternatives as identified in 3.1 based on the strategy defined in 3.2 | ||
| - Document the results of the evaluation process and decide about the preferred solution | - Document the results of the evaluation process and decide about the preferred solution | ||
| + | - Recommend next steps in upstream development and drive upstream solution if needed | ||
| * Planned duration: 3 months. Input to Openstack P release summit | * Planned duration: 3 months. Input to Openstack P release summit | ||
| Line 75: | Line 86: | ||
| The project is intended to focus on the API layer of both the networking service in OpenStack and the SDN controllers in OPNFV's scope evaluating their best way of integration into OpenStack in order to efficiently fulfill NFV needs and the given requirements. Gluon is considered one prototyping activity out of a potential set of alternatives and hence not decided to be the preferred solution/implementation before finishing the evaluation phase. | The project is intended to focus on the API layer of both the networking service in OpenStack and the SDN controllers in OPNFV's scope evaluating their best way of integration into OpenStack in order to efficiently fulfill NFV needs and the given requirements. Gluon is considered one prototyping activity out of a potential set of alternatives and hence not decided to be the preferred solution/implementation before finishing the evaluation phase. | ||
| - | ** Fulfilling the principles of OPNFV ** | + | === Fulfilling the principles of OPNFV === |
| * the first stage of the project is intended to focus on discussing and capturing the use cases that we are aiming to find a solution for and clearly articulate and document the problem space | * the first stage of the project is intended to focus on discussing and capturing the use cases that we are aiming to find a solution for and clearly articulate and document the problem space | ||
| Line 81: | Line 92: | ||
| - | ** Requirements on potential solutions ** | + | === Requirements on potential solutions === |
| The project aims to identify and evaluate the possible solutions that can fulfill the requirements with following statements and criterias: | The project aims to identify and evaluate the possible solutions that can fulfill the requirements with following statements and criterias: | ||
| Line 96: | Line 107: | ||
| - | ** Repository and Source Code Handling ** | + | === Repository and Source Code Handling === |
| The outcome of the project, that is the requirements document and the complementary prototyping code, will be hosted in public repositories. | The outcome of the project, that is the requirements document and the complementary prototyping code, will be hosted in public repositories. | ||
| Line 142: | Line 153: | ||
| * Bin Hu (AT&T), bh526r@att.com | * Bin Hu (AT&T), bh526r@att.com | ||
| * Ashlee Young (Huawei), ashlee@wildernessvoice.com | * Ashlee Young (Huawei), ashlee@wildernessvoice.com | ||
| + | * Juraj Linkes (jlinkes@cisco.com) | ||
| + | * Viliam Luc -X (vluc@cisco.com) | ||
| + | |||
| * Names and affiliations of any other contributors | * Names and affiliations of any other contributors | ||
project_proposals/nfvreadyness.1457838023.txt.gz ยท Last modified: 2016/03/13 03:00 by Prakash Ramchandran
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
