releases:brahmaputra:release_plan:ipv6_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
releases:brahmaputra:release_plan:ipv6_milestone_e_report [2015/12/17 20:04] Debra Scott created |
releases:brahmaputra:release_plan:ipv6_milestone_e_report [2016/01/05 00:03] (current) Bin Hu |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| 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? y/n | ||
| + | |||
| + | Yes, because it is deployed in Huawei’s lab. It is manual deployment, not an “OPNFV deployment” per se. I would expect that: | ||
| + | * Huawei will use Compass to deploy it based on their experience of manual deployment, including the scenario of disabling odl-l3 and enabling neutron-l3-agent | ||
| + | * Other installers will at least let us know the configuration change that is needed for our [[http://wiki.opnfv.org/brahmaputra_testing_page?&#test_scenarios_for_brahmaputra.|Deployment Scenarios]] **A3** and **A4**. | ||
| 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? y/n | ||
| + | |||
| + | Yes. It was done manually. Huawei is developing Yardstick code to automate the tests. | ||
| 3. Are your test cases all ready? y/n | 3. Are your test cases all ready? y/n | ||
| + | |||
| + | Yes | ||
| 4. Are your test cases all passing? y/n | 4. Are your test cases all passing? y/n | ||
| + | |||
| + | Yes | ||
| 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? y/n | ||
| + | |||
| + | Yes except Installer related and Yardstick test related | ||
| 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? y/n | ||
| + | |||
| + | N/A. We don’t have open issues. All Jira issues are either closed or in progress (community lab deployment, testing and documentation) which are expected to resolve and close before B release. | ||
| 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?y/n | ||
| + | |||
| + | N/A. We don’t have open issues. All Jira issues are either closed or in progress (community lab deployment, testing and documentation) which are expected to resolve and close before B release. | ||
| 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?y/n | ||
| + | |||
| + | Yes | ||
| 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)?y/n | ||
| + | |||
| + | 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. All draft complete: | ||
| + | * [[http://artifacts.opnfv.org/ipv6/docs/setupservicevm/index.html|Draft of Install Guide (HTML)]] | ||
| + | * [[http://artifacts.opnfv.org/ipv6/docs/setupservicevm/setupservicevm.pdf|Draft of Install Guide (PDF)]] | ||
| + | * [[http://artifacts.opnfv.org/ipv6/docs/gapanalysis/index.html|Draft of Gap Analysis/User Guide (HTML)]] | ||
| + | * [[http://artifacts.opnfv.org/ipv6/docs/gapanalysis/gapanalysis.pdf|Draft of Gap Analysis/User Guide (PDF)]] | ||
| + | |||
releases/brahmaputra/release_plan/ipv6_milestone_e_report.1450382662.txt.gz · Last modified: 2015/12/17 20:04 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
