Dear Chris Thank you for your work and the presentation, we can say that this is a first step but we have not agreed on the architecture mentioned in your slide as Vimal presented another architecture (consigned by AT&T, Amdocs and Orange). Regards Jamil
De : [email protected] [mailto:[email protected]] De la part de Christopher Donley (Chris) Envoyé : jeudi 20 juillet 2017 22:05 À : [email protected]; [email protected] Cc : [email protected] Objet : [onap-tsc] Architecture Progress Dear ONAP Technical Community, I'd like to update you on progress from the Architecture Committee. * For Amsterdam, we agreed to use the current architecture, as discussed since ONS. This is to reduce risk of late changes to the project teams, who have built their plans based on the current baseline. * Longer-term, starting with Release 2, we reached consensus on an approach to resolve the APP-C/VF-C challenge. We are developing a three-layer orchestrator/controller functional architecture, with service orchestration/resource orchestration/controllers. Note that this functional architecture does not imply a project structure. Between now and the beginning of the R2 planning cycle, the team will drill down to the next level of detail on interfaces and project alignment, and then the projects will map code into the architecture to guide R2 plans. Cross-project discussions have already begun, and will continue over the coming weeks. Meeting logistics will be sent to the ONAP-discuss email list for those who are interested in participating. I have attached a set of diagrams that we reviewed in the Architecture Committee to illustrate both the R1 and R2 architecture. Note that in the R2 slide, since we are focused on the functional architecture and not the projects, we removed some of the boxes listing projects that support ONAP, but don't provide interfaces or data flows through the system. For those interested in more detail, we will discuss this during the developer meeting next week. Chris _________________________________________________________________________________________________________________________ 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 [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
