This is an old revision of the document!
Table of Contents
Fuel@OPNFV Brahmaputra work-package planning
We plan for three work-packages until Brahmaputra code-freeze (Milestone E) Jan 5 - 2016
Work-package 1
Goal:
- Rebasement of Fuel@OPNFV core to Kilo and Fuel 7.0 (Experimental branch), including build, deploy, test, OPNFV CI-pipeline, Fuel@OPNFV Developers' CI-pipeline…
- First integration of Brahmaputra integration/collaboration projects (Fuel plug-ins). Goal is to get 4 projects onboard for WP1. Target system state for the integration is Juno and Fuel 6.1 (master branch)
- Auto deploy of integrated projects.
- Func-test/Yardstick real or noop verification of integrated projects.
Content: Work-package 1 Definition of done: Passing build-, automated deploy- and manual smoke-test.
Due dates: Latest date for integrated projects to sign-up for WP1: Thu November 5 -15 Latest date for a partially functional plugin commit: Tue Nov 10 -15 Latest date for a partially functional plugin demo (Yoytube clip or otherwise): Fri Nov 15
Work-package 2
Content: TBD
Definition of done: Passing build-, install- and partial devel-pipeline func-test.
Due date: Dec 11 - 2015
Work-package 3
Content: TBD
Definition of done: Passing build-, install- and partial devel-pipeline func-test.
Due date: Jan 5 - 2016
Consolidation
Content: Project release consolidation
Definition of done: Stabilization, documentation, bare-metal ci-pipeline clean-out, any PR-material, etc.
Due date: Feb 2 - 2016
