Technical Community Coordinator Update

Congratulations to Magnus Buhrgard re-elected as our ONAP Network Management Technical Community Coordinator!

Other TCC - TSC Vote required #AGREED TSC approves the changes to the TCC positions; Removal of Infrastructure Coordinator, align 5G and Edge to the Requirements Subcommittee, Cloud Native to the CNF Taskforce, and AI/ML to the Control-loop subcommittee.

• Infrastructure - no more require -  TSC approved PTL Toolchain Improvements - Short Term Path
• 5G, Edge Computing – ONAP Requirements Subcommittee to take over this role 
• Cloud Native/CNF – ONAP Cloud Native CNF Task Force to take this role
• AI/ML - ONAP Control Loop Subcommittee to take over

30

Release Status

• Frankfurt Maintenance
  • List of Jira Issues
  • Integration Dashboard
  • Go?
    • Containers?
    • Release notes?
• Guilin
  • Functional requirements REQ335-338 are GREEN
  • Guilin Impact View per Component (v234)
  •  Non functional - TSC Vote options

    • Option #1 Approve all the non functional requirements for M1 so the project teams can try to improve during the Guilin timeframe.

    • Option #2 Reduce Scope - Only consider TSC MUST HAVE and non functional requirements marked as GREEN Today

    • Option #3 Reduce scope - Only consider RANK #0-2 and Green RANK #3 (i.e. REQ-376, 396 and 340)

    • Option #4 Anything else to consider

  • Go on M1?
  • M2 tasks published
    
    • Scheduled Aug 6
  • TSC approved that permissive and weak copyleft licenses can be part of ONAP containers
  • TSC feedback on strong copyleft in the containers. (primarily for targeted at  vendors/integrator members versus carriers)
    • Required for container delivery for Guilin M4 on Sept 10
    • Need guidance from your legal teams regarding the following licenses being included as part of the containers that you are distributing 
      • GFDL, GFDL-1.2, GFDL-1.3 - copyleft licenses used for documentation
      • GPL-1 - copyleft
      • GPL-2 - copyleft license (probably the most popular).
      • GPL-3 - copyleft license which extends the restrictions put by GPL v2

5

RelEng/Infrastructure

• Tickets- Open showstoppers:
• Tickets- Waiting on Community:
• Migration Status / Upcoming Changes

 Project Lifecycle Review

• Working Group Recommendations
• Project Maturity Reviews

Subcommittee Update

Requirement

5

PTL Update

Documentation

• The team is fully staffed.
• Established a plan, using the existing documentation, which is split into 4 milestones. This has been shared with Documentation team. 
• In the process of creating 2 setups (one on AWS cloud, and another on baremetal servers, with the Frankfurt/master branch of OOM/ONAP) to try out the features as the team reviews the documents. 
• The Operations Guide (installation and configuration) and SDC (Design) doc review/testing is in progress, and the team has started filing Jira tickets for the issues found or the improvements. 
• The testing will follow a Persona based approach as proposed in SOW

 TAC Update

10

Subcommittee Update

Seccom

How adopting Harbor will help ONAP community to secure its dockers

Presentation to introduce how Harbor open source olusion form CNCF can help ONAP community to better validate the Dockers podcudd by ONAP community

Presented during Seccom subcommittee and agreement to present to TSC for decision

 PTL Update

5

TSC Activities and Deadlines

2020 Elections:

• Subcommittees: 
  https://lists.onap.org/g/onap-tsc/message/6547

 2020 TSC priorities - Review ONAP Focus

• Implement the "Requirements" Subcommittee - Completed
• Role of ONAP to support CNFs:  ONAP CNF Task Force
• CNTT/ONAP Partnership:  OVP PH2 (Cloud Native)
• Review Release Cadence (Ongoing) 
• Implement Project Review/Lifecycle (under TSC Review)
• Promote "What we have done" (ongoing)
• Deliver Frankfurt (Sign-Off on 6/11) and Guilin 

5

Upcoming Events

• New Dates Open Networking & Edge Summit North America 2020  September 28 & 29, 2020 (Virtual Event is now confirmed) - https://lists.onap.org/g/onap-tsc/message/6513

  • ONAP TSC Abstract “ONAP and Cloud Native” was approved.