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 Gmail 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.Update by Gildas Lanilis Gmail: Information provided during Virtual F2F: Integration Testing and S3P Measurement (slide #17). Action Items: Closed
2. Action Item: Auto-scaling: need for Blandford Scott and Zhao Peng to bring clarification on requirements. Update by Gildas Lanilis Gmail : Peng Zhao made clarification with VFC PTL, Scott Blandford broght clarification on the scope of Auto-scaling for Beijing. Action Items: Closed

M1 Summary of findings

Link to M1 IRC notes.

M2 Status

TSC did not reach quorum today, therefore no vote took place. M2 Recommendations are provided and send out by email for vote.

Recommendations to TSC:

1. Disposition M2 as Pass for aaf,aai, appc, ccsdk, clamp, cli, dcagen2, dmaap, doc, externalapi, holmes, integration, logging, modeling, msb, music, oof, oom, policy, portal, sdnc, so, vfc, vid, vnfrqts, vnfsdk. Update by Gildas Lanilis Gmail: TSC approved the disposition by mailing list vote.

2. 3 projects (sdc, usecase UI, multicloud) could not make it today and are schedule for review at next TSC meeting. Update by Gildas Lanilis Gmail: TSC approved these 3 project during TSC meeting on Feb 22.
3. TSC needs to discuss on VVP. Current status: VVP did not presnt to M1 and M2 and there are some thoughts on breaking thins into a sub-committe and a project.

Action Items:

1. Auto-Scaling: carried over from M1. Peng Zhao and VFC team to clarify.See M1 note above. Action Items: Closed
2. SO external API: Eric Debeau to contact Seshu Kumar Mudiganti for questions and concerns. Action Items: Closed
   
   

Link to M2 IRC notes.

M3 Status

All projects except VVP and logging passed M3 milestone.

Action Items:

1. Logging: checklist was not available. Review will be hold during next week TSC meeting. Action Items: Closed (datails here, slide #3)
2. VVP: Steven wright to organize meeting to review and clarify S3P scope for VVP. (Invitees: Brian Freeman, Helen Chen, Gildas Lanilis Gmail) Action Items: Closed (datails here, slide #4)

Link to M3 IRC notes.

M4 Status

All projects passed except: Usecase-ui, ExternalAPI, AAF, DMAAP. TSC was running out of time to provide its disposition on VVP.

Update on April 26: Usecase-ui, ExternalAPI, AAF, DMAAP passed M4.

Action Items:

1. PTL: Look for details in colunm "M4 notes and Disposition" in PDF file, plus all the items highlighted in Red.
2. PTL: ensure the Functional Requirement and Platform Maturity table are up to date
3. PTL: update project risk

RC0 Status

All projects passed except: DCAE, Portal, ExternalAPI, AAF, OOF and LOGGING. Main focus is on OOM deployment. Details are provided in Excel Sheet Tab RC0 (filter on colunm M) or in PDF format.

Update on May 3: Portal, DCAE, Logging passed RC0

Note: Just after TSC meeting, I have been able to clear UseCaseUI-Server. There isn't anymore dependency on MySQL and build has no error.

RC2 Status

On May 17, TSC took decision to postpone RC2 and Sign-Off date by 2 weeks.

Beijing Release Planning has been updated accordingly.

New dates are:

• RC2: May 31, 2018
• Sign-Off: June 7, 2018

Materials presented on May 17 are:

• ONAP RC2 Overall Status
• ONAP RC2 specific project findings

Beijing Vulnerability Reports

This list projects who have fill out a vulnerability report for Beijing Release.

• Page:
  Security Levels (New) (ONAP Wiki)

  • security
• Page:
  El Alto VNFSDK Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto VFC Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto UsecaseUI Security/Vulnerability Reports (ONAP Wiki)

  • security
  • template
• Page:
  El Alto MultiCloud Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto MSB Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto Modeling Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto Logging Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto Holmes Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto ExtAPI Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto DMaaP Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto CLI Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto CLAMP Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  El Alto oparent Security/Vulnerability Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Security/Vulnerability Threat Template - El Alto (ONAP Wiki)

  • security
  • template
• Page:
  Scenarios for using historical inventory and topology (ONAP Wiki)

  • s3p
  • security
• Page:
  Dublin Logging Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin SO Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin VNFSDK Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin Portal Platform Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin VF-C Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin UUI Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin DCAE Security/Vulnerability Report - Official Copy (ONAP Wiki)

  • security
  • template
• Page:
  Dublin VID Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin SDNC Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin SDC Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin Music Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin MultiVIM/Cloud Security/Vulnerability Report - Official Copy (ONAP Wiki)

  • security
  • template
• Page:
  Dublin Policy Security/Vulnerability Report (ONAP Wiki)

  • security
  • template
• Page:
  Dublin Integration Security/Vulnerability Report (ONAP Wiki)

  • security
  • template

Beijing Milestones Status