releases:brahmaputra:release_plan:vnfgraph_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:vnfgraph_milestone_e_report [2015/12/17 20:14] Debra Scott created |
releases:brahmaputra:release_plan:vnfgraph_milestone_e_report [2016/01/08 01:45] (current) Prakash Ramchandran |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | VNFGraph Milestone E Report | + | vnfgraph Milestone E Report |
| - | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? y/n | + | 1. Has your feature been executed on an OPNFV deployment in a Pharos lab? no |
| + | But we are testing in Huawei Lab which uses Pharos configuration for hardware. B | ||
| + | Besides we are using only devstack installer for now. | ||
| - | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | + | 2. Have your test cases been run on the feature once deployed in a Pharos lab? no |
| - | 3. Are your test cases all ready? y/n | + | 3. Are your test cases all ready? yes |
| - | 4. Are your test cases all passing? y/n | + | 4. Are your test cases all passing? no |
| - | 5. Do you feel you are prepared for code freeze on January 5th? y/n | + | We are setting up tests to be done manually and expect them to pass. |
| - | 6. Have all known open issues (Jira tickets against your project) been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release? y/n | + | 5. Do you feel you are prepared for code freeze on January 5th? yes |
| - | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | + | 6. Have all known open issues (Jira tickets against your project) been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release? no |
| - | 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | + | We Since we have ONOS driver deferred to Rel-C , for Rel-B OVS drivers for OpenStack, we may need no additional Jira tickets |
| - | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?y/n | + | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?yes |
| + | We have everything taken care in upstream and here is the links to bugs and fixes. | ||
| + | open issues: https://review.openstack.org/#/q/status:open+networking-sfc | ||
| + | |||
| + | 8. All known open critical Jira Tickets have been closed or have a workaround in place? | ||
| + | |||
| + | Not Applicable as fixes are in upstream and recorded and patches beyond Dec 23 2015 have addressed them. | ||
| + | |||
| + | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?yes | ||
| 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | ||
| + | |||
| + | Yes. we have documents submitted as part of source code refer | ||
| + | https://gerrit.opnfv.org/gerrit/#/c/5325/1/doc/source/. | ||
| + | |||
releases/brahmaputra/release_plan/vnfgraph_milestone_e_report.1450383263.txt.gz · Last modified: 2015/12/17 20:14 by Debra Scott
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
