Alla, Phil, Gildas,
Thank you for the project reference – this is very useful. We need as many
views of the new system as possible (architectural, deployment, flow(s) and
connectivity for one). This cross reference graph is a good place to start to
break out/follow all dependency types starting with (compile-time (this can be
derived in jenkins), rest based, (non-rest DB/schema based), deploy-time
dependency, runtime health-check dependency, design-time …..). For example
when following a UC flow we usually work bottom up from rest/db calls but a top
level graph like this slide is extremely useful when identifying critical
coverage points/excluding flow sinks - while the grid is versioned/maintained.
Maybe a good place will be in the approved projects page – beside the
existing project reference
https://wiki.onap.org/display/DW/Approved+Projects
thank you
/michael
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Monday, June 19, 2017 10:33
To: Alla Goldner <alla.gold...@amdocs.com>; Gildas Lanilis
<gildas.lani...@huawei.com>
Cc: onap-disc...@lists.onap.org; onap-tsc <onap-tsc@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers
Face-to-Face Meeting
Hi Alla:
Yea, that's a somewhat scary chart. Thanks to you and your team for putting it
together. It will be a great cross reference for Gildas as we get initial
project plans that include their cross-project dependencies.
Gildas, is there somewhere you would like to keep this diagram for reference?
Best,
Phil.
On Mon, Jun 19, 2017 at 9:06 PM, Alla Goldner
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> wrote:
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:image001.png@01D2E8E9.F2F01510]
From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>
[mailto:onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>]
On Behalf Of Phil Robb
Sent: Monday, June 19, 2017 11:47 AM
To: Arul Nambi <arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>>
Cc: Elhay Efrat <elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>>;
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
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
<arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>> wrote:
+1 why can we not have both?
From: Elhay Efrat
Sent: Wednesday, June 14, 2017 5:31 AM
To: jamil.cha...@orange.com<mailto:jamil.cha...@orange.com>; Arul Nambi
<arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>>
Cc: Dhananjay Pavgi
<dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>>; Gadiyar,
Rajesh <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; GILBERT,
MAZIN E (MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>;
Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>;
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-tsc] [onap-discuss] Tentative July ONAP Developers
Face-to-Face Meeting
Why not always add vitrual ☺ ?
From: jamil.cha...@orange.com<mailto:jamil.cha...@orange.com>
[mailto:jamil.cha...@orange.com]
Sent: Wednesday, June 14, 2017 10:00 AM
To: Arul Nambi <arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>>
Cc: Elhay Efrat <elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>>;
Dhananjay Pavgi
<dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>>; Gadiyar,
Rajesh <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; GILBERT,
MAZIN E (MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>;
Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>;
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
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
<arul.na...@amdocs.com<mailto:arul.na...@amdocs.com>> a écrit :
+1 for virtual meetings
From:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Tuesday, June 13, 2017 1:41 AM
To: Dhananjay Pavgi
<dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>>; Gadiyar,
Rajesh <rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; GILBERT,
MAZIN E (MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>;
Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
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:
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi
Sent: Tuesday, June 13, 2017 6:45 AM
To: Gadiyar, Rajesh
<rajesh.gadi...@intel.com<mailto:rajesh.gadi...@intel.com>>; GILBERT, MAZIN E
(MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>; Kenny Paul
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
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: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh
Sent: Tuesday, June 13, 2017 9:12 AM
To: GILBERT, MAZIN E (MAZIN E)
<ma...@research.att.com<mailto:ma...@research.att.com>>; Kenny Paul
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers
Face-to-Face Meeting
+1 Good idea ☺
From: <onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>>
on behalf of "GILBERT, MAZIN E (MAZIN E)"
<ma...@research.att.com<mailto:ma...@research.att.com>>
Date: Monday, June 12, 2017 at 2:01 PM
To: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>
Cc: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>"
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>, onap-tsc
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
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
<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> 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
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945<tel:(510)%20766-5945>
_______________________________________________
onap-discuss mailing list
onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>
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
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
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
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
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<tel:(970)%20229-5949>
(M) 970-420-4292<tel:(970)%20420-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
--
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
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc
