You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
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.
Attendance
Attended | Proxy (w/ @name) | Gov. Holiday | Did Not Attend |
---|
Attendance is taken purely upon #info in Zoom Chat
| AMDOCS |
| | IBM |
| DT |
| | China Mobile |
| WindRiver |
| | Turk Telecom |
| AT&T |
| | Reliance Jio |
| Ericsson |
| | Bell Canada |
| Vodafone |
| | Samsung |
| China Telecom |
| | Huawei |
| Orange |
| | Intel |
| Verizon |
| | Nokia |
Time (mins) | Agenda Items | Presented By | Presos/Notes/Links/ |
---|
45 | Release Status | | - Guilin RC1
- Schedule
- Propose combining RC1 with RC2 / Sign Off on Nov 19.
- Ongoing issues with OOM/SO
-
SO-3322
-
Getting issue details...
STATUS
-
SO-3346
-
Getting issue details...
STATUS
-
SO-3352
-
Getting issue details...
STATUS
- Guilin Milestone Status
- Issue status (i.e., non-relman)
- Integration status
- Guilin RC2
- Honolulu
- Schedule proposed
- Please review and send feedback to David McBride . Be prepared to vote on the schedule on Nov 19.
- PTLs: Please complete survey regarding PTL availability in December.
- TSC Initial Feedback on Requirements
- Honolulu Release Requirements - 3 Use cases; 13 functional requirements (2 submitted post deadline) and 12 non functional requirements (1 submitted post-deadline)
- M1 approval field was used to provide some feedback - only 4 functional requirements are candidate to be approved
- Any new requirement submitted after Oct 16th, 2020 (Honolulu Deadline Submission) will be reviewed for the Istanbul release except Guilin requirement left-overs
- Missing Honolulu Impact View per Component and a lot of information to understand the requirements, company commitments etc. - Please use the Requirement Template
- Missing company commitments, specially for non functional requirement (30 mins PTL practice might not cover all the needs)
- REQ-428 - Is it aligned with the Modeling Subcommittee?
- Request to adopt a phasing approach for the Use Cases to avoid large number of components impacted within a release
- Automated Test Cases are required for the Use Cases - have you factorized this as part of your company's engagement?
- EUAG priorities? No new use case but continuity of former use cases i.e. 5G SON, Network Slicing, CCVPN, CNF
- ACTIONS - No later than Nov 12th, 2020:
- Subcommittees to follow up with the respective requirement owners and ensure that the remaining information is provided
- How does the TSC want to proceed with the first 4 approved requirements?
- Guilin left-overs - start to meet Requirement Subcommittee for review
|
5 | RelEng/Infrastructure | | - Tickets- Open showstoppers:
- Tickets- Waiting on Community:
- Migration Status / Upcoming Changes
|
5 | PTL Update | | |
5 | Subcommittee UpdateArch, Ctrl-Loop, Modeling, Seccom, Requirement |
| |
5 | EUAG Update |
|
|
5 | TCC / ONAP Liaison Update |
|
|
5 | TAC Update |
|
|
5 | Task Force UpdateCNF, Maintenance, ONAP Enterprise |
|
|
10 | TSC Activities and Deadlines | | Proposal to cancel the TSC meeting on Nov 26 due to the Thanksgiving holiday in the U.S. |
5 | Upcoming Events | Linux Foundation | - LFN Developer & Testing Forum - Feb 1 - 4 (tentative)
- Awaiting confirmation by the LFN TAC
|
Action Items
Zoom Chat Log