This shows you the differences between two versions of the page.
— |
movie_milestone_c_report [2015/09/28 21:37] (current) Debra Scott created |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | 1.Project name: | ||
+ | MOVIE | ||
+ | |||
+ | |||
+ | |||
+ | 2.Project status indicator for milestone C readiness: | ||
+ | |||
+ | Green | ||
+ | |||
+ | |||
+ | |||
+ | 3.Name of person providing status: | ||
+ | |||
+ | Tianran Zhou (Zhoutianran@huawei.com) | ||
+ | |||
+ | |||
+ | |||
+ | 4.a link to your Jira tasks (filtered on R2): | ||
+ | |||
+ | https://jira.opnfv.org/issues/?jql=project%20%3D%20MOVIE%20AND%20labels%20%3D%20R2 | ||
+ | |||
+ | |||
+ | |||
+ | 5.a link to your Jira dashboard: | ||
+ | |||
+ | https://jira.opnfv.org/browse/MOVIE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel | ||
+ | |||
+ | |||
+ | |||
+ | 6.a statement of your progress at linking cross project dependencies in Jira. | ||
+ | |||
+ | We have some relations with RS Conductor on API & Configuration filter and we are evaluating the same. | ||
+ | |||
+ | |||
+ | |||
+ | 7.a statement of your readiness (detailed planning complete & in Jira) for your first sprint or first development cycle (if not agile). | ||
+ | |||
+ | Yes we have started on the API gaps and likely to start development upstream after Liberty release. | ||
+ | |||
+ | |||
+ | |||
+ | 8.a statement of your readiness (high level planning complete & in Jira) for future sprints. | ||
+ | |||
+ | |||
+ | |||
+ | 9.a statement about any issues you have. | ||
+ | |||
+ | Yes currently our development is in ODL and we are evaluating ONOS release. | ||
+ | |||
+ | |||
+ | |||
+ | 10.how & when you will finish getting your tasks & dependencies into Jira if not complete? | ||
+ | |||
+ | We have had one pass looks good for now and if need add more details if we find anything missing. | ||
+ | |||
+ | |||
+ | |||
+ | 11.how and when you will get ready to start development for Brahmaputra if not ready now? | ||
+ | |||
+ | We have started in upstream in ODL for now, ONOS can use possibly same OSGi bundles but will verify that while coding and testing APIs. | ||
+ | |||
+ | |||
+ | |||
+ | 12.a statement summarizing your project risk analysis & planning status. | ||
+ | |||
+ | Risk is there depending OpenStack Liberty content but will address that post OpenStack Summit and may use post-install patch strategy if needed. |