User Tools

Site Tools


releases:brahmaputra:release_plan:joid_milestone_e_report

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

YES - we can deploy OpenStack and various SDN, i.e. ODL, OpenContrail and (to be verified) ONOS

3. Are all configurations your tool deploys able to be validated with Functest and/or Yardstick?

Partial - Functest is utilized for verification on Intel POD5 and Orange POD2 - with (so far) ODL only

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?

Yes

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 - it is on our todo list

7. Are all known issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low)?

Yes

8. Do all known critical Jira Tickets have a workaround in place?

Yes

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 - not yet

10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?

No -

releases/brahmaputra/release_plan/joid_milestone_e_report.txt · Last modified: 2016/01/06 17:49 by Artur Tyloch