Versions Compared

Key

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

BRIDGE: https://zoom.us/j/661303200

Table of Contents
maxLevel1

...

Attendance is taken purely upon #info in Zoom Chat 


Time
(mins)

Agenda Items

Presented By

Presos/Notes/Links/

JIRA Tasks

15

Release Status

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

5

EUAG Update

30



5

Logging Update

Any update concerning PTL role?

5

PTL Update

OOM Helm Chart to be transferred @project level

10

Subcommittee Update

(This week in red)
Arch, Ctrl-Loop, Lab, Modeling, Seccom, Usecase

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

Rescheduled to  

TCC Update

Cloud Native

Review proposed agenda for the meeting with CNCF @Kubecon



10

  • Rescheduled to  

Infrastructure TCC Role

Technical Community Coordinators and ONAP Liaisons  

  • Repository Management
    •  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

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

10

Available Slot

10

Available Slot

10

Available Slot

Calendar Management: "Please change my meeting" 


Action Items

  •  Sylvain Desbureaux upload slides based upon on the topics to today's meinures  
  •  Kenny Paul move infrastructure-coordinator  topic to next week  
  •  David McBride add M2/Mx to PTL and and TSC agendas for next week  

Zoom Chat Log 
Anchor
zoom
zoom

notes- initial rollcall truncated - the minutes page is correct. Kenny Paul

