Page tree
Skip to end of metadata
Go to start of metadata

Work-package 1

Status: Not started

Goal:

  • Re-basement of Fuel@OPNFV core to Mitaka
  • First base-line for feature integration/re-basement

Content:

  • Re-basement of Fuel@OPNFV core to Mitaka and Fuel 9.0, including build, deploy, test, OPNFV CI-pipeline, Fuel@OPNFV Developers' CI-pipeline..

Definition of done:

  • Passing build-, automated deploy-, func-test- and yardstick with "os-nosdn-nofeature" scenario.

Due dates:

Start of re-basement: Mon April 24 -1016

Re-basement done: Ready May 9 -2016

Work-package 2

Status: In progress

Goal:

  • Hardening
  • ODL plugin integration
  • Final baseline for feature integration

Content:

  • Hardening-of the Fuel re-basement
  • Refactoring of scenario handling
  • re-basement of ODL to Fuel9 and Beryllium SR3
  • Any additional features imposed by Genesis

Definition of done:

  • Passing build-, automated deploy-, func-test- and yardstick with "os-nosdn-nofeature", "os-odl_l2-nofeature" and "os-odl_l3-nofeature" scenarios.
  • Soft code freeze

Due dates:

  • Start: Thu April 7 - 2016
  • Soft code-freeze: Thu May 19 - 2016
  • Hard code-freeze: Thu June 5 - 2016
  • End: Thu June 5 - 2016

Work-package 3

Status: Not started

Goal:

  • Documentation
  • Feature integration support

Content:

  • Documentation according to OPNFVDocs project requirements

Definition of done:

Docs ready, reviewed and built

Due date: June 30

Consolidation

Dates updated!!

Project release consolidation and stabilization reviews:

TBD

Maintenance reviews will continue until end of life support for Fuel@OPNFV Brahmaputra support

Note: Release review is referred to as the process where the Fuel@OPNFV committers review the actual system stability and decides upon corrective actions. Corrective actions could be any of:

  • Gating commits to the stable branch
  • Assigning a task-force team to perform system stabilization activities/measures
  • Deciding to push features, not enough stable/not meeting enough test coverage to a comming release.
  • Review of documentation and guidelines.
  • Review and approval of deviations
  • Review and approval of maintenance/service release plan.

Feature owners/PTLs of integrated projects as well as the lead for the Genesis-, Releng-, Functest-, Yardstick- and Pharos project are expected to participate in the release reviews, but others than Fuel@OPNFV committers lack voting rights in case voting will become needed. As usual, TSC has the final say!

Definition of done: Released stable system including documentation, repeatably working ci-pipeline, repeatably passing fun-test, a 48 hours of stability test, release notes with documented deviations.

 

  • No labels