Dovetail & CVP Tutorial/Demo Eddie Arrage Email: eddie.arrage@huawei.com

Agenda Beta Feedback Dovetail Test Environment Environment Setup Demo CVP Workflow Comments/Questions

Beta Feedback How many users have begun testing? Haven’t started yet Have the SUT & test tools installed Running tests Finished

Dovetail Test Environment Install Dovetail and other underlying docker containers (assume online) Pull tar.gz results from test host Upload results to CVP Portal

Environment Setup Prepare Environment Download Images & Start Dovetail install Docker-CE, Python set env vars and edit config files Download Images & Start Dovetail Cirros/Ubuntu test image files online: pull Dovetail docker image start Dovetail docker image setup Dovetail environment Run & Interpret Tests Locally all or subset debug logs Upload Results to CVP Portal Login using Linux Foundation or OS ID

Step 1: Prepare Environment – Package Install Install Python 2.7.6 Install Docker CE >= 17.03

Step 1: Prepare Environment – Main Config Exports including SUT credentials HTTPS should be enabled in SUT Workaround: Comment out these lines Key line to populate (identity service) Other services can be gleaned

Step 1: Prepare Environment – Other Config Files pre_config/tempest_conf.yaml (required for mandatory in beta) pre_config/pod.yaml (required for HA) pre_config/host.yaml (optional) Use this config at minimum for now Hostname -> IP mappings Compute Service (SUT) Test Host Image Service (SUT) ex. compass Samples are auto-generated after first test attempt on test host

Step 2: Download Images & Start Dovetail Assumption: Online $ sudo wget -nc http://artifacts.opnfv.org/sdnvpn/ubuntu-16.04-server-cloudimg-amd64-disk1.img -P ${DOVETAIL_HOME}/pre_config $ sudo wget -nc http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img -P ${DOVETAIL_HOME}/pre_config sudo docker pull opnfv/dovetail:cvp.0.7.0 cvp.0.7.0 Into Dovetail container shell

Step 2: Download Images & Start Dovetail If not planning to submit results to CVP portal, the steps below are not required port 27017 (db) and port 8000 (testapi) are default, export new values if there are conflicts on test host When planning to upload results to CVP, complete the steps below In Dovetail docker before running tests

Step 3: Run & Interpret Tests Locally Execute all or subset of tests with: conf/dovetail_conf.yml (dovetail docker) osinterop: VIM Compute VIM Image VIM Network VIM Identity VIM Volume mandatory: osinterop vPing HA --testsuite options --testarea options

Step 3: Run & Interpret Tests Locally Store results to tar.gz for upload to CVP portal: Add the --report option IP of test host Result files stored in DOVETAIL_HOME (Test Host) Log files stored in results directory

Step 3: Run & Interpret Tests Locally Log files stored on test host OS for Dovetail container Log files are in ‘results’ directory Results directory overwritten each time test is executed from Dovetail container Different directories and logs are output for each testarea Ex. osinterop

Step 3: Run & Interpret Tests Locally - Logs Ubiquitous logs: dovetail.log, functest.log osinterop – refstack osinterop_logs/dovetail.osinterop.tc001.log HA – yardstick dovetail.ha.tc001.out - dovetail.ha.tc008.out IPv6 – ipv6_logs/dovetail.ipv6.tc001.log - dovetail.ipv6.tc025.log Haven’t run sdnvpn, tempest, etc.

Step 4 - Upload Results to CVP Portal Main CVP Portal: https://cvp.opnfv.org Use existing user credentials to login: Primary: Linux Foundation, Openstack Others: Google, GitHub, Facebook (creates Linux Foundation login) New users can register at: https://identity.linuxfoundation.org https://www.openstack.org/join/register others

Step 4 - Upload Results to CVP Portal – Tester Role https://cvp.opnfv.org/#/user_results Click here to begin Share results Must know user login ID (Linux Foundation or OpenStack) Testers see options of ‘share with’ and ‘submit for review’ in Operation dropdown

Step 4 - Upload Results to CVP Portal – Review Results Click Test ID to view summary results Click logs to drill into failed results

CVP Workflow Step 1: Applying – PDF/CVP Portal Step 2: Testing (beta) https://cvp.opnfv.org/#/application Step 2: Testing (beta) https://wiki.opnfv.org/display/dovetail/Dovetail+Beta Step 3: Submitting Test Results https://cvp.opnfv.org/#/user_results Step 4: CVP Review Step 5: Grant of Use of Logo

CVP Workflow – Application Form – Administrator Role https://cvp.opnfv.org/#/application Administrator is allowed to submit application on behalf of company Submit to email: cvp@opnfv.org

CVP Workflow – Reviewer Role Reviewers see additional options for ‘approve/not approve’ under Operation dropdown

Beta Guidance Planning couple of revisions in Beta - CVP portal & Dovetail Encourage Beta testers to provide feedback Please send emails or file JIRA tickets with issues or questions

Thank You… www.opnfv.org wiki.opnfv.org

Appendix

CVP FAQ Why does the user guide outline ‘testsuite’ option argument in ‘dovetail run’ command that does not work? Convention ‘CVP_1_0_0’ for ‘testsuite’, where versioning represents ‘<major>_<minor>_<patch>’ will be adopted in future releases Use ‘proposed_tests’ during beta for ‘testsuite’ What image format must the SUT compute nodes support? Images are submitted as qcow2 so compute service must support this format Where are the test results stored? Results are gleaned from logs output from the underlying tools (functest, yardstick, refstack…) Look under the DOVETAIL_HOME/results directory on the test host for all the logs Does direct result upload from test host to CVP portal work? No, the user must first obtain the tar.gz file from test host and upload through the CVP portal

Docker CE Install for Ubuntu Source: https://docs.docker.com/engine/installation/linux/docker-ce/ubuntu/#install-using-the-repository

Dovetail CLI Useful Dovetail commands dovetail --version dovetail list dovetail show <test_case_name> https://wiki.opnfv.org/display/dovetail/Dovetail+Command+Line

Functest Log results/functest.log – SUT connectivity

Functest Log results/functest.log – Create objects in SUT

Functest Log results/functest.log – Post test clean objects