Jamil, As far as I know, being able to utilize public cloud (Azure/AWS/etc) compute resources is an ONAP requirement. The question is to what extent our architecture diagrams should represent the reality of individual releases vs being more release agnostic and future looking?
Regards, Alex Vul Intel Corporation From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of jamil.cha...@orange.com Sent: Tuesday, November 14, 2017 5:17 AM To: Pasi Vaananen <pvaan...@redhat.com>; onap-tsc@lists.onap.org Subject: Re: [onap-tsc] Official ONAP Architecture Slide I agree, we don't need to mention commercial cloud solution in our architecture Regards Jamil Le 14 nov. 2017 à 14:06, Pasi Vaananen <pvaan...@redhat.com<mailto:pvaan...@redhat.com>> a écrit : Are Azure & AMZ clouds really supported in Amsterdam as NFVI+VIM (or at all) ? If not, then they should not be in this "official" picture. Pasi On 11/13/2017 07:03 PM, Kenny Paul wrote: 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-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc _______________________________________________ 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.
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
