TSC 2020-04-09
BRIDGE: https://zoom.us/j/661303200
Attendance
Attended | Proxy (w/ @name) | Gov. Holiday | Did Not Attend |
---|
Attendance is taken purely upon #info in Zoom Chat
Alla.Goldner - proxy Mike Elliott | AMDOCS | IBM | ||
DT | China Mobile | |||
WindRiver | Turk Telecom | |||
cl664y@att.com - proxy: Ryan Hallahan for the last 30 mins. | AT&T | Reliance Jio | ||
Ericsson | Bell Canada | |||
Vodafone | Samsung | |||
China Telecom | Huawei | |||
Orange | Intel | |||
Verizon | Nokia |
Time | Agenda Items | Presented By | Presos/Notes/Links/ |
---|---|---|---|
45 | New project proposal | Configuration Persistency Service https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16398157 | |
15 | Release Status | Outside Frankfurt: CLI, Holmes, Log (incl. Pomba) - Suggested containers at M1 (El-Alto) do not seem compatible with other Frankfurt components? Completed: UUI, VNFReqs, VVP, VFC, VID, APPC, CLAMP, CCSDK, DCAE, DMaaP, ExtAPI, Modeling, SDC, SDNC, SO, VNFSDK
| |
10 | Subcommittee UpdateSecurity (POSTPONED TO 4/16) | Security MVP for Frankfurt Release | |
10 | Subcommittee UpdateArchitecture (POSTPONED TO 4/16) | Arch review policy and process VOTE: Does the TSC approve the architectural review policy and process documented above. | |
10 | RelEng/Infrastructure(Not discussed this week) | Usual RelEng updates (5 min)
| |
10 | Marketing Update(POSTPONED TO 4/16) | Frankfurt Marketing Launch
| |
10 | PTL UpdateDocumentation | Approval of Documentation SoW tasks:
| |
10 | Subcommittee UpdateControl Loop | Control Loop Sub Committee - request for repo for storing some common code for prototyping potential Guilin release requirements. Possibility of it evolving into a common codebase for Control Loops. | |
10 | TAC Update(POSTPONED TO 4/16) | OPNFV Charter Changes: https://wiki.opnfv.org/display/DEV/Agreements+Capture+Page OVP Charter Changes | |
5 | TSC Activities and Deadlines | Kenny Paul | TAC and SPC reviews
|
15 | Upcoming Events |
ONAP: 3 hours per day, for 3 days, held between 13:00 UTC and 16:00 UTC Currently Two parallel sessions Shall we cancel (or not) the TSC call since only 3 hours per day? https://wiki.lfnetworking.org/display/LN/2020+April+Virtual+Technical+Event Please submit your topics not later than April 13th, EOD Please register asap: https://events.linuxfoundation.org/lfn-technical-meetings-spring/ LFN Joint Planning Committee volunteer(s): Timo Perala Tool to track comments: "Quicochat" integrated to confluence, etc.
|
Action Items
- damian.nowak send an email regard ing status of REQ-80 to David McBride , cl664y@att.com and Kenny Paul
Zoom Chat Log
06:57:04 From Kenny Paul (LFN) : #topic rollcall
06:58:23 From Andreas Geissler : #info Andreas Geissler, DT
06:58:38 From Eric Debeau : #info Eric Debeau, Orange
06:58:40 From Fernando (Fred) Oliveira : #info Fred Oliveira, Verizon
06:59:24 From Ciaran Johnston : #info Ciaran Johnston, Ericsson
06:59:53 From bin.yang@windriver.com : #info Bin Yang, Wind River
07:00:06 From Olivier Phenix : #info Olivier Phenix, Bell Canada
07:00:09 From Dong Wang (China Telecom) : #info Dong Wang, China Telecom
07:00:46 From Ning So : #info, Ning So, Reliance Jio
07:00:46 From Timo Perala : #info Timo Perala, Nokia
07:00:56 From Srini Addepalli (Intel) : #info Srini Addepalli,Intel
07:01:50 From Ranny Haiby (Samsung) : #info Ranny Haiby, Samsung
07:02:05 From Jason Hunt : #info Jason Hunt, IBM
07:02:09 From Davide (Vodafone) : #info Davide Cherubini, Vodafone
07:02:15 From John J. Franey (AT&T) : #info John Franey, AT&T
07:02:40 From Tony Finnerty : #info Tony Finnerty, Ericsson
07:03:09 From John J. Franey (AT&T) : sorry, I'm not a member, ignore my info.
07:03:52 From Catherine Lefevre : #ATT, Catherine Lefevre until the top of the hour
07:04:14 From Sai Seshu : #info Seshu, huawei
07:06:00 From Kenny Paul (LFN) : #topic new project proposal -- Data Persistency Service
07:06:36 From Mike Elliott : #info Mike Elliott, Amdocs (proxy for Alla Goldner)
07:06:45 From Kenny Paul (LFN) : @mike thanks
07:07:54 From Murat Turpcu,Turk Telekom : #info Murat TURPCU, türk telekom
07:08:06 From Kenny Paul (LFN) : @murat thanks
07:10:07 From Benjamin Cheung : https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16374021
07:10:22 From Benjamin Cheung : https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16398157
07:11:32 From Krzysztof Opasiak : Doesn't it violate one of very basic microservice architecture prinicples?
07:11:33 From Krzysztof Opasiak : https://microservices.io/patterns/data/database-per-service.html
07:24:51 From sylvain.desbureaux@orange.com : I do see a big NIH syndrom here
07:25:20 From sylvain.desbureaux@orange.com : Why not using already existant Databases Engine (SQL or noSQL)?
07:26:38 From Eric Debeau : Why not extending A&AI ?
07:26:58 From Catherine Lefevre : +1 on Eric
07:28:39 From sylvain.desbureaux@orange.com : It also make me think of that: https://xkcd.com/927/
07:28:51 From sylvain.desbureaux@orange.com : And I strongly +1 Krzysztof
07:29:36 From Krzysztof Opasiak : I'm just a very stupid polish guy but I always thought that main rationale for having separate DB for every services is to make sure that components are loosly coupled and there is no hidden interdependencies. If we now introduce a single DB all components that are using it starts to be tightly coupled and upgrade of them would be a nightmare
07:29:36 From Kenny Paul (LFN) : time check
07:30:55 From Catherine Lefevre : I am concerned about latency
07:31:03 From Catherine Lefevre : if DB not local to app
07:31:12 From Catherine Lefevre : and locked up etc
07:31:29 From Pamela Dragosh : Even if the components share the same instance of a database, work will need to be done to ensure each codebase can work with that instance in how its configured (eg lowercase vs uppercase, certain configuration attributes, etc).
07:31:46 From Trevor Lovett : The categories of data mentioned overlap with many existing components: topology, connections, etc. are in A&AI, configuration data is in SDNC, data publishing via DMaaP, etc. This would seem to create confusion on what components should be used. I also agree with the risks of a shared data store. Storing arbitrary shared data creates a number of problems as others have noted.
07:31:51 From Catherine Lefevre : One "monster" DB will require a lot of re-work and I only see 2 dev on the project proposal
07:32:03 From Krzysztof Opasiak : +1 to Catherine concerns
07:32:13 From Pamela Dragosh : There also is still a very tight coupling between design-time and runtime-data per component. Splitting it off can require synchronization concerns.
07:32:40 From Catherine Lefevre : +1 Pam - replication will be challenging
07:33:41 From Catherine Lefevre : I agree we need to reduce the nbr of different DB i.e. MariaDB, MongoDB, PostgreSQL etc but not sure sure to centralize everyhting in one Monster DB -
07:33:52 From Pamela Dragosh : In addition, now we are adding another api on top of it whereas each component has its api for data access. Although I agree with consolidating into a source of truth, I’m concerned about adding another large amount of lines of code to all of ONAP. Would prefer to see projects or initiatives that help to reduce our codebase first.
07:35:01 From Kenny Paul (LFN) : time check +10
07:36:52 From Ranny Haiby (Samsung) : What is the plan for today? Vote on induction of RTCDB as an ONAP project?
07:36:58 From sylvain.desbureaux@orange.com : +1 to Catherine concerns
07:37:21 From Jason Hunt : Personally, I have some more investigation to do before I’m comfortable voting
07:37:24 From Damian Nowak : Perhaps the question, which shall be asked is -> what are eth data stored in that data-base
07:37:50 From Damian Nowak : as far as I underatdns, these are not application data, e.g. for APPC the intention is not to store there the APPC configuration templates
07:38:18 From Joanne Liu Rudel (AT&T) : SDN-C will update RunTime Config DB with Yang model from the network elements/VNF
07:38:20 From Ranny Haiby (Samsung) : May I suggest that the RTCDB will be done as a PoC for Guilin, and then we can consider induction as a project for the next release?
07:38:21 From Damian Nowak : I am essentially looking at this as a palce, where my analytics applications can look for teh configration data of NFs
07:38:50 From Damian Nowak : SO I can use teh confgiuration data of teh NFs in my analytics, beyond the events provided by these NFs
07:39:07 From Damian Nowak : There is a huge number of use-cases, where we need Fault + Performance + COnfiguration data
07:39:41 From Damian Nowak : But... on teh specific technology to be used, or if this can be merged with AAI, or sth like this - this is open...
07:40:06 From Damian Nowak : (sorry for typos, not that easy in teh Home Office these days)
07:40:30 From Ranny Haiby (Samsung) : @Damian - are you familiar with the Linux Foundation PNDA project (http://pnda.io) It may provide some of the functionality you are looking for
07:40:41 From Damian Nowak : @Ranny
07:41:04 From Kenny Paul (LFN) : time check
07:41:16 From Damian Nowak : Yes, I am aware of PNDA -> there was already an attempt to integrate this one, which wanst` really successful...
07:42:25 From Damian Nowak : But I think, we`re still missing something, where we could fetch the configuration data of NFs, without going to each NF instance with e..g. NetCOnf get-config command
07:43:47 From Jason Hunt to Kenny Paul (LFN)(Privately) : Hi Kenny - my apologies for this, but I have to leave at the top of the hour. I think the TAC update can be deferred to next week’s meeting, as there is nothing timely or requiring the TSC’s action.
07:44:00 From Kenny Paul (LFN) to Jason Hunt(Privately) : ok
07:44:22 From Jason Hunt to Kenny Paul (LFN)(Privately) : thanks
07:47:57 From Kenny Paul (LFN) : #topic Frankfurt release
07:58:45 From Catherine Lefevre : Team - I need to drop. Ryan H. is tking over
07:58:54 From Pamela Dragosh : +1 Kryzystopf - components should be able to upgrade regardless of whether are participating.
07:58:57 From Catherine Lefevre : great job PTLs - keep going !
08:02:23 From Kenny Paul (LFN) : time check
08:04:22 From Eric Debeau : #info proposed topic for next TSC Meeting: decide the list of components to be removed from the installer (eg Pomba, Holmes...)
08:06:00 From Kenny Paul (LFN) : #info added to the agenda
08:06:07 From sylvain.desbureaux@orange.com : Integration of CMPv2 into OOM is going well, hope to finalise soon
08:07:05 From Damian Nowak : Yep, I see improvements in OOM part for CMP v2 happening every day
08:08:04 From Morgan Richomme (Orange) : @seshu still a patch under review https://gerrit.onap.org/r/c/oom/+/103910, OOF delivered but still some security issues open covered by the patch
08:08:42 From Sai Seshu : OK thanks or the confirmation @Morgan … wanted to make sure we dint miss it out
08:12:10 From Kenny Paul (LFN) : time check +10
08:13:26 From Kenny Paul (LFN) : #ACTION Damiecn send an email regard ing status of REQ-80 to david, Catherine and I
08:18:29 From Kenny Paul (LFN) : #topic documentation SOW
08:21:08 From Kenny Paul (LFN) : #startvotre Does the TSC approve the tasks and prioritization for the Documentation S0W and captured in onap-tsc message #6120?
08:21:15 From Eric Debeau : #vote +1
08:21:21 From Andreas Geissler : #vote +1
08:21:22 From Olivier Phenix : #vote +1
08:21:24 From Sai Seshu : #vote +1
08:21:25 From Fernando (Fred) Oliveira : #vote +1
08:21:30 From Dong Wang (China Telecom) : #vote +1
08:21:36 From Ranny Haiby (Samsung) : #vote +1
08:21:37 From Timo Perala (Nokia) : #vote +1
08:21:46 From Mike Elliott (Amdocs) : #vote +1
08:21:49 From Davide (Vodafone) : #vote +1
08:22:03 From Murat Turpcu,Turk Telekom : #vote +1
08:22:12 From Srini Addepalli (Intel) : #vote +1
08:22:14 From Kenny Paul (LFN) : #endvote
08:24:14 From Kenny Paul (LFN) : #AGREED clx TSC meeting during VF2F
08:25:13 From Kenny Paul (LFN) : #AGREED the TSC approves the tasks and prioritization for the Documentation S0W and captured in onap-tsc message #6120
08:25:44 From Kenny Paul (LFN) : #topic controlloop
08:27:23 From Kenny Paul (LFN) : @Pam will persue process
08:27:31 From Kenny Paul (LFN) : #secccom
08:28:16 From Kenny Paul (LFN) : 3 waivers are needed for Frankfurt