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:43] 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 | ||
| Line 7: | 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? | 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? | 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.| | ||
releases/brahmaputra/release_plan/sfc_milestone_d_report.1448894610.txt.gz ยท Last modified: 2015/11/30 14:43 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
