Hi, As the TSC were reviewing every project for the M1 Release Planning, I created a dependency graph based on the data provided (API Incoming dependencies). This Graphiz graph is currently available in wiki at https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-APIDependencies . My plan is to upload in Gerrit the source code that helped creating the graph.
Hope this helps. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: Kanagaraj Manickam Sent: Friday, July 07, 2017 6:00 AM To: 赵化冰; onap-tsc@lists.onap.org; Phil Robb; Kenny Paul; wangchen...@chinamobile.com; dtimo...@att.com; Yunxia Chen; zhao.huab...@zte.com.cn; denglin...@chinamobile.com; pdrag...@research.att.com; denghu...@hotmail.com; talas...@research.att.com; Ram Koya; Seshu m; am8...@att.com; Casey Cain; lxin...@vmware.com; jf2...@att.com; stephen.terr...@ericsson.com; ml6...@intl.att.com; mp...@amdocs.com; sa...@research.att.com; l...@research.att.com; gg2...@att.com; gn4...@intl.att.com; fu.guangr...@zte.com.cn; denghui (L); david.sauvag...@bell.ca; sw3...@att.com; rx1...@att.com; shen...@chinamobile.com; ah0...@intl.att.com; Gildas Lanilis; es4...@att.com Cc: Eman Gil Subject: RE: [onap-tsc][ptls] proposed topic for the next week's PTL meeting One more topic: As part of M1 review, every project has listed the dependencies and I feel it will be very helpful if we could bring them together into one wiki and and draw a dependency graph and get it reviewed/accepted by all of us. Shall we have this topic as part of PTL meeting on Monday (10th) ? Thanks Kanagaraj M *************************************************************************************** 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！************************************************************************************** *************************************************************************************** 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! *************************************************************************************** From: 赵化冰 [mailto:zhaohuab...@gmail.com] Sent: Friday, July 07, 2017 12:32 PM To: onap-tsc@lists.onap.org; Phil Robb; Kenny Paul; wangchen...@chinamobile.com; dtimo...@att.com; Yunxia Chen; zhao.huab...@zte.com.cn; denglin...@chinamobile.com; pdrag...@research.att.com; denghu...@hotmail.com; talas...@research.att.com; Ram Koya; Seshu m; am8...@att.com; Casey Cain; lxin...@vmware.com; jf2...@att.com; stephen.terr...@ericsson.com; ml6...@intl.att.com; mp...@amdocs.com; sa...@research.att.com; l...@research.att.com; gg2...@att.com; Kanagaraj Manickam; gn4...@intl.att.com; fu.guangr...@zte.com.cn; denghui (L); david.sauvag...@bell.ca; sw3...@att.com; rx1...@att.com; shen...@chinamobile.com; ah0...@intl.att.com; Gildas Lanilis; es4...@att.com Cc: Eman Gil Subject: [onap-tsc][ptls] proposed topic for the next week's PTL meeting Dear PTLs, Maybe we could discuss this topic at the next week's PTL meeting. It's important and covers almost all the projects which will produce APIs. https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP Thanks, Huabing ---------- Forwarded message --------- Cc: <onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>> Hi Pam, After taking a look at the other best practices on this page. I realized that this is more like a specification than best practices because we'd like to enforce them to all the ONAP components. I moved this page to https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP Agree that some of the projects may not redesign the existing API for back-compatible reason, We can maintain the old version while designing the new version in parallel. It's possible that both the old and new version can be provided to the ONAP clients. Thanks, Huabing Original Mail Sender: <pdrag...@research.att.com<mailto:pdrag...@research.att.com>>; To: zhaohuabing10201488; <onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>; Date: 2017/06/22 20:09 Subject: Re: [onap-discuss] RESTful API Design Best Practices for ONAPMicroservices Huabing, Thanks, I agree and feel this is very valuable. There is no formal best practices for RESTful API, albeit a few websites that do a fairly good job at making suggestions. I think this detailed information should probably be in the section located here: https://wiki.onap.org/display/DW/Developer+Best+Practices Gildas has been including such details as part of his presentations, and its part of the checklist template. We would perhaps also need to be aware for R1 that some projects may not be able to re-design quite yet. They may have to support their current API version until an appropriate time to deprecate it in lieu of new API conforming to standards. Thanks, Pam From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>" <zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>> Date: Thursday, June 22, 2017 at 7:14 AM To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" <onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>> Subject: [onap-discuss] RESTful API Design Best Practices for ONAP Microservices Dear ONAPer, Most of the projects have already been approved in Beijing meeting or will be approved in this week's TSC meeting, we're starting the development phase of release 1 right now. I went through the API documents of a bunch of existing projects, it seems to me that there's no consistent approach for Restful API design and some of the APIs are not very appropriate. So I‘d like to suggest that we could figure out a unified approach across ONAP projects for the Restful API design before jumping into the coding job. I have worked out a draft as the start point for discussion on this wiki page : https://wiki.onap.org/display/DW/RESTful+API+Design+Best+Practices<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_RESTful-2BAPI-2BDesign-2BBest-2BPractices&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=0YNbxUNtVvCKpTNvgW3_BNoCLCj_MRe742y6dx4OBmU&s=_ZowHTJvm1zMQejvK18VIV9y5yd9QptiXikmoUw-5P4&e=> I hope we could discuss in the community and reach consensus in one or two weeks. Then I'd like to propose to TSC using it as a guideline for all the projects. What do you think about it? Please feel free to share your idea in the comments of the wiki page so we can improve this draft quickly. Thanks and Regards, Huabing _______________________________________________ onap-discuss mailing list onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-discuss
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
