Compass4NFV Milestone E report
1. Has your deploy tool been executed in more than one Pharos lab?
Yes
2. Are you able to deploy all component versions you have targeted for Brahmaputra?
No. Most are ready. OpenContrail support is on-going.
3. Are all configurations your tool deploys able to be validated with Functest and/or Yardstick?
Yes.
4. Is your deployment able to be repeated on the same infrastructure without failures?
Yes
5. Is your deployment able to be run without failures after a different deployment has been on the infrastructure?
No, unless we overwrite the existing deployment. Incremental deployment is not supported by our project.
6. Have all known issues been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release?
No. We have not reached to that point of categorizing known issues and documenting known issues or workarounds.
7. Are all known issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low)?
Partial. No to review and put tickets into correct severity.
8. Do all known critical Jira Tickets have a workaround in place?
No. Not at that point of development yet.
9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?
No. Same as above.
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
No. We still have documentation being updated. We will have release notes and user guides at time of release, and may have an independent revision/improvement on documentation within a month of release.
