vnfgraph Milestone E Report
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? no
3. Are your test cases all ready? yes
4. Are your test cases all passing? no
We are setting up tests to be done manually and expect them to pass.
5. Do you feel you are prepared for code freeze on January 5th? yes
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 Since we have ONOS driver deferred to Rel-C , for Rel-B OVS drivers for OpenStack, we may need no additional Jira tickets
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?
Yes. we have documents submitted as part of source code refer https://gerrit.opnfv.org/gerrit/#/c/5325/1/doc/source/.
