Fuel Milestone E report

1. Has your deploy tool been executed in more than one Pharos lab?

 >>>>
 Yes: It deploys towards both LF lab and Ericsson-1 POD2 as part of the official CI/CD engine.

2. Are you able to deploy all component versions you have targeted for Brahmaputra?

>>>>
 Yes/No: Each component/version officially defined for the B-release deploys in isolation. Combinations
 and permutations of components towards the CI/CD engine has not been fully integrated or verified.
 Work is ongoing, plan is to have it done by the week of Jan 4 - 2016.
 

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

 >>>>
 No: Work is ongoing, plan is to have the Fuel and Releng part of the CI/CD done by the week of Jan 4 - 2016,
 I cannot answer for the Functest plan.

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/No: In principle it should, but I cant tell if it works in practice since current OPNFV CI/CD
 framework doesn't apply POD roaming practices.
    

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're not at the point to accept issues to spill over to future releases.

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

 >>>>
 No: This is not an issue!

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

 >>>>
 No: We're not at the point to accept issues to spill over to next release/creating workarounds. Hard code
 freeze for Fuel follows original August time-plan and will happen Jan 15 (in two weeks). 

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: We're not at the point to accept issues to spill over to future releases.

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

  >>>>
  No: But we're actively contributing in creating community documentation-templates/structure for documentation.
  We see no issue in having documentation ready by release.