Hi Jamil
From the VFC project coming into ONAP, VFC focus on ETSI NFV implimention,
which is well-known in the community.
In R1 arch, VFC marked with ETSI NFV is no problem, which can make the
reader more clear about the main-contribution project.
Because VFC as one project in ONAP, so say ONAP implement ETSI NFV, it is
OK as well. But the mapping pre-shared really confuses the reader.
As I know ONAP scope is more the ETSI NFV, also SDN domain and service
domain.
BR
Maopeng
原始邮件
发件人: <jamil.cha...@orange.com>;
收件人:张茂鹏10030173; <christopher.don...@huawei.com>;
抄送人: <kp...@linuxfoundation.org>; <onap-discuss@lists.onap.org>;
<ajoship...@linuxfoundation.org>; <lcayw...@linuxfoundation.org>;
<onap-...@lists.onap.org>;
日 期 :2017年11月15日 23:47
主 题 :RE: RE: Re: [onap-discuss] [onap-tsc] Official ONAP ArchitectureSlide
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 : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Envoyé : mercredi 15 novembre 2017 08:54
À : CHAWKI Jamil IMT/OLN; christopher.don...@huawei.com
Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
Objet : 答复: RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide
Hi Jamil
As the reader, It will confus me about the mapping method. It does not
make sense.
About the interfaces, I have explained in the another email.
VFC mainly focus on the NSLCM and VNFLCM, which mainly is align to the ETSI
NFV LCM related interfaces.
VFC also provides the driver to adaptor more vendor VNFM to do the
integration.
BR
Maopeng
原始邮件
发件人: <jamil.cha...@orange.com>;
收件人:张茂鹏10030173;
抄送人: <kp...@linuxfoundation.org>; <onap-discuss@lists.onap.org>;
日 期 :2017年11月14日 19:54
主 题 :RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide
Hi Maopeng
In slide 9 you have a first mapping of ONAP architecture to ETSI NFV one.
For APPC stream NFVO is distributed between SO and DCAE. The VNFM is also
distributed in SO, APPC and DCAE.
Regards
Jamil
De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Envoyé : mardi 14 novembre 2017 11:44
À : CHAWKI Jamil IMT/OLN
Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
Objet : 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide
Hi jamil
One quick question:
How is the ONAP architecture Functionally aligned with ETSI NFV? Which
components are NFVO and VNFM in the ONAP aligned with ETSI NFV?
Thanks
BR
Maopeng
原始邮件
发件人: <jamil.cha...@orange.com>;
收件人: <kp...@linuxfoundation.org>; <onap-discuss@lists.onap.org>;
<onap-...@lists.onap.org>; <ajoship...@linuxfoundation.org>;
<lcayw...@linuxfoundation.org>;
日 期 :2017年11月14日 17:43
主 题 :Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide
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 : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org]
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
kp...@linuxfoundation.org
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.
_________________________________________________________________________________________________________________________
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.
_________________________________________________________________________________________________________________________
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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss