release_c_planning:priority_list
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
release_c_planning:priority_list [2016/03/04 13:12] Simona Coppola |
release_c_planning:priority_list [2016/03/15 19:47] (current) Al Morton [Table] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======= OVS Release C Priority Feature List Candidates ======= | ======= OVS Release C Priority Feature List Candidates ======= | ||
| + | This Page lists features which have been submitted by community and OVS team as requirements for OVSNFV. It is expected that the output here will fold into higher level of OVS feature list for REL C | ||
| + | **Purpose of the Priority List** | ||
| + | |||
| + | *Establish a definitive list of features/improvements | ||
| + | *Analyse each feature and prioritize based on the categories defined below | ||
| + | |||
| + | *Impact - measure of significance/improvement would the feature help with achieving our overall objective (i.e. does this address industry use case or a customer pain point) | ||
| + | *Priority – How important is the feature to the community/user | ||
| + | *Effort- How long will it take? Time, resources, testing | ||
| ---- | ---- | ||
| - | Use the above information to create a key project facts section on your project page | + | |
| ^ Feature | Description | Priority | Effort | Impact | Jira ^ Comments ^ | ^ Feature | Description | Priority | Effort | Impact | Jira ^ Comments ^ | ||
| | **Fuel Feature List** | | | | | | | | | **Fuel Feature List** | | | | | | | | ||
| Line 21: | Line 30: | ||
| ---- | ---- | ||
| - | ^ Feature ^Description |Priority | Effort | Impact |Jira | Comments | | + | ^ Feature ^ Description | Priority | Effort | Impact | Jira | Comments | |
| - | | **Apex Feature List** | | | | | | | | + | | **Apex Feature List** | | | | | | | |
| - | | Need the ability to deploy with arbitrary patches | | | | | | | | + | | Functest successful run with clean results | Successful completion with reported results. | High | XL | High | | | |
| - | | Functest successful run with clean results | needs to run sucessfully as it validates the build (functional results) | | | | | | | + | | Yardstick Sucessful run with clean results | Successful completion with reported results. | High | XL | High | | | |
| - | | Yardstick Sucessful run with clean results |will provide performance results | | | | | | | + | | Apex Consume ovs4opnfv generated RPM | Define Deployment options for DPDK and non-DPDK. | | | | | Work with Apex for successful integration (TFH) | |
| - | | OS and ODL integration | | | | | | | | + | | NSH for vxLan | NSH/vLAN available for DPDK and non-DPDK. | High | XL | High | | Integrate and Test | |
| - | | Build more RPM versions |2 OVS 2 OVS with DPDK | | | | | | | + | |
| ---- | ---- | ||
| - | ^ Feature |Description ^ Priority | Effort | Impact | Jira | Comments | | + | ^ Feature | Description ^ Priority | Effort | Impact | Jira | Comments | |
| - | |** OVS Feature List** | | | | | | | | + | | ** OVS Feature List** | | | | | | | |
| - | | OVS Performance (Requested by Bin, Hu) | need to set expectations based on Use Cases | High | | | | follow up meeting to be scheduled( 1 hour session)| | + | | OVS Performance (Requested by Bin, Hu) | need to set expectations based on Use Cases | High | | | | follow up meeting to be scheduled( 1 hour session) | |
| - | | Priority Path through OVS | scheduling priority packets before others, OVS may not be the right place for it |High | | | | follow up meeting to be scheduled( 1 hour session) | | + | | Priority Path through OVS | scheduling priority packets before others. Dataplane Approaches include NIC queues, multi-queue at guest interface, and multiple guest interfaces. Control plane approach involves Auxiliary control connections to OF controller. | High | | | | follow up meeting at Hackfest (March) produces current list of alternatives. | |
| - | | NSH Requirement | Happening independent of us, we need to ensure its reflected in OPNFV | Low | | | | | | + | | NSH Requirement | Happening independent of us, we need to ensure its reflected in OPNFV | Low | | | | | |
| - | | MPLS over GRE | Specific requirement brought up by Ericsson but is being worked on by someone else, need to get link to it | Low | | | | | | + | | MPLS over GRE | Specific requirement brought up by Ericsson but is being worked on by someone else, need to get link to it | Low | | | | | |
| - | | 100G Requirement | | | | | | | | + | | 100G Requirement | | | | | | | |
| - | | Virtio Container requirement | | | | | | | | + | | Virtio Container requirement | | | | | | | |
| - | | Port Placement on Cores | | | | | | | | + | | Port Placement on Cores | | | | | | | |
| + | |||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | ^ Feature ^ Description | Priority | Effort | Impact | Jira | Comments | | ||
| + | | **JOID Feature List** | | | | | | | | ||
| + | | Functest successful run with results | Successful completion with reported results. | High | XL | High | | | | ||
| + | | Yardstick Successful run with results | Successful completion with reported results. | High | XL | High | | | | ||
| + | | JOID support with DPDK | Define Deployment options for DPDK | | | | | Work with JOID to integreted DPDK | | ||
| + | | Support for Power8 architecture | Define Deployment options for different architecture | | | | | Work with JOID to integreted power8 architecture. | | ||
| + | |||
| + | |||
| + | |||
release_c_planning/priority_list.1457097153.txt.gz · Last modified: 2016/03/04 13:12 by Simona Coppola
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
