Re: [onap-tsc] EUAG Survey

huawei] Leading Global ICT Innovations From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> [mailto:onap-tsc@lists.onap.org] On Behalf Of Haiby, Ranny (Nokia - US/San Jose USA) Sent: Tuesday, October 02, 2018 11:27 AM To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.or

Re: [onap-tsc] EUAG Survey

or our network service. We are currently making some progress towards this. Thanks Ramki From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> mailto:onap-tsc@lists.onap.org>> On Behalf Of Haiby, Ranny (Nokia - US/San Jose USA) Sent: Tuesday, October 2, 2018 8:48 AM To:

[onap-tsc] EUAG Survey

Hi, Following a discussion on the TSC weekly call two weeks ago I started creating a survey that will be used to solicit EUAG input to ONAP. With the help of several community members we now have a first draft of the survey available for review: https://wiki.onap.org/display/DW/EUAG+Survey

Re: [onap-tsc] Definition of Subcommittee Membership

Hi Phil, Your proposal to have a formal definition of subcommittee membership makes a lot of sense. One thing I was concerned about is discouraging community members from contributing to the subcommittee work just because they are not their company designated voting member. So I suggest to

Re: [onap-tsc] FYI on Ecomp 1806 code merge

Hi, I would like to share some feedback from my Nokia colleagues about “collateral damage” done by this merge. *For several weeks prior to the merge it was not possible to get code merge requests in SO approved due to the imminent code change. * As part of this merge, some tests created by the

Re: [onap-tsc] #lfn IMPORTANT- Proposed TSC Composition Language

+1 Alla raises important issues that are not covered by the current ONAP community document. Although I am “guilty” of voting for the current language, I am literally losing sleep lately with concerns over this hybrid meritocratic/appointed model we have created. I believe our intentions were

Re: [onap-tsc] Committer Promotion Request for [appc]

+1 Ranny. From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of MAHER, RANDA Sent: Thursday, January 11, 2018 3:58 PM To: onap-tsc@lists.onap.org Cc: onap-disc...@lists.onap.org Subject: [onap-tsc] Committer Promotion Request for [appc] Dear TSC, Please

Re: [onap-tsc] Planning for ONAP TSC Elections

+1 And will be glad to join the WG. Ranny. From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Wednesday, December 13, 2017 4:03 PM To: onap-tsc Subject: [onap-tsc] Planning for ONAP TSC Elections Hello ONAP TSC

Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release

Hi, Yes, I would be happy to further discuss this next week in Paris. Regards, Ranny. From: Yunxia Chen [mailto:helen.c...@huawei.com] Sent: Thursday, September 21, 2017 11:35 PM To: Haiby, Ranny (Nokia - US/San Jose USA) <ranny.ha...@nokia.com> Cc: onap-tsc <onap-tsc@lists.onap.or

Re: [onap-tsc] [tsc]Vote: ONAP Deployment Proposal for Amsterdam Release

Helen, While I don’t want to jeopardize the Amsterdam release by not voting for the Heat option, I am still concerned about the usability of the deployment. I have some colleagues who tried to deploy openECOMP with the Heat templates and just gave up due to complexity. As you can imagine, they

Re: [onap-tsc] More Help For Adding Committers

