Date
Meeting Logistics
Day | Time | Meeting ID | Zoom Link | Join by phone |
Monday | [sdc] Team ONAP4, Mon UTC 15:00 / China 23:00 / Eastern 10:00 / Pacific 07:00 | 489 989 304 | https://zoom.us/j/489989304 | Or iPhone one-tap (US Toll): +14086380968,,489989304# or +16465588656,,489989304# Or Telephone:Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) International numbers available: https://zoom.us/zoomconference?m=aBHgZkfSu_j-URGxXCTMLZ2_0FUeopNH |
Meeting Attendees
Agenda & Minutes
Review open action items from last week
Agenda | Minutes | Slides |
SDC status in the sprint | update about the work being done in sdc this sprint. | |
Archive feature presentation | presentation regarding the Archive option available in SDC today. | |
Q&A | general QA | |
Presentation regarding the NS concept | the request from the SDC team was to support this for R3. SDC stated that this is a very late submission of requirements and the implantation is a difficult one. the fasts option for this would be to define NS as a vnf. because this work is stile in definition state, sdc suggested to define it as a POC that will be done on a fork of sdc, sdc will assist in importing the node type. |
Action Items
- Michael Lando review the solution for SDC-1401 - Fix Zip Slip vulnerabilities when content of a ZIP files is extracted Open
- Michael Lando document the high level contributions from AT&T.
- Michael Lando show case sol 004 show case
- Michael Lando document the licensing header requirements for SDC. SDC-1576 - Document the License requirements for SDC Open
Recording
Chat
17:09:50 From maopeng : Hi Michael, could you give a slot for me to discuss network service in this meeting or tues day meeting? thanks
17:27:13 From Michael Lando (SDC) : yes no problem
17:27:27 From Michael Lando (SDC) : after the QA i will provide you with the time
17:27:48 From maopeng : thanks Michael
17:39:39 From Michael Lando (SDC) : DCAE-Design Studio
17:47:57 From Lingli : I don’t think it requires recursion in this proposal
17:48:43 From Lingli : it could be implemented as a type of service with simple restrictions
17:49:08 From Lingli : on the type of resources in its combination