Hi Nati,
I agree on the point you mentioned in general about the way open source systems have to work w.r.t the commercial licenses and enterprise editions. The point which we are trying to discuss here is not to be a part of the ONAP release but enable the experts handle issues reported in a quick turn around time. This is one of the short term solutions that we had thought of adapting to overcome the current situation, where most of the runtime issues are reported first on SO side. I discussed on this in yesterday's SO weekly meeting as one of the options, but does not limit us from trying the other alternatives. We have so far found 3 ways to tackle the current situation on the long term and are open for other options too that are feasible within the current infrastructure not making our lives more tougher. Hence, request all to kindly provide your suggestions. Best Regards, Seshu ****************************************************************************************** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained here in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this email in error, please notify the sender by phone or email immediately and delete it! ***************************************************************************************** ________________________________ From: Nati Shalom [[email protected]] Sent: Thursday, October 26, 2017 2:49 AM To: Yunxia Chen Cc: Seshu m; onap-tsc; [email protected] Subject: Re: [onap-tsc] Issue with Camunda cockpit license Seshu I think that this is the wrong direction to go. In general we need to make sure that ONAP is not dependent on such third party tools that are blocking developers features and debugging tools which really make the tools useless in the broader community context. Instead of buying license we should simply demand that those features will be available to to the community or start looking for alternatives. OpenSource that are monetizing in those area's are not really open IMO. Nati S. On Tue, Oct 24, 2017 at 6:56 PM Yunxia Chen <[email protected]<mailto:[email protected]>> wrote: I am second on this one. While we are doing integration testing, Rob from AT&T has to export those data, and come back to AT&T to check for it. The Enterprise edition license could definitely help speed up the process. Regards, Helen Chen From: <[email protected]<mailto:[email protected]>> on behalf of Seshu m <[email protected]<mailto:[email protected]>> Date: Tuesday, October 24, 2017 at 7:28 AM To: onap-tsc <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [onap-tsc] Issue with Camunda cockpit license Dear TSC, Currently SO team is fore-seeing risks on identification and debugging the critical issues reported and like to seek help from TSC. The workflow in the SO uses BPMN and groovy scripts and Camunda cockpit tool used for purpose of debugging the state of the BPMN flows. The issue we have right now is Camunda Cockpit features we are looking for are only available with the Enterprise edition license (and this is currently available with the ATT). And it would be great if we could leverage similar license for SO community , while I reached out to Camunda.org to get the quote on this and waiting for their response. Please let me know your inputs and I like to discuss this more on up-coming TSC meeting. ________________________________ Best regards Seshu Kumar M Huawei Technologies India Pvt, Ltd. ________________________________ 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-tsc
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
