BRIDGE: https://zoom.us/j/661303200

Attendance 

Attendance is taken purely upon #info in Zoom Chat 

Previous Action Items

•  Pamela Dragosh to convene a group to discuss java 11 07 Nov 2019 - this action item will be tracked under the PTL meeting
  
•  Looking for a Volunteer to convene a group to discuss python3 (if required) - this action item will be tracked under the PTL meeting
  

New Action Items

• David McBride follow up on LCM API Evolution for status of completion 21 Nov 2019 

Zoom Chat Log 

05:57:27 From Sai Seshu : #info Seshu huawei
05:58:03 From Magnus Buhrgard (Ericsson) : #info Magnus Buhrgard (Ericsson)
05:59:22 From Catherine Lefèvre : #info, Catherine lefevre, att
05:59:29 From Andreas Geissler : #info Andreas Geissler, DT
05:59:38 From Stephen Terrill : #info, Stephen Terrill, Proxy for Ciaran, Ericsson
06:00:16 From Ranny Haiby (Samsung) : #info Ranny Haiby, Samsung
06:01:57 From Alexis de Talhouët : #info Alexis de Talhouët, Bell Canada
06:02:11 From Timo Perala (Nokia) : #info Timo Perala, Nokia
06:02:25 From Eric Debeau : #info Eric Debeau, Orange
06:04:16 From Avi Chapnick : Avi Chapnick , Proxy for Alla Goldner
06:04:26 From Jason Hunt : #info Jason Hunt, IBM
06:04:28 From Lingli : #info Lingli, CMCC
06:05:31 From Srinivasa Addepalli (Intel) : #info Srini Addepalli, Intel
06:07:13 From Ning So : #info, Ning So, Reliance Jio
06:07:49 From bin.yang@windriver.com : #info Bin Yang, Wind River
06:07:51 From Viswa ( Verizon ) : #info Viswa, Verizon
06:08:36 From Kenny Paul (LFN) : @Srini, Ning, Bin & Viswa - thanks
06:09:48 From Kenny Paul (LFN) : #topic TCC Update - Network Management
06:11:34 From Kenny Paul (LFN) : @Magnus shared content found on https://lf-onap.atlassian.net/wiki/display/DW/TCC+Generic+Network+Management
06:12:21 From Alexis de Talhouët : Congrats to all new TSC member! And many thanks to those stepping down. It’s been a pleasure partnering with you, and your valuable inputs were always enabling good discussions toward better open source project.
06:19:48 From Murat Turpcu,Turk Telekom : #info Murat TURPCU, türk telekom
06:21:34 From Kenny Paul (LFN) : @Murat- thanks
06:27:18 From Steven Wright : https://docs.onap.org/en/elalto/submodules/vnfrqts/requirements.git/docs/Chapter8/index.html
06:30:14 From Catherine Lefèvre : As stated, versioning is important but what about the implementation?
06:32:38 From Lingli : I prefer the specification to be consistent with the implementation. So we only
06:32:55 From Lingli : I need the release version
06:33:35 From Steven Wright : currently we publish specifications with ONAP releases, if there is something inconsistent with this please advise.
06:33:52 From Lingli : perhaps a rearrangement of our release documentation would do.
06:34:06 From Lingli : gu
06:35:43 From David McBride to Kenny Paul (LFN)(Privately) : Interesting that he didn’t mention GSMA or CNTT
06:35:59 From Lingli : for any third party referenced documents, create a permanent URL, where all released versions could be found.
06:36:08 From Stephen Terrill : The point to keep in mind is that it has to be a way to reference the specification in several years time (maybe 20?). I am not sure it has to be a URL, but that is one approach - but if we do have a URL, then are we sure that we are still using readthedocs in x years time?
06:37:10 From Lingli : An indirect point of reference could solve it.
06:37:21 From Ranny Haiby (Samsung) : It may be better to export the ONAP VES specification periodically to some longer term archive. It sounds like a bad idea to me to impose long term persistence on ONAP documentation
06:38:38 From Steven Wright : once the release documentation is published for a release, there is no longer active use of the tooling ( sphinx etc). I do not know who pays for the storage, domain name etc hosting the material.
06:40:29 From Eric Debeau : ONAP doc is duplicated to github today : https://github.com/onap/vnfrqts-requirements/blob/master/docs/Chapter8/VES_Registraion_3_2.rst
06:40:43 From Kenny Paul (LFN) : tome check- topic +10 mins
06:40:51 From Kenny Paul (LFN) : time check
06:41:41 From Eric Debeau : OpenAPI spec is also available on github: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md
06:41:43 From Kenny Paul (LFN) : @eric - that was also my initial thought. Just need to see if that is acceptable.
06:44:29 From Kenny Paul (LFN) : #topic Frankfurt M1
06:47:32 From Kenny Paul (LFN) : #AGREED the TSC approves the recommendations of the Release Manager for OOF, UUI & Portal as passing Frankfurt M1
06:52:08 From Kenny Paul (LFN) : #AGREED the TSC recommendations of the Release Manager for approving the usecases as found in v.404 of Frankfurt Release Requirements
06:52:43 From Kenny Paul (LFN) : scratch- the above
06:53:21 From Kenny Paul (LFN) : #AGREED the TSC approves the recommendations of the Release Manager for approving the usecases as found in v.404 of Frankfurt Release Requirements
06:57:27 From Kenny Paul (LFN) : #ACTION dmcbride follow up on LCM API Evolution for status of completion
06:57:35 From Kenny Paul (LFN) : -
06:59:54 From Kenny Paul (LFN) : #AGREED the TSC approves the recommendations of the Release Manager for approving the requirements marked as “YES” for passing M1 as found in v.404 of Frankfurt Release Requirements
07:00:12 From Srinivasa Addepalli (Intel) : I am sorry I need to drop early.
07:03:34 From Magnus Buhrgard (Ericsson) : The slides I showed for TCC Generic Network Management are now also available here: https://lf-onap.atlassian.net/wiki/display/DW/TCC+Generic+Network+Management
07:08:34 From Catherine Lefèvre : #AGREED To recommend TSC M1 approval as YES for Network slicing considering ExtAPI and SO components only impacted
07:09:24 From Brian Freeman (AT&T) : Does the TSC approve the the now GREEN use case for Plug and Play and Network Slicing as discussed during the TSC meeting for M1 [as long as it is Green]
07:14:16 From Kenny Paul (LFN) : #AGREED the TSC approves Plug and Play as meeting the M1
07:17:19 From Eric Debeau : If we xwant to plus GO with external NSSMF, we also need simulator for NSSMF to test use case
07:18:48 From Lingli : yes, we will use sumulator to do the test.
07:19:23 From Kenny Paul (LFN) : #info discussion regarding e2e Network Slicing regarding NSSMF inclusion
07:20:10 From Lingli : We are not dicussing inclusion of NSSMF.
07:20:35 From Lingli : inclusion of OOF for NSMF inclusion
07:20:53 From Kenny Paul (LFN) : - Shankar limited committer resources creates risk. Would require assistance from the usecase team
07:22:31 From Kenny Paul (LFN) : - Lingli does anyone on the usecase team have the resources to assist SO?
07:23:15 From Kenny Paul (LFN) : - LinMeng believe we have the resources
07:25:00 From Kenny Paul (LFN) : - Suggestion of making M2 deadline for determining if it in or out.
07:30:55 From Brian Freeman (AT&T) : I thought UUI was green for common and int he release - if UUI PTL concurs they are green as well then its okay ?
07:35:56 From Swaminathan S : Thanks to the TSC for considering our request.
07:36:23 From Kenny Paul (LFN) : #AGREED approves SO, ExtAPI  UUI scope only for E2E Network Slicing
07:36:59 From Kenny Paul (LFN) : #AGREED NSSMF is outside ONAP for E2E Network Slicing
07:37:26 From LinMeng(CMCC) : Thank you all for supporting this use case.
07:37:52 From Kenny Paul (LFN) : #AGREED OOF is provisionally approved for E2E Network Slicing and will be reviewed at M2
07:39:53 From Kenny Paul (LFN) : - SECCOM Communication Matrix
07:42:03 From Kenny Paul (LFN) : #AGREED that DCAE will be a prototype as per REQ-239 for the SECCOM Communication Matrix
07:44:45 From Catherine Lefèvre : Team - thanks for all - i am sorry i need to drop