Hi Gildas, Tks for considering the “Matrix” we sent. My clarifications regarding your comments:
1. The goal of the matrix we built was not to highlight the consumer/provider relationship. Based on what currently specified in each project description we wanted to find the inconsistencies in how the project creator sees the interactions with other projects (row per project) versus what other projects thing about their interaction with this specific project (column per project). The green boxes indicate an existence of the record of such interaction as described in all the approved projects. 2. The idea behind the blue boxes was to indicate an existence of logical interaction but not necessarily requiring developing of an API. For instance VNF Requirement or Modeling have logical relation with other projects but do not require developing API’s in between. 3. The red box intent is to indicate the inconsistency I mentioned in (1). To our understanding this analysis is the primary goal of the matrix. 4. Thanks for spotting the fact that the two proposed projects (Network Function change management and External System Register) have not approved yet. BR Andrei From: Gildas Lanilis [mailto:[email protected]] Sent: Tuesday, June 20, 2017 3:11 AM To: Andrei Kojukhov <[email protected]> Cc: [email protected]; onap-tsc <[email protected]>; Alla Goldner <[email protected]>; Phil Robb <[email protected]>; Arul Nambi <[email protected]> Subject: RE: [onap-discuss] [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting Thanks Andrei for putting the deck together. It helps to move forward. It was my intention to build a similar table based on the dependencies input<https://wiki.onap.org/display/DW/Release+Planning+Template#ReleasePlanningTemplate-ONAPDependencies> for each and every project. I posted your table as a reference on wiki at https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ReleaseDependencies and started to build directly into the wiki the same table (so far with only approved projects). That should help into avoiding the question “what is the latest version?”. A couple of questions: 1) I was wondering how to read the dependency table. In other words who is the API provider and who is the API consumer? In the Release Planning Template<https://wiki.onap.org/display/DW/Release+Planning+Template#ReleasePlanningTemplate-APIIncomingDependencies>, I called it “API Incoming Dependencies” (provider) and “API Outgoing Dependencies” (consumer). Your clarification would help (my guess is that the projects in the column have dependencies on the projects in the row). Thanks to confirm. 2) Would you mind clarifying the blue boxes “Interact but no direct interface”? To some extend everything interact through a different level of connection in ONAP. 3) For the red boxes “Likely but not mentioned”. Would you mind explaining where it is not mentioned? May be we should wait until all projects have created their release plan. 4) Not sure what are the “Change Man”, “Ext Sys Reg” projects. To my knowledge, none have not been approved so far, and I do not see them in the list of “proposed project<https://wiki.onap.org/display/DW/Proposed+Projects>”. May be it is just a wording issue. It would help if you could provide a link. Thanks, Gildas ONAP Release Manager 1 415 238 6287 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andrei Kojukhov Sent: Monday, June 19, 2017 6:17 AM To: Alla Goldner; Phil Robb; Arul Nambi Cc: [email protected]<mailto:[email protected]>; onap-tsc Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting Alla, Phil, Please take an updated slide (attached) – I sent you an email twice by mistake. BR Andrei From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alla Goldner Sent: Monday, June 19, 2017 4:06 PM To: Phil Robb <[email protected]<mailto:[email protected]>>; Arul Nambi <[email protected]<mailto:[email protected]>> Cc: Elhay Efrat <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting Hi Phil, all, Given the huge number of approved projects and their complexity, from one side, and lack of well-defined interactions and interfaces between those projects/modules representing the projects, from the other side, I would say we may need a meeting to define those, to synchronize on those, to see if all needed interfaces are indeed defined etc. We’ve been trying to access the complexity internally and came up with the list of all potential interactions which will have to be developed, attached. The list may not be fully correct, I will be happy to upload it (just needs to know what would be the ideal placement for it) and invite the community to respond and introduce all required modifications. The list will have to be extended once we approve more projects. (Please note that Integration and Documentation interfaces with all projects, but there is no need to build interface, just to coordinate.) My development experience tells me such a mission can’t be achieved by project calls only, or even project-to-project calls, but requires a dedicated meeting, the sooner the better. My 2 cents ☺ Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Phil Robb Sent: Monday, June 19, 2017 11:47 AM To: Arul Nambi <[email protected]<mailto:[email protected]>> Cc: Elhay Efrat <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting Hi Arul: The problem with doing "both" is that if not enough people get in the room together physically, then for those that took the time, expense, and effort to get there they will not get much value from it. If there is critical mass that get together in the room, then those remote, and on the phone *never* get nearly as much out of it as those in the room. I would like to better understand what we would do at a group gathering, virtual or physical in late July. Can folks propose propose agenda topics so we can see what we would want to accomplish, and from that we can figure out the best format it? Thanks, Phil. On Wed, Jun 14, 2017 at 9:28 PM, Arul Nambi <[email protected]<mailto:[email protected]>> wrote: +1 why can we not have both? From: Elhay Efrat Sent: Wednesday, June 14, 2017 5:31 AM To: [email protected]<mailto:[email protected]>; Arul Nambi <[email protected]<mailto:[email protected]>> Cc: Dhananjay Pavgi <[email protected]<mailto:[email protected]>>; Gadiyar, Rajesh <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: RE: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting Why not always add vitrual ☺ ? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Wednesday, June 14, 2017 10:00 AM To: Arul Nambi <[email protected]<mailto:[email protected]>> Cc: Elhay Efrat <[email protected]<mailto:[email protected]>>; Dhananjay Pavgi <[email protected]<mailto:[email protected]>>; Gadiyar, Rajesh <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting My understanding the agreement was to have a virtual meeting in July and a physical one in September Best Jamil Le 14 juin 2017 à 01:11, Arul Nambi <[email protected]<mailto:[email protected]>> a écrit : +1 for virtual meetings From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Elhay Efrat Sent: Tuesday, June 13, 2017 1:41 AM To: Dhananjay Pavgi <[email protected]<mailto:[email protected]>>; Gadiyar, Rajesh <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting Good , can we do also F2F over webex , skype … something ☺? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dhananjay Pavgi Sent: Tuesday, June 13, 2017 6:45 AM To: Gadiyar, Rajesh <[email protected]<mailto:[email protected]>>; GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers Face-to-Face Meeting +1 thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264<tel:+91%2098220%2022264> <image001.png> <image002.jpg> www.techmahindra.com<http://www.techmahindra.com/> Platinum Member. Visit : http://www.onap.org<http://www.onap.org/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gadiyar, Rajesh Sent: Tuesday, June 13, 2017 9:12 AM To: GILBERT, MAZIN E (MAZIN E) <[email protected]<mailto:[email protected]>>; Kenny Paul <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting +1 Good idea ☺ From: <[email protected]<mailto:[email protected]>> on behalf of "GILBERT, MAZIN E (MAZIN E)" <[email protected]<mailto:[email protected]>> Date: Monday, June 12, 2017 at 2:01 PM To: Kenny Paul <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, onap-tsc <[email protected]<mailto:[email protected]>> Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting I was not present for this discussion. We need to have a meeting around the 3rd week of July to go through project by project progress. Phil and I discussed a virtual meeting since folks will be too busy to travel, and some may not be able to. Would like to get a sense from the TSC community if this is appropriate and more convenient while voting for dates. thanks Mazin On Jun 12, 2017, at 1:08 PM, Kenny Paul <[email protected]<mailto:[email protected]>> wrote: Please respond to the doodle poll below no later than: Thurs. 01:00 PM UTC Thurs. 09:00 PM China Thurs: 09:00 AM Eastern Thurs: 06:00 AM Pacific https://doodle.com/poll/7zufivqebtnvrhdt<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_7zufivqebtnvrhdt&d=DwMCAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM&s=W2yLAyRSo72NJJvcQibUZP8thCi407eXKwPoV15Q3N8&e=> Thank You. Best Regards, -kenny Kenny Paul, Technical Program Manager [email protected]<mailto:[email protected]> 510.766.5945<tel:(510)%20766-5945> _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IKSC5mg8GeOiSar1dax3GQ&m=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM&s=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E&e= ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-tsc _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-tsc -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
