NFV for KVM Milestone D Report
1. If you have code are features frozen? Y
2. If you have api/s, files or other interfaces that other projects rely on to integrate with your project are they frozen? Y
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
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? We are talking to Yardstick about this.
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? Working on optimizations (no API changes), what we have by 1/1/16 will be what is frozen for the B release. Major effort on establishing the source tree and getting that fully functional. Also ongoing work on getting the project integrated into the CI system.
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.) Ongoing optimizations and Fuel integration.
8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? GREEN
9. List any serious or blocking issues that are impeding progress on your project: Biggest concern is Fuel integration since changing the underlying kernel (required for our project) is disruptive to any other project that needs a kernel loadable modeul (like OVS).