06:04:35 From Benjamin Cheung : # Ben Cheung Nokia Proxy
06:04:59 From Kenny Paul (LFN) : #topic M1 review
06:06:13 From Kenny Paul (LFN) : - logging project not participating in Frankfurt
06:06:29 From LinMeng(CMCC) : Hi David, Can you give me 1 minute to calarify the status for slicing use case?
06:06:40 From Kenny Paul (LFN) : - 325 out of 353 issues closed - good progress siunce last week
06:07:17 From Ning So : #info, Ning So, Reliance Jio
06:07:25 From LinMeng(CMCC) : For UUI, OOF, SDC, we’ve already get the commitment from the PTL and there is no Arc issue. That’s why Steve comment on only SO and External API
06:07:41 From Davide (Vodafone) : #info Davide Cherubini, Vodafone
06:08:03 From Kenny Paul (LFN) : @Ning, @Davide- thank you
06:10:33 From Kenny Paul (LFN) : -@Catherine reminds community that scope was agreed upon on sept 27
06:10:35 From Ciaran Johnston : #info CIaran Johnston, Ericsson, Proxy for Stephen Terrill
06:11:03 From Kenny Paul (LFN) : @Ciaran - thank you
06:13:15 From LinMeng(CMCC) : I think there is some misunderstanding. I agree with Catherines point on AAI, SDN-C and DCAE, But for UUI, OOF, SDC, we’ve already get the commitment
06:25:38 From Kenny Paul (LFN) : -The community is reminded that usecase resources must first address TSC "Must have" items
06:26:47 From LinMeng(CMCC) : we have resource to commit in U-UI and OOF for this release.
06:26:51 From Swaminathan : We will certainly look at where we can help, however, considerable work has already gone in for the Network Slicing use case, and we don't want to lose the momentum
06:27:50 From Swaminathan : And at the end, for Frankfurt, importantly, we should have something meaningful to show
06:28:12 From Swaminathan : in terms of some minimum functionality from a use case working perspective
06:28:22 From Milind Jalwadi (Tech Mahindra) : Another alternate way is that we can develop the features and the later upstream when it is possible. That way we still are going ahead and not loosing time.
06:28:59 From Kenny Paul (LFN) : -@Lingli notes that if resources are being provided for a specific item forcing them to work on something they didn't sign up for is contradictory to opensource spirit
06:38:33 From Kenny Paul (LFN) : -@Catherine reviewed email to TSC sent Oct. 30
06:38:38 From Kenny Paul (LFN) : https://lists.onap.org/g/onap-tsc/message/5545
06:39:15 From LinMeng(CMCC) : We have plenty resources to help U-UI and OOF’s improvements not even for this use case. We’d like to see more maturity on these modules after F release and we’re happy to contribute on these modules.
06:43:24 From Kenny Paul (LFN) : - Discussion regarding interpretation of expectations - right now UUI does not meet the agreed upon "must have" items - so it isn't qualified for the release.
06:45:39 From Lingli : UUI PTL is not on the call. need to get back later.
06:46:30 From Kenny Paul (LFN) : -Discussion- applying additional resources exclusively for usecases to a project that does not meet "must have" does not get the project approved.
06:47:24 From Kenny Paul (LFN) : time check - topic +15 mins
06:48:59 From Kenny Paul (LFN) : #AGREED all projects listed in green approved for M1: AAI, AAF, APPC, CLAMP, CCSDK, DCAE, DMaaP; ExtAPI, Integration, Modeling, MUSIC, MSB, MutliCloud, OOM, Policy, SNDC, SDC, SO, VF-C, VID, VNFReqs, VVP, VNFSDK
06:58:47 From Eric Debeau : #info if we use El Alto containers for Holmes, Logging and CLI, we must clarify it in the release note and explain the limitation if any (eg security)
07:01:27 From Kenny Paul (LFN) : time check- topic +30 mins
07:09:16 From Swaminathan : UUI, OOF and SDC were stated as impacted components for E2E Network Slicing use case
07:09:28 From Swaminathan : There was no architecture consideration for these
07:09:38 From Swaminathan : because they are more of functional enhancements
07:09:59 From Swaminathan : SO and EXT-API were explicitly mentioned because there is an architectural implication
07:10:50 From LinMeng(CMCC) : Yes, These points also have been clarified by Steve via the email.
07:16:39 From Kenny Paul (LFN) : time check - topic +45
07:16:48 From Sylvain Desbureaux - Orange : If we have security issues on these containers, what do we do?
07:19:32 From Catherine Lefèvre : https://lf-onap.atlassian.net/wiki/display/DW/Frankfurt+Milestone+Status
07:19:52 From Sylvain Desbureaux - Orange : No problem!
07:19:54 From Sylvain Desbureaux - Orange : Cath
07:20:49 From Kenny Paul (LFN) : #vote does the TSC approve the NO GO as documented in (v. 63) of https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16398321 ? +1, 0 -1
07:20:52 From Catherine Lefèvre : #vote +1
07:21:00 From Srini Addepalli (Intel) : #vote +1
07:21:03 From Andreas Geissler : #vote +1
07:21:13 From ALLAGO : #vote +1
07:21:19 From Davide (Vodafone) : #vote +1
07:21:22 From Alexis de Talhouët : #vote 0
07:21:23 From Eric Debeau : #vote +1
07:21:25 From Milind Jalwadi (Tech Mahindra) : #vote +1
07:21:26 From Ciaran Johnston : #vote +1
07:21:37 From Chaker Al-Hakim : +1
07:21:42 From Viswa ( Verizon ) : #vote +1
07:21:43 From Jason Hunt : #vote +1
07:21:53 From Murat Turpcu,Turk Telekom : #vote +1
07:22:08 From Chaker Al-Hakim : #vote +1
07:22:29 From Kenny Paul (LFN) : #endvote
07:22:53 From Srini Addepalli (Intel) : Hi, I wanted to bring this up before we run of time. Intel lab is unavailable in second or third week of January as we are moving the ONAP lab to a different building. I will communicate more details and exact days as and when I get more information.
07:22:59 From Kenny Paul (LFN) : #AGREED the the TSC approves the NO GO as documented in (v. 63) of https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16398321
07:24:11 From Brian Freeman (AT&T) : Srini - ouch - understand need to move but this is a big impact
07:26:42 From Kenny Paul (LFN) : #info what was agreed in v. 63: NO GO- no impact on use cases/requirements: CLI, HOLMES, LOGGING => Re-use El Alto containers except if any blocking issue are identified during the Frankfurt testing cycle by the Integration Team. Any other finding (security, non blocking issue) should be documented in the Frankfurt Release Note
07:27:13 From Kenny Paul (LFN) : #info end of what was agreed
07:27:52 From Kenny Paul (LFN) : #topic CNCF topics for Kubecon meeting
07:30:51 From Brian Freeman (AT&T) : When is M2/M# vis a vis the windriver lab move ?
07:30:59 From Brian Freeman (AT&T) : m2/m3
07:34:50 From Kenny Paul (LFN) : #info Final M1 signoff will occur next week.