Multisite Milestone D Report

1. If you have code are features frozen? y/n/na

- yes. Multisite is a requirement project. All use cases frozen

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

- yes.

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

-no. As a requirement project, all BPs and Code will be done in OpenStack, so the test cases will be done in OpenStack, and some BPs are still in review process (not frozen) in OpenStack.

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? -na

5. If you have no code(e.g. documentation projects) - drafts of all deliverables exist and are ready for first review? y/n/na -no, project's deliverable are ready ( use cases, requirements, BPs ), but the documentation in OPNFV is not ready for review.

6. List/describe your progress to date?

As multisite project is an requirement project, the planned deliverable (https://wiki.opnfv.org/requirements_projects/multisite) has been finished

And the follow up contribution to upstream project like OpenStack is as following (https://wiki.opnfv.org/multisite/bug_bp) :

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.)

Documentation(Configuration and user guide)

8. How confident are you that you will be complete for Milestone E/code freeze on Jan 5? Green/Yellow/Red

Green. Does Milestone E freeze includes documentation?

9. List any serious or blocking issues that are impeding progress on your project:

No