SDNVPN Milestone E Report
1. Has your feature been executed on an OPNFV deployment in a Pharos lab? n
We are currently defining Fuel deployment scenarios and will hopefully have Jenkins jobs deploying and testing them during next week.
2. Have your test cases been run on the feature once deployed in a Pharos lab? n
See above
3. Are your test cases all ready? 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.
4. Are your test cases all passing? n
5. Do you feel you are prepared for code freeze on January 5th? y
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.
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.
