releases:brahmaputra:release_plan:sdnvpn_milestone_e_report
Differences
This shows you the differences between two versions of the page.
|
releases:brahmaputra:release_plan:sdnvpn_milestone_e_report [2015/12/17 20:18] Debra Scott created |
releases:brahmaputra:release_plan:sdnvpn_milestone_e_report [2016/01/08 16:58] (current) Tim Irnich |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| SDNVPN Milestone E Report | SDNVPN 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? n |
| - | 2. Have your test cases been run on the feature once deployed in a Pharos lab? y/n | + | We are currently defining Fuel deployment scenarios and will hopefully have Jenkins jobs deploying and testing them during next week. |
| - | 3. Are your test cases all ready? y/n | + | 2. Have your test cases been run on the feature once deployed in a Pharos lab? n |
| - | 4. Are your test cases all passing? y/n | + | See above |
| - | 5. Do you feel you are prepared for code freeze on January 5th? y/n | + | 3. Are your test cases all ready? 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? y/n | + | The functional test cases are taken from upstream (ODL VPN Service and OpenStack BGPVPN Tempest tests) and their integration into Functest is almost finished. We have defined but not implemented Yardstick test cases. |
| - | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | + | 4. Are your test cases all passing? n |
| - | 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | + | 5. Do you feel you are prepared for code freeze on January 5th? y |
| - | 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 | + | Except for the Yardstick test cases we have done the needed development and if need be we could live without Yardstick test cases for Brahmaputra since the functionality has been manually verified in other settings and has proved to be quite stable. |
| - | 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? | + | 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? n |
| + | |||
| + | Documentation is a somewhat weak point of the project in general, we have just started to work on this. | ||
| + | |||
| + | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? n | ||
| + | |||
| + | 8. All known open critical Jira Tickets have been closed or have a workaround in place? n/a | ||
| + | |||
| + | See 7. | ||
| + | |||
| + | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? n/a | ||
| + | |||
| + | See 7. | ||
| + | |||
| + | 10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release? n | ||
| + | |||
| + | See 6. | ||
releases/brahmaputra/release_plan/sdnvpn_milestone_e_report.1450383484.txt.gz · Last modified: 2015/12/17 20:18 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
