Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
Apex 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?
I assume components here include SDN Controllers.  We have only deployed with ODL and manual verification with Onos has been completed.  We are still missing deploying other components like OpenContrail.

3. Are all configurations your tool deploys able to be validated with Functest and/or Yardstick?
All the ones currently integrated, 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?
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?
All known issues are documented in JIRA.  Any unresolved issues will be listed in the release notes.

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, some are critical tasks that need to be done and not critical bugs.

9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?
Yes, requirements from Genesis we have to meet, others we can defer if we don't make it for later release

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

User Tools

Site Tools

Page Tools
