+1
I don't believe 9 commercial vNFs from three different vendors could
successfully deployed by VFC in voLTE service without compliance with ETSI
specification.
Yuan Yue
袁越 yuanyue
资深战略规划师 Senior Strategy Planner
技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System
Product
南京市雨花区软件大道50号中兴通讯3号楼1/F,Building 3, ZTE Nanjing R&D Center II, No.50, Software
Avenue,YuHua District,Nanjing,P.R.China 210012
T: +025 88013478
M: +86 13851446442
E: [email protected]
www.zte.com.cn
原始邮件
发件人： <[email protected]>;
收件人： <[email protected]>; <[email protected]>;
<[email protected]>;
抄送人： <[email protected]>; <[email protected]>;
日 期 ：2017年11月15日 18:02
主 题 ：[onap-tsc] 答复: Official ONAP Architecture Slide
Hi
I’d afraid that I can’t agree on it. The goal of VFC in ONAP is to
provide ETSI NFV align capability, so make ONAP integrated with ETSI NFV
complaint commercial solution in a more smooth way. I think the original
version is most suitable way to describe the difference between VFC and APPC.
Best regards
发件人: [email protected] [mailto:[email protected]]
代表 [email protected]
发送时间: 2017年11月14日 23:30
收件人: Sabater, Susana, Vodafone Spain; Lisa Caywood
抄送: onap-discuss; onap-tsc
主题: Re: [onap-tsc] Official ONAP Architecture Slide
Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil
De : Sabater, Susana, Vodafone Spain [mailto:[email protected]]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide
And maybe it is wise to avoid making any statement that “ONAP is functionally
aligned with ETSI NFV architecture”, since it will deeply confuse the audience
trying to see the alignment.
Cheers
/Susana
From: [email protected] [mailto:[email protected]]
On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN <[email protected]>
Cc: onap-discuss <[email protected]>; onap-tsc
<[email protected]>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide
Jamil, we can not spell out the names of all of the components on the slide;
there isn't room. It must be legible, including from a distance (eg in a public
presentation).
Chris can answer #2.
Thanks, Lisa
On Tue, Nov 14, 2017 at 7:14 AM, <[email protected]> wrote:
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 WindRiver ?
3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation
layer today. Replace it by Multi VIM/Cloud (official project name).
4- Replace SDN-C by SDN Controller, similar to Application Controller
5- VVP, VNF Requirements, Modelling, Testing & integration are not
mentioned in the architecture
a. Proposals:
i. To add Requirements and
Validation with VNF SDK.
ii. To add Modelling with CLAMP
iii. To add Test and Integration
with OOM
6- We need to avoid the abbreviations like AAF, OOF …
a. Proposal to replace:
i. SDC by Service Design Creation
ii. Clamp by Closed Loop Design
iii. DMaaP by Data Movement
iv. A&AI by Active & Available
Inventory
v. Holmes by Fault Correction
vi. DCAE by Data Collection
Analytics and Events
vii. AAF by Application Authorization
Framework
viii. CC SDK Common Controller SDK
ix. OOF by Optimization Framework
Regards
jamil
De : [email protected] [mailto:[email protected]]
De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide
As was pointed out in Paris there are too many variations of the Amsterdam
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2
In preparation for the release announcement here is what we are asking in order
of priority:
-If an archecture image is referecned in your official readthedocs
documentation, please use this image
-If an archecture image is referenced in your wiki pages, please add the URL
above to reference the the image.
-If an archecture image is referecned in a presentation slide deck, please
ensure you use this image.
I am intentionally NOT distributing it because that is how we ended up with so
many versions in the first place. :-)
Thanks!
Best Regards,
-kenny
Kenny Paul, Technical Program Manager
[email protected]
510.766.5945
_________________________________________________________________________________________________________________________
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.
--
______________
Lisa Caywood
Director of Ecosystem Development
OpenDaylight and ONAP Projects
[email protected]
+1 (408) 857-3642
Skype: RealLisaC
Twitter: @RealLisaC
_________________________________________________________________________________________________________________________
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._______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
