You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 24
Next »
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) | Gov. Holiday | Did Not Attend |
---|
Attendance is taken purely upon #info in Zoom Chat
| AMDOCS |
| | Individual Contributor |
| DT |
| | Ericsson |
| WindRiver |
| | STL |
| Bell Canada |
| | Samsung |
| AT&T |
| | Huawei |
| China Telecom |
| | Nokia |
| Orange |
| | China Mobile |
Agenda Items | Presented By | Presos/Notes/Links/ |
---|
Release Status | | Weekly update Jakarta Release - M2 exceptions have been met - Congratulations !!! Next Milestone: M3 on March 3rd, 2022 Istanbul Maintenance Release slipped one week to Feb 17 due to unresolved Jira issues and ongoing problems with x-testing. |
RelEng/Infrastructure | | - Tickets- Open showstoppers:
- Tickets- Waiting on Community:
- Migration Status / Upcoming Changes
- Discussion of a couple of CI-MAN commits which are pending review. - Seshu and Jess to talk off-line
|
RelEng/Infrastructure | | - Proposal for an additional lab on Azure to run daily tests on Azure so ONAP community would have it’s own and independent schedule to execute tests.
- Scope is being prepared for discussion
|
Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements |
| - Where do we move 3GPP VES specification ownership? Options to host '3GPP VES specification' :
- E-mail sent to the ONAP Modeling Subcommittee - VES Specifications
- Thank you to the Modeling Subcommunity to take it over
- Magnus Buhrgard (Unlicensed) 3GPP won't pick up any thing new related to the VES spec - will stick to the reference they have already taken from ONAP
- N.K. Shankaranarayanan some discussion needed coming out of ORAN discussions which includes aspects of licensing / IPR
- Investigate how we can move existing repo under Modeling or leave as active in VNFRQTS -
https://gerrit.onap.org/r/admin/repos/vnfrqts/requirements,branches - Magnus notes that the path must remain intact - cannot change.
- #AGREED all Committers and rights currently assigned to the Modeling repo will also be applied to the VNFRQTS/requirements Repo. - all other VNFRQTS repos to be moved to read only.
|
Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements | | - Application Service Descriptor (ASD) - model approval
 - ASD is a simplified (Compared to ETSI-NFV SOL001) method for Cloud Native Network Function (CNF) description.
- A PoC implementation is being developed as part of Jakarta.
- This work is related to the CNFF Taskforce report presented by Byung-Woo Jun and Fernando Oliveira during the last TSC meeting.
- There was a poll to approve the ASD spec in the modeling subcommittee. There was one "no" vote, stating the need for ETSI-NFV alignment. However, by definition the ASD is different from ETSI-NFV specification.
- cl664y@att.com- What is the plan long term? Keep two alternatives (ETSI and ASD), or merge them? Byung-Woo Jun - ASD is an additional path to the ETSI-aligned-orchestration. Fernando Oliveira - There is a planned meeting between ONAP ASD creators and ETSI-NFV workgroup to figure out if the two approaches may be reconciled.
- The team working on ASD implementation would like to have a clear "go" from the modeling subcommittee so they can continue integration with SDC and other ONAP modules.
- Kenny Paul - Unclear how a three-participant poll determined the decision of the modeling subcommittee
- Eric Debeau - Concerned about creating two alternative orchestration approaches.
- Thinh Nguyenphu (Unlicensed) - Re: Joint workshop with ETSI NFV on ASD proposal (onap.org)
Next steps: - Magnus Buhrgard (Unlicensed) Clarify the area and find an agreement with the ONAP Modeling team
- Ranny Haiby Participate to the Joint workshop with ETSI NFV on ASD proposal on is Monday Feb 21st, 2-3 pm C.E.T
- Ranny Haiby Anybody interested to learn about the technical ASD proposal to join the CNF Task Force on 2/15 at 3pm CET/9am EST/6am PST
Additional technical information: |
PTL Updates | Thomas Kulik | We are lacking Thomas Kulik ONAP Community - please contact Thomas Kulik if you believe any improvement is required - Thanks Thomas Kulik for all the improvements already integrated. |
LFN Cross-Organization UpdatesMAC, SPC, TAC, EUAG, LFN Board |
| ONAP SPC representative |
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise |
| Wiki 2.0 - Call for Volunteers Thank you Chaker Al-Hakim , Ranny Haiby , Timo Perala to be part of it as participant Need a lead for this task force |
TSC Activities and Deadlines | | |
Upcoming Events & Housekeeping | | |
Zoom Chat Log
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.