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] Official ONAP Architecture Slide Thanks, Jamil. I like the diagram. My question was Is there an intention / timeline for delivery of specifications with the level of details as e.g. in OpenStack (ETSI NFV, …)? Vladimir From: jamil.cha...@orange.com<mailto:jamil.cha...@orange.com> [mailto:jamil.cha...@orange.com] Sent: Tuesday, November 14, 2017 3:45 PM To: Vladimir Yanover (vyanover) <vyano...@cisco.com<mailto:vyano...@cisco.com>> Cc: Kenny Paul <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; Lisa Caywood <lcayw...@linuxfoundation.org<mailto:lcayw...@linuxfoundation.org>> Subject: Re: [onap-tsc] Official ONAP Architecture Slide Hi Vladimir The diagram is more a technical overview of onap components. Regards Jamil Le 14 nov. 2017 à 11:25, Vladimir Yanover (vyanover) <vyano...@cisco.com<mailto:vyano...@cisco.com>> a écrit : Hello, Kenny Thanks for sharing the Architecture diagram. I will appreciate if you help me with a question that I have on the ONAP architecture documentation. Consider potential products to be integrated into the ONAP system itself, interfacing to its components such as the Policy Framework and SDN-C Controller. For such integration, the published Architecture diagram lacks many details that normally are provided in the architecture specifications, such as 3GPP TS 23.501 or ETSI GS NFV 002. It’s functional description of every component, interfaces between the components, operations that can be executed over these interfaces etc. Examples from open source communities: the OpenStack’s Conceptual architecture https://docs.openstack.org/mitaka/install-guide-rdo/common/get_started_conceptual_architecture.html and Networking architecture at https://docs.openstack.org/security-guide/networking/architecture.html#<https://docs.openstack.org/security-guide/networking/architecture.html>. Here is my question: is there an intention / timeline for delivery of specifications with this level of details? Thanks Vladimir Yanover (Cisco) From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul Sent: Tuesday, November 14, 2017 3:13 AM To: onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>> Cc: Lisa Caywood <lcayw...@linuxfoundation.org<mailto:lcayw...@linuxfoundation.org>> Subject: Re: [onap-tsc] Official ONAP Architecture Slide Should be fixed. I’ve been using Confluence since 2010 and I just learned something new tonight :-} Also, I'm not sure how the same word can be misspelled 3 times in an email and not flagged as an error until I reply. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 On Nov 13, 2017, at 4:14 PM, 邓灵莉/Lingli Deng <denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>> wrote: Hi Kenny I am a raid that the link returns a error as Page not found. Lingli 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用 发件人: Kenny Paul<mailto:kp...@linuxfoundation.org> 发送时间: 2017年11月14日 8:04 收件人: onap-discuss<mailto:onap-discuss@lists.onap.org>; onap-tsc<mailto:onap-...@lists.onap.org> 抄送: Lisa Caywood<mailto:lcayw...@linuxfoundation.org> 主题: [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<mailto:kp...@linuxfoundation.org> 510.766.5945 _______________________________________________ ONAP-TSC mailing list onap-...@lists.onap.org<mailto:onap-...@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. _________________________________________________________________________________________________________________________ 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
