Dovetail project update 3/27/2017

Dovetail user facing view A reviewer A vendor’s domain Use e.g. LF ID to login & check results e.g. https://cvp.opnfv.org (client) The external network with Https open A host or VM or container to run dovetail (server) Web server and DB hosted and administered by e.g. OPNFV or hired help. (A vendor can also do dry-runs by installing a local server. * May also add a local file dump for simplicity.) The internal network SUT

SUT (in Danube cycle) Products from vendors Not OPNFV release artifacts themselves Development tooling, such as CI/CD, is not part of the SUT. The vendors can bring up the SUT to a pre-Dovetail-test state in any way they choose. Dovetail will provide documentation to help to do so. The SUT consists of NFVI software, VIM software, and necessary hardware in one System Under Test. The hardware should follow Pharos guidelines. Vendors can use their own hardware, or third party or white box hardware to be tested as a whole. And if the combined whole passes the test suite, the CVP label applies to the software. The Danube cycle does not plan to test hardware-only systems.

Test scope draft Test scope draft in high level: Hardware assumed to be Pharos compliant Features Validation of common cloud environment requirements Openstack refstack/defcore integrated Capabilities required to provide consistent VNF lifecycle Networking features required to support carrier environment Resilience Ability for virtual infrastructure to detect and recover from failures – currently focused on control plane and hardware failures. Scalability Some level of scalability demanded by Pharos & resilience, but not tested quantitatively Security: not yet addressed Performance characterization: not included in this release

Info collected in the test result DB OPNFV test case example http://testresults.opnfv.org/test/api/v1/results?case=vping_ssh&last=1 OPNFV integrated refstack http://testresults.opnfv.org/test/api/v1/results?case=refstack_defcore&last=1 Explanatory information in documentation Web UI to be developed in LF infrastructure along with hosted server. Local report utility to be added to dovetail client CLI.

Test case requirements Open community brainstorm session completed and inputs collected and review completed. See the updated wiki: https://wiki.opnfv.org/display/dovetail/Dovetail+Test+Case+Requirements

Test case reviews Test case info worksheet template to help collect and organize the most relevant information: https://wiki.opnfv.org/pages/viewpage.action?pageId=10291560 Each test area needs community members to research and complete the worksheet Review each test area in Dovetail calls We are starting this process now… please join by proposing test cases and completing the required worksheet And add the resulting action items, if any, to JIRA

Working with upstream communities Openstack Refstack-Defcore integrated in Functest/Dovetail A collaborative relationship going forward Give feedback on existing test cases Possible to have rare exceptions that test cases may not be suitable for OPNFV Work on NFV extension test cases to refstack-defcore Consider other communities in Euphrates

Draft timetable Many people are still busy on finishing the Danube release. Test strategy still in draft form. Work items not finalized. Overall timeframe to target: ~Danube + 3 months Code freeze: ~end of May - June Announcement: June 12-16, OPNFV Summit, demo/tutorial Launch: possibly July ~ August Draft timetable & plan here https://wiki.opnfv.org/display/dovetail/Dovetail+Danube+Plan