releases:brahmaputra:release_plan:armband_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:armband_milestone_e_report [2015/12/17 19:58] Debra Scott |
releases:brahmaputra:release_plan:armband_milestone_e_report [2016/01/05 20:12] (current) Joe Kidder |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ARMband Milestone E Report | ARMband 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? yes |
| + | Running with Arno SR1 level components (Fuel 6.1, Juno, ODL Lithium) we have installed OPNFV on ARM servers in a Pharos lab. | ||
| + | We intend to up-level during the last month to Fuel 8 and Liberty. | ||
| - | 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 |
| + | We have not yet run Functest against this installation. | ||
| - | 3. Are your test cases all ready? y/n | + | 3. Are your test cases all ready? N/A |
| + | We have don't have any test cases unique to ARM. | ||
| + | We will be using the test cases in Functest and Yardstick. | ||
| - | 4. Are your test cases all passing? y/n | + | 4. Are your test cases all passing? no (see #2 above) |
| - | 5. Do you feel you are prepared for code freeze on January 5th? y/n | + | 5. Do you feel you are prepared for code freeze on January 5th? N/A |
| + | Most of the code changes outstanding are in the Fuel installer to support ARM. | ||
| + | There are a minimal number of changes anticipated for Functest. | ||
| + | There is one change needed upstream for ODL. | ||
| - | 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 | + | 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. |
| + | We are investigating and planning to close a number of x86 dependencies. | ||
| + | Any deviations or exceptions will be documented in the release notes or referred by release notes to an external public page. | ||
| - | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?y/n | + | 7. Are all known open issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users? Yes |
| - | 8. All known open critical Jira Tickets have been closed or have a workaround in place?y/n | + | 8. All known open critical Jira Tickets have been closed or have a workaround in place? No |
| + | We are working all of the critical issues. | ||
| - | 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 | + | 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 |
| + | All non-critical Jira tickets have been targeted at a future release. | ||
| 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? | ||
| + | No, we intend to check it in and deliver it prior to the release. | ||
releases/brahmaputra/release_plan/armband_milestone_e_report.1450382284.txt.gz · Last modified: 2015/12/17 19:58 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
