releases:brahmaputra:release_plan:sfc_milestone_d_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:sfc_milestone_d_report [2015/11/30 14:40] Brady Johnson |
releases:brahmaputra:release_plan:sfc_milestone_d_report [2015/11/30 17:26] (current) Brady Johnson |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Notice: This is still a work in progress | ||
| SFC Milestone D Report | SFC Milestone D Report | ||
| - | |||
| - | Things left to finish: | ||
| - | |||
| - | 4. send the email | ||
| - | |||
| - | 6. List/describe your progress to date? | ||
| - | |||
| |Item|Question|Answer| | |Item|Question|Answer| | ||
| Line 14: | Line 6: | ||
| |2 | If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? | (N) There are no OPNFV SFC APIs used by other projects. | | |2 | If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? | (N) There are no OPNFV SFC APIs used by other projects. | | ||
| |3 | Are your test specifications frozen and provided to test projects? No additional use cases can be added to the release after this milestone (ie. feature projects have added the test cases for their project to the test team suite) | (Y) We have been working closely with Yardstick and Functest.| | |3 | Are your test specifications frozen and provided to test projects? No additional use cases can be added to the release after this milestone (ie. feature projects have added the test cases for their project to the test team suite) | (Y) We have been working closely with Yardstick and Functest.| | ||
| - | |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) Not yet, still not sure what we will have in our post-install. I sent a heads-up email. TODO send this email. | | + | |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) Not yet, its still not sure if we will have to install Tacker in our post-install. I sent a heads-up email to the Functest, Yardstick, and Releng contacts | |
| |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? | Deploy Yardstick in 5 community labs, start executing test cases, implement test result API in framework, evolve Yardstick framework architecture and develop Yardstick framework to cater for companion projects, more details in Jira.| | + | |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.| |
| |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.)| 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| | ||
| |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|Yellow - Pending completion of the items in number 7 and results of testing. | | ||
| |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| 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.| | ||
| - | |||
releases/brahmaputra/release_plan/sfc_milestone_d_report.1448894411.txt.gz ยท Last modified: 2015/11/30 14:40 by Brady Johnson
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
