TSC 2023-04-06
BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09
Passcode: 209247
We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
Attended | Proxy (w/ @name) | Holiday | Did Not Attend |
---|
Attendance is taken purely upon #info in Zoom Chat
Andreas Geißler(proxy Thomas Kulik ) | DT | Ericsson | ||
Orange | Individual | |||
Individual | F5 | |||
Huawei | Bell Canada | |||
China Telecom | Windriver | |||
AT&T | Nokia | |||
China Mobile |
Agenda Items | Presented By | Presos/Notes/Links/ | |
---|---|---|---|
Strategy (45 minutes) | ONAP takeaways | We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements. | |
LFN Cross-Organization UpdatesMAC, SPC, TAC, EUAG, LFN Board | Introducing Marek Szwalkiewicz - candidate for INT PTL #AGREED: Does the TSC approve Marek Szwalkiewicz as the PTL for the INT project? Announcement - Kevin Tang will be joining the TSC call next week (April 13) to provide an update on the Network Slicing use case | ||
TCC / ONAP Liaison Updates | |||
Task Force Updates | Proposed new Mission statement
#VOTE: does the TSC approve sharing the proposed new ONAP mission statement with the TAC? Vote deferred to next week There's some interest in the TSC with using "Program". Discuss with Magnus next week about what the specific objections were. How about "Provisioning"? Stacked rank survey: partnership, process, potential, prospect, project, provisioning Plan:
Shankar: include in the poll a question about whether TSC members agree or disagree with the new mission statement. Shankar: Third sentence should include "management". Magnus agreed to this last week.
| ||
Operations (40 minutes) | TSC Activities and Deadlines | ||
Release Status | London release status
#AGREED: Does the TSC approve that the requirements for the London M3 milestone have been met, with the exception of AAI, OOF, and DCAE? Montreal release
Plan for a vote on April 20, after the ONAP / ODL sync meeting. | ||
RelEng/Infrastructure | Update on enabling SBOM -- Update global-jjb: unpin tox version and remove tox-pyenv Breakage related to whitelist_externals → allowlist_externals | ||
PTL Updates | |||
Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements | |||
Events & Meetings (5 minutes) | Upcoming Events & Housekeeping | PTL meeting on Monday, April 10, is canceled due to the Easter Monday holiday in Europe Release name nominations
Pawel asks about Kohn awards. Kenny is working on it. Vote will be available soon. |
Zoom Chat Log
07:08:51 From Chaker Al-Hakim : #info Chaker Al-Hakim, IC
07:09:19 From David McBride : https://lf-onap.atlassian.net/wiki/x/I0fs
07:14:05 From David McBride : #VOTE: Does the TSC approve Marek Szwalkiewicz as the PTL for the INT project?
07:14:21 From N. K. Shankar : #vote +1
07:14:24 From Timo Perala (Nokia) : #vote +1
07:14:26 From Keguang He(China Mobile) : #vote +1
07:14:27 From Martial Ngueko(AT&T) : #vote +1
07:14:29 From Thomas KULIK (DT) : #vote +1
07:14:33 From Byung-Woo Jun : #vote +1
07:14:35 From Dan Xu : #vote +1
07:14:41 From Paweł Pawlak : #vote +1
07:15:16 From Chaker Al-Hakim : #vote +1
07:15:42 From Dong Wang (China Telecom) : #vote +1
07:15:52 From Kenny PAUL (LFN) : #endvote
07:16:07 From Kenny PAUL (LFN) : #APPROVED: the TSC approves Marek Szwalkiewicz as the PTL for the INT project
07:16:35 From Kenny PAUL (LFN) : ^^#AGREED
07:16:54 From Kenny PAUL (LFN) : Congrats Marek!
07:24:11 From Bengt Thuree LFN : Asked ChatGPT
Sure, here are some possible alternatives for the letter "P" in ONAP:
Open Network Automation Protocol
Open Network Automation Project
Open Network Automation Platformer
Open Network Automation Process
Open Network Automation Program
Open Network Automation Procedure
Open Network Automation Performance
Open Network Automation Provider
Open Network Automation Provisioning
Open Network Automation Policy
07:34:46 From Tony HANSEN (AT&T) : ONAP-E ??
07:35:24 From N Shankar : Comment on the mission statement. I had verbally provided a comment that the last sentence ".. to define, describe and evolve a common architecture for real-time, policy-driven orchestration and automation .." should include management as in the first sentence and read ".. to define, describe and evolve a common architecture for real-time, policy-driven orchestration, management and automation ..
07:41:43 From Tony HANSEN (AT&T) : ONAP-E for ONAP Evolved
07:42:11 From Byung-Woo Jun : Replying to "ONAP-E for ONAP Evol..."
ONAP-E for ONAP Evolved
I was wondering what E stands for. Thanks.
07:44:08 From David McBride : #VOTE: Does the TSC approve that the requirements for the London M3 milestone have been met, with the exception of AAI, OOF, and DCAE?
07:44:17 From Timo Perala (Nokia) : #vote +1
07:44:17 From Martial Ngueko(AT&T) : #vote +1
07:44:18 From Byung-Woo Jun : #vote +1
07:44:22 From Paweł Pawlak : #vote +1
07:44:25 From Thomas KULIK (DT) : #vote +1
07:44:26 From N Shankar : #vote +1
07:44:26 From Dan Xu : #vote +1
07:44:31 From Chaker Al-Hakim : #vote +1
07:44:34 From Keguang He(China Mobile) : #vote +1
07:44:37 From Dong Wang (China Telecom) : #vote +1
07:45:10 From Kenny PAUL (LFN) : #endvote
07:45:44 From Kenny PAUL (LFN) : #AGREED: The TSC approves that the requirements for the London M3 milestone have been met, with the exception of AAI, OOF, and DCAE.
07:51:26 From Liam Fallon : I need to drop
Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative! Information as to why .
They are included here as a time stamp cross-reference for the recording only! The notes above this line and the actual recordings are authoritative.