You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
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) | Holiday | Did Not Attend |
|---|
Attendance is taken purely upon #info in Zoom Chat
| DT |
| | China Mobile |
| Ericsson |
| | Individual |
| AT&T |
| | Individual |
| Huawei |
| | Windriver |
| China Telecom |
|
|
|
| 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 | Keguang He Sandra Jackson (Deactivated) Byung-Woo Jun | - China Mobile has a plan for Model as a Service (MaaS) utilizing large models
- China Mobile needs publicly accessible GPU-enabled virtual machines for development
- Can LFN provide or assist in acquiring a necessary public cloud infrastructure?
- LF and ONAP has lab resources to support the community via UNH-IOL.
- Keguang He , will check with his resources; Kevin Sandi , may help resources from LFN?
- Jack Lucas , Marek Szwałkiewicz , Andreas Geißler and others need a testing environment for potential ONAP enhancements
- Any update? Please contact Lincoln Lavoie for any questions/requests
- 2025 Budget
|
|
|
TCC / ONAP Liaison Updates |
|
|
|
|
Task Force Updates |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Operations (40 minutes)
| TSC Activities and Deadlines | | - ONAP Streamlining Documentation Enhancements for Oslo:
- Defining ONAP Core components and extensions (e.g., lightweight ONAP, optional components)
- Core component functions
- Installation guide, including ArgoCD-based deployment options
- configuration guide
- User guide
- Use cases by operators and vendors
- reference architecture (component, interface, security, function...) for lightweight ONAP
- PTLs will be contacted for core component contents, as needed
- Thomas Kulik, shared the tool https://wiki.onap.org/x/TYAmDg analysis, Thanks
- Start the documentation for ONAP Streamlining here, ONAP Streamlining Evolution
- Ongoing
|
|
|
Release Status | | - Oslo release wiki pages:-Byung will update its status next week
|
|
|
RelEng/Infrastructure | |
|
|
|
PTL Updates | |
|
|
|
| Subcommittee UpdatesArch, Lab, Modeling, Seccom, Requirements | | - The Architecture diagram for Oslo, Oslo-R15 Architecture Diagram - WIP to deprecate DMaaP
- Oslo Architecture main wiki pages, Oslo-R15 Architecture/ArchCom Wiki Page ; see its sub directories for project architecture pages
- Updated Oslo project component architecture descriptions
- Wait for Oslo requirement and architecture review requests (e.g., UUI GenAI requirements from Dong Wang and Keguang He ). Most likely in September.
- Byung-Woo Jun , will write the ONAP Streamlining document for architecture...
|
|
|
Events & Meetings (5 minutes) | 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.