This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
releases:brahmaputra:release_plan:policytest_milestone_d_report [2015/12/08 17:11] Brady Johnson |
releases:brahmaputra:release_plan:policytest_milestone_d_report [2015/12/08 18:04] (current) Brady Johnson |
||
---|---|---|---|
Line 1: | Line 1: | ||
Policy Test Milestone D Report | Policy Test Milestone D Report | ||
- | |||
- | |||
- | Remaining questions to answer in the table below: | ||
- | |||
- | 5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na | ||
- | |||
- | 6. List/describe your progress to date? | ||
- | |||
- | 7. Describe what you have remaining to do? (hint: You should only have completion of existing features and bug fixes to do. For test projects you will be developing remaining tests according to frozen specifications.) | ||
- | |||
- | 8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red | ||
- | |||
- | 9. List any serious or blocking issues that are impeding progress on your project: | ||
- | |||
Line 22: | Line 8: | ||
|4 | If you require post-install processing have you consulted with CI (Octopus), CD (Releng), and/or companion test projects (functest, yardstick, etc) regarding scripts you may need to provide such as for install, set-env, run-test, clean-env?| (N) No post processing needed. | | |4 | If you require post-install processing have you consulted with CI (Octopus), CD (Releng), and/or companion test projects (functest, yardstick, etc) regarding scripts you may need to provide such as for install, set-env, run-test, clean-env?| (N) No post processing needed. | | ||
|5 | If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? | (NA) | | |5 | If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? | (NA) | | ||
- | |6 | List/describe your progress to date? | We have been able to create a Service Chain and necessary Service Function (SF) VMs from Tacker and pass packets through the chain and SF VMs. This was using NetVirt as a classifier, and the App-coexistence mentioned in number 7 below was hard-coded.| | + | |6 | List/describe your progress to date? | Keith, fill this part in.| |
- | |7 | Describe what you have remaining to do? (hint: You should only have completion of existing features and bug fixes to do. For test projects you will be developing remaining tests according to frozen specifications.)| In upstream ODL SFC we still have to finish App Co-existence, whereby multiple apps can write to the same OpenFlow switch. We also have to finish the Abstract Data Types ODL SFC API, whereby Tacker can request a chain be created with an abstract list of Service Function Types; Documentation; Bug fixes| | + | |7 | Describe what you have remaining to do? (hint: You should only have completion of existing features and bug fixes to do. For test projects you will be developing remaining tests according to frozen specifications.)| Keith, fill this part in. | |
- | |8 | How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red|Yellow - Pending completion of the items in number 7 and results of testing. | | + | |8 | How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red| Keith, fill this part in. | |
- | |9 | List any serious or blocking issues that are impeding progress on your project| The upstream OVS NSH patch is taking too long to finish, but we have a work-around in place where SFF to SF packets first go to the local IP stack for VXLAN encapsulation, and are then sent back into the switch. Then the packets are handled as normal IP/UDP packets and sent to the Service Function.| | + | |9 | List any serious or blocking issues that are impeding progress on your project| Keith, fill this part in.| |