IPv6 Milestone D Report
1. If you have code are features frozen? y/n/na
(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/n/na
(NA)
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/n/na
(Y, YARDSTICK-153)
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?
(Y, OCTO-135 and GENESIS-72)
5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na
(NA)
6. List/describe your progress to date?
(Steadily in progress)
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.)
(Completion of existing features and bug fixes, which also includes upstream bug fixes in Neutron, for example, (1) Support MTU advertisement using IPv6 RAs - https://review.openstack.org/#/c/244722/ and (2)Support for IPv6 RDNSS Option in Router Advts - https://review.openstack.org/#/c/236805/, and upstream bug fixes in ODL, for example, Java exception - http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-November/006718.html)
8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red
(Green)
9. List any serious or blocking issues that are impeding progress on your project:
(None)
