Hi Wenjing Yes its new thread.
Re. EUAG I am aware of the Pain Points Wiki page however it's not clear to me how this is feeding initial scope of CVP. The CVP page https://wiki.opnfv.org/pages/viewpage.action?pageId=11700688 does not have any feedback yet from what I can see ... any idea on how we can facilitate getting some feedback? I take your point about complexity of those applications and common patterns ... but what was the suggestion for an alternative "use-case approach"? I assumed it meant using specific use-models e.g. VOLTE to derive platform capabilities that we should include in scope of tests ... this also seems to be what you are saying but I don't think that analysis has been done in Dovetail yet, correct? /Trevor From: Wenjing Chu [mailto:wenjing....@huawei.com] Sent: Tuesday, July 11, 2017 11:16 AM To: Cooper, Trevor <trevor.coo...@intel.com>; opnfv-tech-discuss@lists.opnfv.org Subject: RE: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube Release Hi Trevor I'm not sure if your email is a follow-up of a previous message or not. I couldn't find another email so I'm assuming this is a new thread. Let me know if I'm mistaken. First of all, we did receive detailed feedbacks from EUAG as far back as Feb and most recently during the Summit in June. So additional feedbacks are welcome but we are not waiting/gating on anything from EUAG at this time. As part of action items during the Summit when CVP was discussed with the EUAG, we agreed to set up a wiki in EUAG for tracking additional feedbacks. It's under the EUAG wiki page and just follow the link for cvp feedbacks. I personally use the term "use case approach" in the context of CVP to mean that for a given SUT, we identify common use patterns, and develop automated test cases to exercise such patterns. I agree with Bryan's comment in yesterday's c&c call that applications like VOLTE and vCPE are too complex for our purposes - it won't be easy to separate issues of the application's implementation from the issues of SUT (the latter is what we wish to identify). A better approach is abstract the common design patterns out of a complex application, and develop test cases around those common patterns that have more general applicability to all similar applications. For example, vPING is a common pattern of "2 virtual machines with virtual network connectivity between them". This can be seen as the simplest use pattern. Another use pattern may be multiple virtual machines load balancing to provide a common service. vCPE, if narrowly defined, can be a pattern of secure gateway between two network domains. I personally think this space between simplicity of a vPING to a well understood gateway function may be the most productive area we can focus on. Many of OPNFV projects can contribute these use pattern test cases, by abstracting and by clarifying what the test intention is, in some cases. This is a great area of 'low hanging fruit' during the E release cycle. Regards Wenjing From: opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Cooper, Trevor Sent: Monday, July 10, 2017 4:50 PM To: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: [opnfv-tech-discuss] [dovetail] Use-cases for Dovetail Danube Release My notes on the "use-case approach" with VOLTE and vCPE ... capture that EUAG supports the approach and will get back with some suggestions. Are we still waiting on the EUAG to get back? If yes what are our expectations for receiving guidance? Can we try to define the "use-case approach" better ... e.g. meld this with our current approach to say identify gaps/deficiencies with the test cases? What approach should we take for identifying and organizing VOLTE and vCPE capabilities and their relevant test-cases? /Trevor
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
