. Project name Fuel@OPNFV
2. Project status indicator for milestone C readiness: Green/Yellow/Red; GREEN = on track; YELLOW = working minor issues to get back on track; RED = offtrack with major issues Yellow towards orange (Yellow-red)
3.Name of person providing status Jonas Bjurel (email@example.com)
4.a link to your Jira tasks (filtered on R2) See the Fuel@OPNFV B-release Dash-board:https://jira.opnfv.org/secure/Dashboard.jspa?selectPageId=10608 Or the Fuel@OPNFV B-release Kanban-board https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=41
5.a link to your Jira dashboard See above
6.a statement of your progress at linking cross project dependencies in Jira Ongoing through Genesis – still in its starting phase with Genesis. Genesis voting on requirements started. A clear view on dependencies and capabilities is likely two weeks out in time. Current critical Genesis dependency inflow is ~10 Epics/day.
7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile) First development cycle is set and will start October 1. We will not use Scrum/Sprints.
8.a statement of your readiness (high level planning complete & in Jira) for future sprints Yet unknown.
9.a statement about any issues you have - Dependencies and capabilities largely unknown at this point. - SR1 Release cycle still running - Deployment compositions and its relation to CI/Functest/Pharos resources/WoW largely undefined. - Dependency to Fuel 8.0 and the timing match is worrying.
10.how & when you will finish getting your tasks & dependencies into Jira if not complete Complete October 16
11.how and when you will get ready to start development for Brahmaputra if not ready now It is a evolution from Arno SR0, Arno SR1 anf B-release SR0. We hope to release A-release SR1 beginning next week, an B-release devel will start the hour after.
12.a statement summarizing your project risk analysis & planning status - See point 9: Issues. - Testing strategy with the multitude of deployment options - CI-pipeline resource contention