Hi Tapio, I think there are some basic artifacts we can produce that are “relatively easy” to provide and can help all the extended aspects of this type of work. (Excuse the use of the word “Architecture” it comes from my previous RUP brainwashing. ;) 1) More detailed software reference architecture – can we identify key interfaces etc? 2) Runtime architecture – how can we represent the target of OPNFV when it’s up and running? 3) Deployment architecture – where and how is OPNFV deployed and which features matter where?
These don’t need to be at the Nth degree of detail, but having something representative of our solutions that can mapp across these domains would I think help provide clarity where today we don’t have a clear message/position. / Chris On 2016-10-20, 14:43, "Tallgren, Tapio (Nokia - FI/Espoo)" <[email protected] on behalf of [email protected]> wrote: Hi all, Here are some slides as a basis for discussion today. -Tapio _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
