User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

sfc_milestone_c_report [2015/09/28 22:29] (current)
Debra Scott created
Line 1: Line 1:
 +Project name
 +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
 +3.Name of person providing status
 +Brady Johnson,
 +4.a link to your Jira tasks (filtered on R2)
 +5.a link to your Jira dashboard
 +6.a statement of your progress at linking cross project dependencies in Jira
 +We have reported Requirements in Genesis, and have linked Stories with Yardstick.
 +We are in constant communication with the Yardstick and Functest projects.  ​
 +7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile)
 +Epics have been created for the release, and each Epic has sub-Stories. Stories have been identified for the first sprint and have been assigned and added.
 +8.a statement of your readiness (high level planning complete & in Jira) for future sprints
 +All Sprints have been defined with durations set on slide 8 here:               
 +9.a statement about any issues you have
 +Nothing more than reported below in 12.
 + & when you will finish getting your tasks & dependencies into Jira if not complete
 +Everything has been introduced into JIRA already. In true Agile form, we will add more tasks as we progress in our Use Case Implementation.
 + and when you will get ready to start development for Brahmaputra if not ready now
 +12.a statement summarizing your project risk analysis & planning status
 +Risk level is medium to low. We have identified the following 2 main risks
 +·         SFC depends on an OVS NSH patch, which is actively being up-streamed to OVS.
 +The patch is backed by an IETF spec, and actively supported by Intel, Ericsson, and Cisco.
 +We’ve been told it can take 3-6 months.
 +·         SFC requires VXLAN for NSH. We have identified a problem with how OpenStack creates VXLAN networking for newly created VMs. We have identified 2 possible solutions, and are discussing how to proceed
 +Planning status is “on track”
sfc_milestone_c_report.txt · Last modified: 2015/09/28 22:29 by Debra Scott