Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Hi David, all, Thanks for raising this issue! Similar to others, I believe we should handle this by creating (and then enforcing) best practices on code quality and code reviews starting from Release 2. Best regards, Alla Goldner Open Network Division Amdocs Technology

[onap-tsc] Enforcing an "Upstream first" approach to ONAP

+1 for raising this topic We should avoid 10k LOC patches because it is very complex to review and is not aligned with an open source spirit. I do not believe that we should create another subcommitte to handle such issue. The integration project may be able to detect such behavior and alerts

[onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face

+1 Eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Thank you Helen. Appreciate the leadership. Mazin Sent through AT's fastest network On Aug 3, 2017, at 7:00 PM, Yunxia Chen > wrote: Hi, Mazin, The Integration team will take this one as an action item: we will define a list, (there’s other

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I am ok if the integration team wants to take the task of defining best code practices and guidelines on significant code insertion. I agree with Ash that code that can not be reviewed should not be committed blindly. But we need to form guidelines so we are all following the same practices.

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Hi, Mazin, The Integration team will take this one as an action item: we will define a list, (there’s other best code practice as well, such as code review etc.). with an implementation plan since we may not able to do everything in R1, and get TSC’s approval. Regards, Helen Chen From:

Re: [onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE use case

Hi, Can you elaborate on what #4 means? Thanks, Alex Vul Intel Corporation From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of denghui (L) Sent: Thursday, August 3, 2017 8:34 AM To: onap-disc...@lists.onap.org; onap-tsc

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I do tend to agree with Oliver here. There is a process of simply getting existing code upstream at all. Ideally, this happens with all the 'seed' code for a project going out at project creation. Early on in communities, this is sometimes difficult for a variety of reasons. As communities

[onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE use case

Hello all After 3 days continuous teleconf during modeling subcommittee, we finally made concensus on this. Thanks everybody. https://wiki.onap.org/display/DW/Modeling+sub-committee+meetings 1) SDC team will start to support service composition from R2 2) agree the hack solution, SDC will

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Hi, It great that David highlighted this need, just a few thoughts from my perspective: * I read that there is general agreement about going for upstream first. Maybe its not about introducing something new actually. When looking at our Wiki, we already have guidance:

Re: [onap-tsc] ONAP VoLTE SDC call

All, SDC can support SO suggestion for VoLTE service design presented in th call. With that, I believe we concluded the discussion about the different options, and we are moving forward with Option A. 1. SDC supports onboarding the vIMS and vEPC validated (VNF SDK) VNFs. 2. vIMS,

Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

+1! From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael Brenner Sent: 03 August 2017 20:05 To: SHADMI, DAVID Cc: KAPELUTO, ZAHI ; onap-disc...@lists.onap.org; onap-tsc ; ROZIN,

Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

Very nice outcome indeed; 10x to all involved. Now we need to deliver. From: Stephen Terrill [mailto:stephen.terr...@ericsson.com] Sent: Thursday, August 03, 2017 9:14 PM To: Michael Brenner ; SHADMI, DAVID Cc: Kapeluto, Zahi ;

Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

+1 On Thu, Aug 3, 2017 at 3:41 PM, Lando,Michael wrote: > Since we were able to agree on a solution using SDC. > > > > I suggest we do not move forward with the addition of the VNF-DESIGNE code > to the SDC repository. > > > > I think the resource of the community can be

Re: [onap-tsc] [onap-discuss] ONAP VoLTE SDC call

Since we were able to agree on a solution using SDC. I suggest we do not move forward with the addition of the VNF-DESIGNE code to the SDC repository. I think the resource of the community can be spent on contributing to SDC and helping us reach R1 successfully. BR, Michael Lando SDC PTL AT

Re: [onap-tsc] [VoLTE][Control Loop] VoLTE Use Case Control Loop Automation followup discussion

Hi, The detail of VoLTE use case control loop related to fault correlation has been updated in the following page. Please review and welcome comments. Thanks. https://wiki.onap.org/display/DW/VoLTE+Use+Case+Control+Loop Regards, Yuan 刘媛 / Liu Yuan 网络技术研究所 / Department of Network Technology

[onap-tsc] 答复: Re: ONAP VoLTE SDC call

Congratulations! Great progress for ONAP R1. @David: SO, SDNC, SDC team and WAN provider of Volte usecase(ZTE and CMCC) might have further work on defining of WAN service descriptor which is not as clear as NS descriptor. @Zhuoyao Huang: please prepare and arrange discussion with related

Re: [onap-tsc] [sdc][so][vfc][modeling]Concensus of SDC modeling on VoLTE use case

Hi Alex, Multiple projects feels that we need to decide which path we are going to take since there are two different IM candidates on the table Thanks DENG Hui From: Vul, Alex [mailto:alex@intel.com] Sent: Thursday, August 3, 2017 11:36 PM To: denghui (L) ;

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

I think we all agree on the goal. I do wonder though how much of what you see is an artifact of projects getting established and moving large pre existing code fragments as seed code into the correct location and how much is really new development which has started for this release and been