It seems like Confluence is a supported source for Bitergia (It is listed here under “supported tools”: https://www.bitergia.com/products/dashboards/) So it should be possible to collect stats like: * Wiki Page creations * Page edits * Comments * File uploads Ranny. From:

Re: [onap-tsc] R2 use cases planning

Alla – Thanks for bringing it up for discussion. Before making decisions on the use case content of R2, I believe we should have a better definition of the purpose of the use cases, and their selection criteria. I believe that once we have that nailed down, it will be easy to decide what goes

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

+1 Ranny. From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb Sent: Wednesday, August 2, 2017 2:49 PM To: onap-tsc Subject: [onap-tsc] Vote on Date & Location of Next ONAP Developer Face To Face Hello ONAP TSC Members:

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

Suggestion for encouraging proper behavior – Can the LF implement a code contribution statistics tool (something like OpenStack stackalytics) on the ONAP repos? That way we can easily track things like average LOC per commit for each project/repo, find anomalies and

Re: [onap-tsc] YOUR ACTION IS REQUIRED: A Project needs new repos for microservices

+1 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gildas Lanilis Sent: Thursday, July 6, 2017 3:27 PM To: 'onap-tsc@lists.onap.org' Subject: [onap-tsc] YOUR ACTION IS REQUIRED: A Project needs new repos for microservices

Re: [onap-tsc] TSC Meeting Minute Approvals

Jason Hunt; rajesh.gadi...@intel.com; Haiby, Ranny (Nokia - US/San Jose USA); jamil.cha...@orange.com; aayush.bhatna...@ril.com; Dhananjay Pavgi; Xinhui Li; susana.saba...@vodafone.com; meng.zhaoxi...@zte.com.cn Cc: onap-tsc Subject: TSC Meeting Minute Approvals TSC Members: As agreed upon a

Re: [onap-tsc] Corrective Action on Approved Project Proposals

+1 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul Sent: Thursday, June 29, 2017 12:13 PM To: onap-tsc Subject: [onap-tsc] Corrective Action on Approved Project Proposals TSC Members: The following are

[onap-tsc] ONAP virtual lab

Hi, A small group of community members discussed the feasibility of creating a fully virtual, cloud hosted, ONAP lab. Thanks for everyone who contributed. The initial findings are here: https://wiki.onap.org/display/DW/Virtual+lab You are welcome to review and comment. If you are too busy to

Re: [onap-tsc] Release Naming

Option 2 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Tuesday, May 16, 2017 11:23 AM To: Alla Goldner ; GILBERT, MAZIN E (MAZIN E) ; onap-tsc Subject:

Re: [onap-tsc] [onap-discuss] [modeling] TOSCA BPMN supportproposal at OASIS TOSCA WG

Just to chip in my perspective on this “Rome” discussion, It is not about what “works very well now” and what doesn’t. Both approaches may very well work now. The BPMN approach apparently worked well in Open-O and I can attest that in Nokia we successfully delivered working EPC and VoLTE

Re: [onap-tsc] Proposal: Architecture Subcommittee

Chris, I am having a hard time figuring out the difference between an architecture subcommittee member and a “plain” member of the community. Architectural discussions take place in the community on a regular basis and they are open to all. With the current definition of the subcommittee I

Re: [onap-tsc] [onap-discuss] [modeling] TOSCA BPMN support proposal at OASIS TOSCA WG

Huabing, I like your direction of giving concrete examples for possible implementation that you did in some other branch of this thread. Following that, could you please illustrate how the following scenario will be addressed with a BPMN workflow: Let say I am deploying an EPC P-GW, and in

[onap-tsc] ONAP Architecture Overview Slides

Great! Thanks for the quick response. Regards, Ranny. From: BEGWANI, VIMAL <vb1...@att.com> Sent: Wednesday, April 12, 2017 11:50:03 AM To: Haiby, Ranny (Nokia - US/San Jose USA); onap-tsc at lists.onap.org Subject: RE: [onap-tsc] ONAP Architecture Ov

[onap-tsc] ONAP Architecture Overview Slides

Thank you for sharing Lingli and Vimal. Slide 6 has the overlay callouts that hide some of the diagram. Could you please export another PDF version without the callouts? Or share the original PowerPoint slide deck with the animation? Thanks, Ranny. From: onap-tsc-bounces at lists.onap.org

[onap-tsc] DRAFT Technical Community Charter

Thanks Ed, Steve, Alla, Lingli, Phil, and Chris. I suggest adding another coordinator - a "usability coordinator". The inherent complexity of each of the merged projects, the complex task of the merge and a community led by engineers may result in severe usability issues. We may end up with