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

Attendance 

Attendance is taken purely upon #info in Zoom Chat 

Action Items

Zoom Chat Log 

06:52:50 From Kenny Paul (LFN) : #topic rollcall
06:56:08 From Fernando (Fred) Oliveira : #info Fred Oliveira, Verizon
06:59:03 From bin.yang@windriver.com : #info Bin Yang, Wind River
06:59:35 From Sai Seshu : #info Seshu, huawei
06:59:52 From Ning So : #info Ning So, Reliance Jio
06:59:52 From Catherine Lefevre : #info, Catherine Lefevre
07:00:10 From Dong Wang (China Telecom) : #info Dong Wang, China Telecom
07:00:25 From Timo Perala : #info Timo Perala, Nokia
07:00:31 From Andreas Geissler : #info Andreas Geissler, DT
07:00:32 From Ciaran Johnston : #info Ciaran Johnston, Ericsson
07:00:55 From Eric Debeau : #info Eric Debeau, Orange
07:01:18 From Murat Turpcu,Turk Telekom : #info Murat TURPCU, Türk Telekom
07:01:20 From Jason Hunt : #info Jason Hunt, IBM
07:02:22 From Davide Cherubini (Vodafone) : #info Davide Cherubini, Vodafone
07:02:55 From Ranny Haiby (Samsung) : #info Ranny Haiby, Samsung
07:03:24 From Srini Add : #info Srini Addepalli, Inel
07:03:37 From Srini Add : #info Srini Addepalli, Intel
07:07:07 From Eric Debeau : THe Press release is there: https://www.onap.org/announcement/2020/06/18/onaps-6th-release-frankfurt-available-now-most-comprehensive-secure-and-collaborative-software-to-accelerate-5g-deployments
07:07:14 From Kenny Paul (LFN) : #topic Frankfurt
07:07:30 From Kenny Paul (LFN) : Press release going out this morning
07:07:51 From Kenny Paul (LFN) : ZTSC provisions have been met :-)
07:08:55 From Kenny Paul (LFN) : #topic Configuration & Persistency Service Project Proposal
07:09:26 From Bruno Sakoto : # Bruno Sakoto for Bell (Olivier proxy)
07:10:43 From Kenny Paul (LFN) : @bruno thanks
07:13:35 From Jason Hunt : where is the link to this presentation?
07:15:16 From Kenny Paul (LFN) : link to the project page https://lf-onap.atlassian.net/wiki/x/TTf6
07:17:47 From Catherine Lefevre : Is there a reason why Model storage is in CP&S and not in SDC?
07:19:48 From Catherine Lefevre : sounds like a lot of "copy' into CP&S ... and therefore a lot of sync mechanisms to be put in place
07:20:03 From Catherine Lefevre : or CP&S =cache DB role?
07:20:16 From Srini Add : What models do you intend to support for NF configuration? I would assume Yang is one such thing? Any thing else such as TR-069 & K8s Custom Resource templates?
07:20:48 From Ciaran Johnston : The models are distributed by SDC into this "model service"
07:20:55 From Avi Chapnick : is it a general data persistency technology?
07:21:04 From Ciaran Johnston : Yes, YANG is a primary driver
07:21:09 From Joanne Liu Rudel : SDC with onboard package (Yang model) will be distributed to CDS/C&PS
07:21:37 From Srini Add : Thanks @Ciaran.
07:21:42 From Joanne Liu Rudel : SDC will have Dat base record for the modeling
07:22:06 From Ciaran Johnston : Avi, the underlying DB is general purpose, supporting generic or non-schema persistence
07:22:07 From Srini Add : Does this project also talk to NFs over NetConf? Or Does it use other projects to deliver the data to NFs?
07:23:04 From Joanne Liu Rudel : C&PS is the real time network configuration data.
07:24:02 From Avi Chapnick : does this replace the NF controller such as APPC which was suppose to be the source of truth of NF application configuration ?
07:24:04 From Joanne Liu Rudel : Network configuration data will be received by Netconf/yang from SDN-C(R) and put the real time yang model to C&PS
07:27:12 From Catherine Lefevre : we need to avoid tu duplicate same information into multiple components
07:28:14 From Srini Add to Kenny Paul (LFN)(Privately) : Hi Kenny, Need to drop today at 7:30 for a customer meeting.
07:28:30 From Catherine Lefevre : i thougth CP&S will store 5G/RAN conf data not stored anywhere in ONAP Today - then it made sense but if we duplicate - sync issues, adding latency with extra layer are my concenrs
07:28:36 From Kenny Paul (LFN) to Srini Add(Privately) : k
07:28:55 From Jason Hunt : in the spirit of our principle of “modularity”, how do we ensure that the APIs for this are well-defined, standardized (if possible) allowing operators to substitute their own functionality?
07:29:13 From Ciaran Johnston : Catherine, I understand your concerns and share them
07:30:02 From Joanne Liu Rudel : C&PS is the real time network configuration data. It is not duplicated from A&AI. C&PS will only get PNF objects from A&AI initially.
07:30:39 From Catherine Lefevre : if it was AAI initally then why do we need to change now?
07:31:10 From Catherine Lefevre : oups sorry - mis-read the comment
07:32:07 From Ciaran Johnston : I guess the duplication that concerns you is between the controllers and the CPS?
07:32:07 From Olivier olivier.phenix@bell.ca : #info Olivier Phénix, Bell Canada
07:32:16 From Olivier olivier.phenix@bell.ca : Sorry for being late, Bruno was there to cover for me :)
07:32:34 From Kenny Paul (LFN) : @Olivier thanks
07:33:04 From Avi Chapnick : #info Avi Chapnick, Amdocs (proxy for Alla)
07:33:14 From Joanne Liu Rudel : When C&PS gets PNF objects from A&AI initially, C&PS will have the scheme based on Yang model to sync up the real time network configuration data.
07:33:16 From Kenny Paul (LFN) : @Avi thanks
07:33:27 From Pamela Dragosh : Agree with Jason. It would be good to start changing the development culture in ONAP towards using an “API-first” approach with new projects being introduced into ONAP.
07:34:11 From Krzysztof Opasiak : +1 to Pam!!!
07:35:12 From Sylvain Desbureaux : +1 to Pam too
07:36:08 From Ciaran Johnston : +1 from me too. Part of the PoC should start to specify that API
07:37:58 From Eric Debeau : +1 with well defined Swagger API
07:38:02 From Joanne Liu Rudel : APIs will be defined for C&PS in Guilin release.
07:39:26 From Joanne Liu Rudel : i.e: SDN-C(R) and C&PS (CDS). VES/DMaaP to C&PS (CDS). SDC/DMaaP to C&PS.
07:39:48 From Pamela Dragosh : That’s great Joanne/Ciaran. One suggestion it to look at Postman as the tool to help create the API and vet it. And yes Eric, that tool revolves around creation of a swagger (eg OpenAPI) definition of the API.
07:40:34 From Avi Chapnick : CCDSK was meant to host all ONAP controller platform components , what makes this outstanding?
07:41:43 From Joanne Liu Rudel : For Guilin Release, it was suggested to put C&PS in CCSDK in Guilin release
07:48:42 From Kenny Paul (LFN) : link to definitions https://lf-onap.atlassian.net/wiki/x/n1z6
07:49:36 From Benjamin Cheung : POC Definition:
07:49:36 From Benjamin Cheung : https://lf-onap.atlassian.net/wiki/display/DW/POC+definition
07:53:45 From Catherine Lefevre : no TSC vote is required since it is a POC
07:54:11 From Fernando (Fred) Oliveira : Sorry, I need to drop.
07:54:31 From Catherine Lefevre : Alla/Ranny have also been working together on a path from POC to release requirement
07:54:33 From Sai Seshu : Discuss this in the details on the questions
07:54:43 From Sai Seshu : You had over so
07:54:51 From Catherine Lefevre : maybe something to present one day to the TSC when they will be ready
07:55:20 From Kenny Paul (LFN) : As per the TSC definition: Approval for inclusion - The TSC or Use Case S/C shall approve the PoC to proceed as part of the current release.
07:55:39 From Kenny Paul (LFN) : POC definition not TSC definition
07:55:42 From Catherine Lefevre : POC is not part of the release
07:56:01 From Catherine Lefevre : POC can be performed outside the release timeline
07:56:08 From Catherine Lefevre : we never approve any so far
07:56:27 From Kenny Paul (LFN) : Then the definition of POC that the TSC approved on Oct 29, 2019 needs to be changed
07:56:38 From Catherine Lefevre : I am checking
08:03:36 From Pamela Dragosh : It should have been included on the bottom of this page: https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Requirements
08:04:14 From Pamela Dragosh : We have the same issue coming up for the Control Loop TOSCA POC that we would like to be introduced, but missed the deadline to get it on that page.
08:04:48 From Tony Finnerty : Yes, I missed the deadline for the PoC, and have asked for an exemption
08:08:11 From Catherine Lefevre : apologies to the PTL representatives - not sure we will be able to review all
08:10:21 From Pamela Dragosh : That assumes the PoC would use an existing repo. If it needs new repos, would they need TSC approval for that?
08:10:53 From Catherine Lefevre : new repo should follow the normal process
08:11:05 From Catherine Lefevre : ask infrastructure coordinator
08:12:21 From Catherine Lefevre : @Tony- you should be good
08:13:05 From Catherine Lefevre : @Liam, Pam - POC CL TOsCA you should be good but we appreciate that you share what you plan to do
08:13:10 From Tony Finnerty : ok, thanks
08:13:16 From Catherine Lefevre : probably not today because we are running late
08:13:48 From Pamela Dragosh : Ok thank you Catherine.
08:17:20 From Benjamin Cheung : #AGree
08:17:21 From Benjamin Cheung : 06:52:50 From Kenny Paul (LFN) : #topic rollcall
06:56:08 From Fernando (Fred) Oliveira : #info Fred Oliveira, Verizon
06:59:03 From bin.yang@windriver.com : #info Bin Yang, Wind River
06:59:35 From Sai Seshu : #info Seshu, huawei
06:59:52 From Ning So : #info Ning So, Reliance Jio
06:59:52 From Catherine Lefevre : #info, Catherine Lefevre
07:00:10 From Dong Wang (China Telecom) : #info Dong Wang, China Telecom
07:00:25 From Timo Perala : #info Timo Perala, Nokia
07:00:31 From Andreas Geissler : #info Andreas Geissler, DT
07:00:32 From Ciaran Johnston : #info Ciaran Johnston, Ericsson
07:00:55 From Eric Debeau : #info Eric Debeau, Orange
07:01:18 From Murat Turpcu,Turk Telekom : #info Murat TURPCU, Türk Telekom
07:01:20 From Jason Hunt : #info Jason Hunt, IBM
07:02:22 From Davide Cherubini (Vodafone) : #info Davide Cherubini, Vodafone
07:02:55 From Ranny Haiby (Samsung) : #info Ranny Haiby, Samsung
07:03:24 From Srini Add : #info Srini Addepalli, Inel
07:03:37 From Srini Add : #info Srini Addepalli, Intel
07:07:07 From Eric Debeau : THe Press release is there: https://www.onap.org/announcement/2020/06/18/onaps-6th-release-frankfurt-available-now-most-comprehensive-secure-and-collaborative-software-to-accelerate-5g-deployments
07:07:14 From Kenny Paul (LFN) : #topic Frankfurt
07:07:30 From Kenny Paul (LFN) : Press release going out this morning
07:07:51 From Kenny Paul (LFN) : ZTSC provisions have been met :-)
07:08:55 From Kenny Paul (LFN) : #topic Configuration & Persistency Service Project Proposal
07:09:26 From Bruno Sakoto : # Bruno Sakoto for Bell (Olivier proxy)
07:10:43 From Kenny Paul (LFN) : @bruno thanks
07:13:35 From Jason Hunt : where is the link to this presentation?
07:15:16 From Kenny Paul (LFN) : link to the project page https://lf-onap.atlassian.net/wiki/x/TTf6
07:17:47 From Catherine Lefevre : Is there a reason why Model storage is in CP&S and not in SDC?
07:19:48 From Catherine Lefevre : sounds like a lot of "copy' into CP&S ... and therefore a lot of sync mechanisms to be put in place
07:20:03 From Catherine Lefevre : or CP&S =cache DB role?
07:20:16 From Srini Add : What models do you intend to support for NF configuration? I would assume Yang is one such thing? Any thing else such as TR-069 & K8s Custom Resource templates?
07:20:48 From Ciaran Johnston : The models are distributed by SDC into this "model service"
07:20:55 From Avi Chapnick : is it a general data persistency technology?
07:21:04 From Ciaran Johnston : Yes, YANG is a primary driver
07:21:09 From Joanne Liu Rudel : SDC with onboard package (Yang model) will be distributed to CDS/C&PS
07:21:37 From Srini Add : Thanks @Ciaran.
07:21:42 From Joanne Liu Rudel : SDC will have Dat base record for the modeling
07:22:06 From Ciaran Johnston : Avi, the underlying DB is general purpose, supporting generic or non-schema persistence
07:22:07 From Srini Add : Does this project also talk to NFs over NetConf? Or Does it use other projects to deliver the data to NFs?
07:23:04 From Joanne Liu Rudel : C&PS is the real time network configuration data.
07:24:02 From Avi Chapnick : does this replace the NF controller such as APPC which was suppose to be the source of truth of NF application configuration ?
07:24:04 From Joanne Liu Rudel : Network configuration data will be received by Netconf/yang from SDN-C(R) and put the real time yang model to C&PS
07:27:12 From Catherine Lefevre : we need to avoid tu duplicate same information into multiple components
07:28:14 From Srini Add to Kenny Paul (LFN)(Privately) : Hi Kenny, Need to drop today at 7:30 for a customer meeting.
07:28:30 From Catherine Lefevre : i thougth CP&S will store 5G/RAN conf data not stored anywhere in ONAP Today - then it made sense but if we duplicate - sync issues, adding latency with extra layer are my concenrs
07:28:36 From Kenny Paul (LFN) to Srini Add(Privately) : k
07:28:55 From Jason Hunt : in the spirit of our principle of “modularity”, how do we ensure that the APIs for this are well-defined, standardized (if possible) allowing operators to substitute their own functionality?
07:29:13 From Ciaran Johnston : Catherine, I understand your concerns and share them
07:30:02 From Joanne Liu Rudel : C&PS is the real time network configuration data. It is not duplicated from A&AI. C&PS will only get PNF objects from A&AI initially.
07:30:39 From Catherine Lefevre : if it was AAI initally then why do we need to change now?
07:31:10 From Catherine Lefevre : oups sorry - mis-read the comment
07:32:07 From Ciaran Johnston : I guess the duplication that concerns you is between the controllers and the CPS?
07:32:07 From Olivier olivier.phenix@bell.ca : #info Olivier Phénix, Bell Canada
07:32:16 From Olivier olivier.phenix@bell.ca : Sorry for being late, Bruno was there to cover for me :)
07:32:34 From Kenny Paul (LFN) : @Olivier thanks
07:33:04 From Avi Chapnick : #info Avi Chapnick, Amdocs (proxy for Alla)
07:33:14 From Joanne Liu Rudel : When C&PS gets PNF objects from A&AI initially, C&PS will have the scheme based on Yang model to sync up the real time network configuration data.
07:33:16 From Kenny Paul (LFN) : @Avi thanks
07:33:27 From Pamela Dragosh : Agree with Jason. It would be good to start changing the development culture in ONAP towards using an “API-first” approach with new projects being introduced into ONAP.
07:34:11 From Krzysztof Opasiak : +1 to Pam!!!
07:35:12 From Sylvain Desbureaux : +1 to Pam too
07:36:08 From Ciaran Johnston : +1 from me too. Part of the PoC should start to specify that API
07:37:58 From Eric Debeau : +1 with well defined Swagger API
07:38:02 From Joanne Liu Rudel : APIs will be defined for C&PS in Guilin release.
07:39:26 From Joanne Liu Rudel : i.e: SDN-C(R) and C&PS (CDS). VES/DMaaP to C&PS (CDS). SDC/DMaaP to C&PS.
07:39:48 From Pamela Dragosh : That’s great Joanne/Ciaran. One suggestion it to look at Postman as the tool to help create the API and vet it. And yes Eric, that tool revolves around creation of a swagger (eg OpenAPI) definition of the API.
07:40:34 From Avi Chapnick : CCDSK was meant to host all ONAP controller platform components , what makes this outstanding?
07:41:43 From Joanne Liu Rudel : For Guilin Release, it was suggested to put C&PS in CCSDK in Guilin release
07:48:42 From Kenny Paul (LFN) : link to definitions https://lf-onap.atlassian.net/wiki/x/n1z6
07:49:36 From Benjamin Cheung : POC Definition:
07:49:36 From Benjamin Cheung : https://lf-onap.atlassian.net/wiki/display/DW/POC+definition
07:53:45 From Catherine Lefevre : no TSC vote is required since it is a POC
07:54:11 From Fernando (Fred) Oliveira : Sorry, I need to drop.
07:54:31 From Catherine Lefevre : Alla/Ranny have also been working together on a path from POC to release requirement
07:54:33 From Sai Seshu : Discuss this in the details on the questions
07:54:43 From Sai Seshu : You had over so
07:54:51 From Catherine Lefevre : maybe something to present one day to the TSC when they will be ready
07:55:20 From Kenny Paul (LFN) : As per the TSC definition: Approval for inclusion - The TSC or Use Case S/C shall approve the PoC to proceed as part of the current release.
07:55:39 From Kenny Paul (LFN) : POC definition not TSC definition
07:55:42 From Catherine Lefevre : POC is not part of the release
07:56:01 From Catherine Lefevre : POC can be performed outside the release timeline
07:56:08 From Catherine Lefevre : we never approve any so far
07:56:27 From Kenny Paul (LFN) : Then the definition of POC that the TSC approved on Oct 29, 2019 needs to be changed
07:56:38 From Catherine Lefevre : I am checking
08:03:36 From Pamela Dragosh : It should have been included on the bottom of this page: https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Requirements
08:04:14 From Pamela Dragosh : We have the same issue coming up for the Control Loop TOSCA POC that we would like to be introduced, but missed the deadline to get it on that page.
08:04:48 From Tony Finnerty : Yes, I missed the deadline for the PoC, and have asked for an exemption
08:08:11 From Catherine Lefevre : apologies to the PTL representatives - not sure we will be able to review all
08:10:21 From Pamela Dragosh : That assumes the PoC would use an existing repo. If it needs new repos, would they need TSC approval for that?
08:10:53 From Catherine Lefevre : new repo should follow the normal process
08:11:05 From Catherine Lefevre : ask infrastructure coordinator
08:12:21 From Catherine Lefevre : @Tony- you should be good
08:13:05 From Catherine Lefevre : @Liam, Pam - POC CL TOsCA you should be good but we appreciate that you share what you plan to do
08:13:10 From Tony Finnerty : ok, thanks
08:13:16 From Catherine Lefevre : probably not today because we are running late
08:13:48 From Pamela Dragosh : Ok thank you Catherine.
08:17:20 From Benjamin Cheung : #AGree
08:17:21 From Benjamin Cheung : anybody can build a POC always nice to share intent of the PoC w/ TSC to faciltate inclusion later what's important is to follow guidelines because don't want to break release that committed 3J - approval for inclusion exception - normally a PoC should not be incorporate into the same release anybody can build a PoC at any time There should be no DEADLINE to incorporate into this page: https://lf-onap.atlassian.net/wiki/display/DW/Guilin+Release+Requirements don't generate any regression issue. Resources committment / integration - PoCs from PREVIOUS release incorporating into CURRENT release.
08:20:52 From Catherine Lefevre : liam, pam - shall we keep you poc presentation for july 2nd?
08:24:05 From Pamela Dragosh : Yes - Liam and Michela will present. I will be OOO.
08:26:41 From Pamela Dragosh : Policy team will have 1st set of containers in 2 weeks.
08:27:44 From Brandon Wick : https://zoom.us/webinar/register/WN_UQR4N-PMQbWcus9m9AkM-w
08:33:11 From Kenny Paul (LFN) : Frankfurt launch announcement: https://www.onap.org/software
08:38:08 From Catherine Lefevre : Kudos onap team !!!!
08:38:14 From Catherine Lefevre : thanks timo and Ranny for DDF !!!

08:20:52 From Catherine Lefevre : liam, pam - shall we keep you poc presentation for july 2nd?
08:24:05 From Pamela Dragosh : Yes - Liam and Michela will present. I will be OOO.
08:26:41 From Pamela Dragosh : Policy team will have 1st set of containers in 2 weeks.
08:27:44 From Brandon Wick : https://zoom.us/webinar/register/WN_UQR4N-PMQbWcus9m9AkM-w
08:33:11 From Kenny Paul (LFN) : Frankfurt launch announcement: https://www.onap.org/software
08:38:08 From Catherine Lefevre : Kudos onap team !!!!
08:38:14 From Catherine Lefevre : thanks timo and Ranny for DDF !!!