Dear Chris
Éric will participate to the architecture meeting
Regards
Jamil
Le 27 juil. 2017 à 20:22, Christopher Donley (Chris)
> a écrit :
Dear Jamil,
Thank you for sharing. I’d like to invite you to present your concerns
Hi Mazin
Are you proposing a new subcommittee to review the TSC voting procedure for the
election of subcommittee Chair ?
My preference will be to discuss first the irregularity of the use case
election during the next TSC meeting before to take any action.
Regards
Jamil
De :
+1
Regards
jamil
De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
De la part de Stephen Terrill
Envoyé : samedi 8 juillet 2017 23:23
À : t...@lists.onap.org
Cc : David Jorm; SPATSCHECK, OLIVER (OLIVER); HE Ruan IMT/OLS;
onap-sec...@lists.onap.org
Objet : [onap-tsc]
Hello
Thank you Phil for this analysis, we need also to analyse the election of
other subcommittee. I will ask during the TSC meeting to cancel this election
and to review the process.
Regards
Jamil
Cordialement
Jamil
Le 5 juil. 2017 à 23:44, Phil Robb
Hello
I can't understand how projects editing are managed, modifications are
introduced in SO project without agreement and not aligned with the what were
discussed and agreed last week.
Phil, Mazin cloud you clarify the situation ?
Regards
Jamil
Le 11 mai 2017 à 21:48,
Le 17 juin 2017 à 05:52, Phil Robb
> a écrit :
Hello ONAP TSC Members:
As we left it on the ONAP TSC call this week, please review and vote on the
vCPE Residential Broadband Use Case proposal for inclusion in Release-1 of the
ONAP
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
> a écrit :
+1 for virtual meetings
From:
-1 for physical F2F meeting in July
De : Lingli Deng [mailto:denglin...@chinamobile.com]
Envoyé : vendredi 16 juin 2017 10:25
À : aayush.bhatna...@ril.com; CHAWKI Jamil IMT/OLN; arul.na...@amdocs.com;
elhay.efr...@amdocs.com
Cc : onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Objet : RE:
Hello
I don’t remember that we have agreed to initiate a vote on this topic. As
mentioned by Mazin we have agreed to have in priority Heat but without
excluding OOM which I hope will be ready for a v2 of Rel-1.
Regards
Jamil
De : onap-tsc-boun...@lists.onap.org
Interesting presentations on ETSI NFV
https://nfvwiki.etsi.org/index.php?title=ETSI_NFV_Tutorial
_
Ce message et ses pieces jointes peuvent contenir des informations
Hello
To my knowledge we have agreed to integrate any project that will pass M4, the
gating is a kind of top priority project for Release Amsterdam.
Regards
Jamil
De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
De la part de eric.deb...@orange.com
Envoyé : vendredi
Hello Phil
I am interested to be part of a workgroup.
Best
Jamil
Le 14 déc. 2017 à 01:03, Phil Robb
> a écrit :
Hello ONAP TSC Members:
As documented in the ONAP Project Charter, the TSC is tasked with figuring out
how to populate
I agree, we don’t need to mention commercial cloud solution in our architecture
Regards
Jamil
Le 14 nov. 2017 à 14:06, Pasi Vaananen
> a écrit :
Are Azure & AMZ clouds really supported in Amsterdam as NFVI+VIM (or at all) ?
If not, then they
Hi Vladimir
The diagram is more a technical overview of onap components.
Regards
Jamil
Le 14 nov. 2017 à 11:25, Vladimir Yanover (vyanover)
> a écrit :
Hello, Kenny
Thanks for sharing the Architecture diagram.
I will appreciate if you help me with a
Hello Kenny
I have a question on the ETSI aligned of VFC module, to my knowledge the VFC
interfaces are not aligned with ETSI NFV.
I think we need to remove this term from VFC and to add that ONAP architecture
is Functionally aligned with ETSI NFV.
Regards
Jamil
De :
Hi Lisa
I understand but also we cannot keep a no meaning abbreviations...
We can have a list of abbreviation or a simplify name like:
· Clamp > Closed Loop
· AAF > Authorization
· OOF Optimization
Regards
Jamil
De : Lisa Caywood [mailto:lcayw...@linuxfoundation.org]
Hello Kenny
Additional comments and proposals on this figure:
1- Remove ETSI NFV alignment from VFC and to replace it by a general note
that 'ONAP is functionally aligned with ETSI NFV architecture'
2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and
not
Yes this is in the Scope of the Architecture subcommittee
https://wiki.onap.org/display/DW/Goals
De : Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Envoyé : mardi 14 novembre 2017 14:55
À : CHAWKI Jamil IMT/OLN
Cc : Kenny Paul; onap-discuss; onap-tsc; Lisa Caywood
Objet : RE: [onap-tsc]
Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil
De : Sabater, Susana, Vodafone Spain [mailto:susana.saba...@vodafone.com]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP
+1
And also a short summary of the meeting
Best
Jamil
De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
De la part de Alla Goldner
Envoyé : mardi 21 novembre 2017 18:32
À : Pasi Vaananen; Stephen Terrill; onap-...@lists.onap.org;
onap-tsc@lists.onap.org
Objet : Re:
+1
De : Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Envoyé : mercredi 15 novembre 2017 06:00
À : TALASILA, MANOOP (MANOOP); Kenny Paul; Lisa Caywood
Cc : Sabater, Susana, Vodafone Spain; CHAWKI Jamil IMT/OLN; onap-discuss;
onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture
+1 in addition Portal should not be part of the Design Time.
OOM need to be positioned on the right to avoid to be considered as on the top
of External API
Regards
Jamil
De : TALASILA, MANOOP (MANOOP) [mailto:talas...@research.att.com]
Envoyé : mercredi 15 novembre 2017 03:43
À : Kenny Paul;
Hi Maopeng
I understand that it is not easy to map ETSI to ONAP architecture. But I don’t
think by putting VFC aligned with ETSI NFV make any sense.
As we are in one project my preference is to mention that ONAP is a way to
implement ETSI NFV functionalities.
Regards
jamil
De :
Hello Team
I think having one representative and a mix 50/50 of vendors/operators is a big
opportunity for the adoption of ONAP by the Telco Industry.
Our position is to have the TSC election after the delivery of a
stable/deployable Release C and more Operators involvement in the community.
Hello
I agree with Steve that we need to select an option. Phil do you have a
proposal for selection?
Best
Jamil
Le 22 janv. 2018 à 23:45, Stephen Terrill
> a écrit :
Hi,
Originally there were three proposals put on the table,
Hi Phil
I am in favor with your proposal for #2
Best
Jamil
Le 11 janv. 2018 à 16:08, Phil Robb
> a écrit :
Hello ONAP TSC Members:
Now that ONAP is a part of the Linux Foundation Networking (LFN) Directed Fund,
we need to decide how
Hello Randa
+1 for your proposal
Regards
Jamil
Le 12 janv. 2018 à 00:58, MAHER, RANDA >
a écrit :
Dear TSC,
Please consider request below for Committer Promotion for APPC project.
https://wiki.onap.org/pages/viewpage.action?pageId=22251669
One of our
Good news Phill
Best
Jamil
Le 27 janv. 2018 à 06:48, Phil Robb
> a écrit :
Hello ONAP community:
Active developers and project leadership are strongly encouraged to participate
in the ONS event. Monday and Tuesday will be
Daer Maopeng
We have agreed in the architecture Subcommittee to evaluate the impact of the
RT Catalog on other technical modules (SO, APPC, VFC, SDNC …) .
My preference will be to wait the output of this evaluation before to present
this project at the TSC level.
Regards
Jamil
·
Thank You Mazin
I fully understand and support your concern to have 50% of Telecom Operators in
the TSC,
10 members (out of 15) have voted to postpone the election after Releace C (not
accepted as we need 12 to change the Charter).
I don’t understand Chirs and Steve motivation to have a TSC
30 matches
Mail list logo