This page summarizes the projects that are within the scope of Beijing Release.

At M1 Release Planning milestone, Jan 18, 2018, the TSC will review all project planning materials and provide its disposition. It is expected that all projects intending to participate into Beijing submit their Project Planning Materials no later than Jan 8, 2018.

That will provide time for everyone to:

1. understand each project scope
2. review dependencies
3. review all M1 materials
4. ask openly question
5. smooth the TSC approval process

Calendar for Beijing Release.

For those who intend to propose a new project, use the ONAP Project Proposal Template and post it in the Proposed Project list.

New project proposal for Beijing are available here. These new projects will be reviewed by TSC during Santa Clara F2F the week of Dec 11-13 amd added to the list below as they are approved byTSC.

M1 Status

Conditions on projects:

1. AAF: Pass with condition TSC need to agree on expending to CSM sub project scope.
2. AAI: Pass with condition TSC need to agree on expending to Image Manager sub project scope. Gildas Lanilis Update Feb 8. Team's decision to defer Image Manager to Casablanca.
3. DCAE: Pass with condition on exception Cloudify manager.
4. LOG: Pass with condition to review security guidelines and badges.
5. OOM: Pass with Condition to Clarify Maturity scope.
6. SO: Pass with Condition to reach 2 for Resiliency and Scalability at cpts Level (strectch ). Should be OK for 2 at Platform level.

Action Items:

1. Benchmark-Integration (Jason-Helen) team to provide performance measurement by M2.
2. Action Item: Auto-scaling: need for Blandford Scott and Zhao Peng to bring clarification on requirements.

M1 Summary of findings

Link to M1 IRC notes.

Beijing Milestones Status