Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

JIRA Tasks

30

Frankfurt Release Status

M1 Review

M1 Recommendations for the TSC

What's next?

  • Confirm the Frankfurt Roadmap
  • Move to M2 Milestone


5

RelEng/Infrastructure

  • Tickets- Open showstoppers:
  • Other issues
    • RELENG-2517 - ONAP JIRA has invalid resolution type resulting in confusing behavior
    • TSC vote required to attempt fix due to potential risk.
  • Tickets- Waiting on Community:
    • RELENG-2422 (was IT-17739) Expand python template to support timestamp based docker push
  • Migration Status / Upcoming Changes
  • SonarQube/Cloud WARNING metric Kenny Paul



5

Logging Update

Any update concerning PTL role?

5

PTL Update

OOM Helm Chart to be transferred @project level

10

Subcommittee Update

Security









Paweł Pawlak , Amy Zwarico

Java 11 Migration (

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-219
)

  • SECCOM actioned to make recommendation on specific Java/Alpine versions
  • SECCOM respond with version recommendation but PTLs want pre-built image recommendation
  • PROBLEM: pre-built images not available for Java 11
  • Question for TSC:  is it acceptable to change the requirement to Java 12 or java 13  in order to allow PTLs to consolidate around a specific pre-built image recommendation from SECCOM?
    • Note that requirement says Java 11 or 13, so the question really is, do we want to remove the option for Java 11? 
    • We could consider saying that if you are already at Java 11, you don't need to update, but if you are at Java 8, you need to move to Java 13 (NOT 11), using the recommended pre-built image.


Proposal about Security Assessment for the Frankfurt release


30

TCC Update

Cloud Native

Review proposed agenda for the meeting with CNCF @Kubecon
10

Infrastructure TCC Role

Technical Community Coordinators  

  • Repository Management FAQ
    •  Send email to infrastructure-coordinator@onap.org
    • The Infrastructure coordinator is responsible for reviewing the request and either opening the ticket with LF-IT if everything is OK  --OR-- taking the issue back up with the PTL  --OR--  escalating it to the TSC only if something in the request is not OK and the PTL insists on moving forward anyway.

                5

PTL Update

Integration: 2 repos approved - https://lists.onap.org/g/onap-tsc/message/5620

Committer's requests under review (OOF, UUI, CCSDK)



5

TSC Activities and Deadlines

  • TSC Election - Ballots distributed. Voting ends Nov 19, 22:00 UTC
  • Recording retention Kenny Paul
  • Milestone Exception process has been approved by TSC on 11/8. Let's discuss when we would like to apply it.
  • DEMOS - R5 El-Alto Demos

Under review with the TSC

  • TSC El-Alto Community Awards
  • TSC Vote- Chaker's proposition

  • TSC Vote-Usecase requirement proposal


5

Incoming Events

Timo PeralaChaker Al-Hakim


  • ONAP 2 day event before or after ONES North America (April 20&21) - Los Angeles (TBC)
    • ONAP DDF planned in June - under planning
    • ONAP 2 day event before or after ONS North Europe - Antwerp (TBC)
    • Survey coming from LFN for Dec OR Jan for steady-state full DDF meetings to all LFN communities & locations
    • TSC Meetings will be canceled on Nov 28th, Dec 25th, 2019 and Jan 1st, 2020
    • Linux Foundation office holiday closures
      • Nov. 28th & 29th
      • Dec. 23rd through Jan 3rd, 2020


5

Additional Housekeeping

Linux Foundation

Calendar Management: "Please change my meeting" 


Action Items

  •  Sylvain Desbureaux upload slides based upon on the topics to today's meinures //mm-dd-yyyy

...