From 1502753c041ec7179260890c8b2c41305fc91378 Mon Sep 17 00:00:00 2001 From: "zhifeng.jiang" Date: Thu, 2 Jun 2016 20:10:25 +0800 Subject: Add zte-pod1 test cases and include proxy in playbooks. JIRA:QTIP-75 Change-Id: I20cd348c292db9f2d7478d46183229544a604bbb Signed-off-by: zhifeng.jiang --- test_cases/zte-pod1/compute/dhrystone_bm.yaml | 5 ++- test_cases/zte-pod1/compute/dhrystone_vm.yaml | 50 ++++++++++++++++++++++++ test_cases/zte-pod1/compute/dpi_bm.yaml | 40 +++++++++++++++++++ test_cases/zte-pod1/compute/dpi_vm.yaml | 40 +++++++++++++++++++ test_cases/zte-pod1/compute/ramspeed_bm.yaml | 40 +++++++++++++++++++ test_cases/zte-pod1/compute/ramspeed_vm.yaml | 50 ++++++++++++++++++++++++ test_cases/zte-pod1/compute/ssl_bm.yaml | 36 ++++++++++++++++++ test_cases/zte-pod1/compute/ssl_vm.yaml | 40 +++++++++++++++++++ test_cases/zte-pod1/compute/whetstone_bm.yaml | 38 ++++++++++++++++++ test_cases/zte-pod1/compute/whetstone_vm.yaml | 48 +++++++++++++++++++++++ test_cases/zte-pod1/network/iperf_bm.yaml | 55 +++++++++++++++++++++++++++ test_cases/zte-pod1/network/iperf_vm.yaml | 48 +++++++++++++++++++++++ test_cases/zte-pod1/network/iperf_vm_2.yaml | 49 ++++++++++++++++++++++++ test_cases/zte-pod1/storage/fio_bm.yaml | 44 +++++++++++++++++++++ test_cases/zte-pod1/storage/fio_vm.yaml | 49 ++++++++++++++++++++++++ 15 files changed, 630 insertions(+), 2 deletions(-) create mode 100644 test_cases/zte-pod1/compute/dhrystone_vm.yaml create mode 100644 test_cases/zte-pod1/compute/dpi_bm.yaml create mode 100644 test_cases/zte-pod1/compute/dpi_vm.yaml create mode 100644 test_cases/zte-pod1/compute/ramspeed_bm.yaml create mode 100644 test_cases/zte-pod1/compute/ramspeed_vm.yaml create mode 100644 test_cases/zte-pod1/compute/ssl_bm.yaml create mode 100644 test_cases/zte-pod1/compute/ssl_vm.yaml create mode 100644 test_cases/zte-pod1/compute/whetstone_bm.yaml create mode 100644 test_cases/zte-pod1/compute/whetstone_vm.yaml create mode 100644 test_cases/zte-pod1/network/iperf_bm.yaml create mode 100644 test_cases/zte-pod1/network/iperf_vm.yaml create mode 100644 test_cases/zte-pod1/network/iperf_vm_2.yaml create mode 100644 test_cases/zte-pod1/storage/fio_bm.yaml create mode 100644 test_cases/zte-pod1/storage/fio_vm.yaml (limited to 'test_cases') diff --git a/test_cases/zte-pod1/compute/dhrystone_bm.yaml b/test_cases/zte-pod1/compute/dhrystone_bm.yaml index 2835ba8c..437dafd8 100644 --- a/test_cases/zte-pod1/compute/dhrystone_bm.yaml +++ b/test_cases/zte-pod1/compute/dhrystone_bm.yaml @@ -7,11 +7,11 @@ Scenario: Context: Host_Machines: machine_1: - ip: 10.20.0.24 + ip: 10.20.0.23 pw: role: host machine_2: - ip: 10.20.0.25 + ip: 10.20.0.24 pw: role: host @@ -23,6 +23,7 @@ Context: no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + Test_Description: Test_category: "Compute" Benchmark: "dhrystone" diff --git a/test_cases/zte-pod1/compute/dhrystone_vm.yaml b/test_cases/zte-pod1/compute/dhrystone_vm.yaml new file mode 100644 index 00000000..6f213426 --- /dev/null +++ b/test_cases/zte-pod1/compute/dhrystone_vm.yaml @@ -0,0 +1,50 @@ +Scenario: + benchmark: dhrystone + host: virtualmachine_1, virtualmachine_2 + server: blakc + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + virtualmachine_2: + availability_zone: compute2 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "dhrystone" + Overview: > + '''This test will run the dhrystone benchmark in parallel on machine_1 and machine_2.\n + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + machine_1: + ip: 172.18.0.16 + pw: Op3nStack + role: host + machine_2: + ip: 172.18.0.15 + pw: Op3nStack + role: host + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' + diff --git a/test_cases/zte-pod1/compute/dpi_bm.yaml b/test_cases/zte-pod1/compute/dpi_bm.yaml new file mode 100644 index 00000000..d1c5963e --- /dev/null +++ b/test_cases/zte-pod1/compute/dpi_bm.yaml @@ -0,0 +1,40 @@ +Scenario: + benchmark: dpi + host: machine_1,machine_2 + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: host + machine_2: + ip: 10.20.0.24 + pw: + role: host + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "dpi" + Overview: > + '''This test will run the DPI benchmark in serial on virutalmachine_1 and virtualmachine_2.\n + if you wish to add a host machine add the following information under the Host_Machine tag + virtualmachine_2: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'provider_network' + + role: 1host + flavor: m1.large + machine_1: + ip: + pw: + role: + ''' + diff --git a/test_cases/zte-pod1/compute/dpi_vm.yaml b/test_cases/zte-pod1/compute/dpi_vm.yaml new file mode 100644 index 00000000..d47b7f31 --- /dev/null +++ b/test_cases/zte-pod1/compute/dpi_vm.yaml @@ -0,0 +1,40 @@ +Scenario: + benchmark: dpi + 1Run : virtualmachine_1, virtualmachine_2 + +Context: + Host_Machines: + + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 1Run + flavor: m1.large + virtualmachine_2: + availability_zone: compute2 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 1Run + flavor: m1.large + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "dpi" + Overview: > + '''This test will run the DPI benchmark in parallel on virutalmachine_1 and virtualmachine_2.\n + if you wish to add a host machine add the following information under the Host_Machine tag + + machine_1: + ip: + pw: + role: + ''' + diff --git a/test_cases/zte-pod1/compute/ramspeed_bm.yaml b/test_cases/zte-pod1/compute/ramspeed_bm.yaml new file mode 100644 index 00000000..d9e1f170 --- /dev/null +++ b/test_cases/zte-pod1/compute/ramspeed_bm.yaml @@ -0,0 +1,40 @@ + +Scenario: + benchmark: ramspeed + host: machine_1, machine_2 + server: + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: host + machine_2: + ip: 10.20.0.24 + pw: + role: host + + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + + +Test_Description: + Test_category: "Compute" + Benchmark: "dhrystone" + Overview: > + ''' This test will run the dhrystone benchmark in parallel on machine_1 and machine_2.\n + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: ''' + + diff --git a/test_cases/zte-pod1/compute/ramspeed_vm.yaml b/test_cases/zte-pod1/compute/ramspeed_vm.yaml new file mode 100644 index 00000000..942aa3fe --- /dev/null +++ b/test_cases/zte-pod1/compute/ramspeed_vm.yaml @@ -0,0 +1,50 @@ +Scenario: + benchmark: ramspeed + host: virtualmachine_1, virtualmachine_2 + server: blakc + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + virtualmachine_2: + availability_zone: compute2 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "dhrystone" + Overview: > + '''This test will run the dhrystone benchmark in parallel on machine_1 and machine_2.\n + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + machine_1: + ip: 172.18.0.16 + pw: Op3nStack + role: host + machine_2: + ip: 172.18.0.15 + pw: Op3nStack + role: host + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' + diff --git a/test_cases/zte-pod1/compute/ssl_bm.yaml b/test_cases/zte-pod1/compute/ssl_bm.yaml new file mode 100644 index 00000000..e4f608e6 --- /dev/null +++ b/test_cases/zte-pod1/compute/ssl_bm.yaml @@ -0,0 +1,36 @@ +Scenario: + benchmark: ssl + host: machine_1,machine_2 + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: host + machine_2: + ip: 10.20.0.24 + pw: + role: host + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + + +Test_Description: + Test_category: "Compute" + Benchmark: "ssl" + Overview: > + '''This test will run the SSL benchmark in parallel on machine_1 and machine_1. + If you wish to add a virtual machine add the following information under the Virtual_Machine tag + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' diff --git a/test_cases/zte-pod1/compute/ssl_vm.yaml b/test_cases/zte-pod1/compute/ssl_vm.yaml new file mode 100644 index 00000000..cc97ecfd --- /dev/null +++ b/test_cases/zte-pod1/compute/ssl_vm.yaml @@ -0,0 +1,40 @@ +Scenario: + benchmark: ssl + host: virtualmachine_1, virtualmachine_2 + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + public_network: 'admin-floating_net' + OS_image: 'QTIP_CentOS' + flavor: 'm1.large' + role: host + virtualmachine_2: + availability_zone: compute2 + public_network: 'admin-floating_net' + OS_image: 'QTIP_CentOS' + flavor: 'm1.large' + role: host + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "ssl" + Overview: > + '''This test will run the SSL benchmark in parallel on virtualmachine_1 and machine_1.\n + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' diff --git a/test_cases/zte-pod1/compute/whetstone_bm.yaml b/test_cases/zte-pod1/compute/whetstone_bm.yaml new file mode 100644 index 00000000..6c703de1 --- /dev/null +++ b/test_cases/zte-pod1/compute/whetstone_bm.yaml @@ -0,0 +1,38 @@ + +Scenario: + benchmark: whetstone + host: machine_1, machine_2 + + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: host + machine_2: + ip: 10.20.0.24 + pw: + role: host + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + + +Test_Description: + Test_category: "Compute" + Benchmark: "whetstone" + Overview: > + ''' This test will run the whetstone benchmark in parallel on machine_1 and machine_2.\n + if you wish to add a baremetal machine add the following information under the Virtual_Machine tag + + machine_3: + ip: + pw: + role: + ''' + + diff --git a/test_cases/zte-pod1/compute/whetstone_vm.yaml b/test_cases/zte-pod1/compute/whetstone_vm.yaml new file mode 100644 index 00000000..bcde58c1 --- /dev/null +++ b/test_cases/zte-pod1/compute/whetstone_vm.yaml @@ -0,0 +1,48 @@ +Scenario: + benchmark: whetstone + host: virtualmachine_1, virtualmachine_1 + server: + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + virtualmachine_2: + availability_zone: compute2 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Compute" + Benchmark: "dhrystone" + Overview: > + '''This test will run the whetstone benchmark in parallel on machine_1 and machine_2.\n + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + virtualmachine_1: + availability_zone: nova + public_network: 'net04_ext' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + + virtualmachine_1: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' + diff --git a/test_cases/zte-pod1/network/iperf_bm.yaml b/test_cases/zte-pod1/network/iperf_bm.yaml new file mode 100644 index 00000000..5b2126fd --- /dev/null +++ b/test_cases/zte-pod1/network/iperf_bm.yaml @@ -0,0 +1,55 @@ +Scenario: + benchmark: iperf + topology: Client and Server on different baremetal Compute nodes + server: machine_1 + client: machine_2 + benchmark_details: + duration: 20 + protocol: tcp + bandwidthGbps: 10 + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: 1-server + machine_2: + ip: 10.20.0.24 + pw: + role: 2-host + + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "network" + Benchmark: "iperf" + Overview: > + '''This test will run the IPERF benchmark on virutalmachine_1 and virtualmachine_2. On the\n + same compute node + if you wish to add a host machine add the following information under the Host_Machine tag + virtualmachine_1: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'net04_ext' + role: 1-server + flavor: m1.large + + virtualmachine_2: + availability_zone: compute2 + OS_image: QTIP_CentOS + public_network: 'net04_ext' + role: 2-host + flavor: m1.large + + machine_1: + ip: + pw: + role: + ''' + diff --git a/test_cases/zte-pod1/network/iperf_vm.yaml b/test_cases/zte-pod1/network/iperf_vm.yaml new file mode 100644 index 00000000..f03b5b6f --- /dev/null +++ b/test_cases/zte-pod1/network/iperf_vm.yaml @@ -0,0 +1,48 @@ +Scenario: + benchmark: iperf + topology: Client and Server on ONE compute + server : virtualmachine_1 + client: virtualmachine_2 + description: 'Leave the bandwidth as 0 to throttle maximum traffic' + benchmark_details: + duration: 20 + protocol: tcp + bandwidthGbps: 0 + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 1-server + flavor: m1.large + + virtualmachine_2: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 2-host + flavor: m1.large + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "network" + Benchmark: "iperf" + Overview: > + '''This test will run the IPERF benchmark on virutalmachine_1 and virtualmachine_2. On the\n + same compute node + if you wish to add a host machine add the following information under the Host_Machine tag + + machine_1: + ip: + pw: + role: + ''' + diff --git a/test_cases/zte-pod1/network/iperf_vm_2.yaml b/test_cases/zte-pod1/network/iperf_vm_2.yaml new file mode 100644 index 00000000..649adf8c --- /dev/null +++ b/test_cases/zte-pod1/network/iperf_vm_2.yaml @@ -0,0 +1,49 @@ +Scenario: + benchmark: iperf + topology: Client and Server on two different compute nodes + server : virtualmachine_1 + client: virtualmachine_2 + description: 'Leave the bandwidth as 0 to throttle maximum traffic' + benchmark_details: + duration: 20 + protocol: tcp + bandwidthGbps: 0 + +Context: + Host_Machines: + + + Virtual_Machines: + virtualmachine_1: + availability_zone: compute1 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 1-server + flavor: m1.large + + virtualmachine_2: + availability_zone: compute2 + OS_image: QTIP_CentOS + public_network: 'admin-floating_net' + role: 2-host + flavor: m1.large + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "network" + Benchmark: "iperf" + Overview: > + '''This test will run the IPERF benchmark on virutalmachine_1 and virtualmachine_2. On the\n + same compute node + if you wish to add a host machine add the following information under the Host_Machine tag + + machine_1: + ip: + pw: + role: + ''' + diff --git a/test_cases/zte-pod1/storage/fio_bm.yaml b/test_cases/zte-pod1/storage/fio_bm.yaml new file mode 100644 index 00000000..d07623c5 --- /dev/null +++ b/test_cases/zte-pod1/storage/fio_bm.yaml @@ -0,0 +1,44 @@ +Scenario: + benchmark: fio + host: machine_1, machine_2 + server: + +Context: + Host_Machines: + machine_1: + ip: 10.20.0.23 + pw: + role: host + machine_2: + ip: 10.20.0.24 + pw: + role: host + + + Virtual_Machines: + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + + +Test_Description: + Test_category: "Storage" + Benchmark: "FIO" + Overview: > + '''This test will run the FIO benchmark in parallel on host machines "machine_1" and "machine_2".\n + The fio job specifications can be found in qtip/benchmarks/fio_jobs/test_job. + The job conists of an fio load of: + 1.50% rand read 50% rand write + 2.Asynch engine + 3.Direct IO. + 4.Queing depth of 2 + + if you wish to add another machine add the following information under the Host_Machines tag + machine_3: + ip: 172.18.0.16 + pw: Op3nStack + role: host + ''' + diff --git a/test_cases/zte-pod1/storage/fio_vm.yaml b/test_cases/zte-pod1/storage/fio_vm.yaml new file mode 100644 index 00000000..3e2f9174 --- /dev/null +++ b/test_cases/zte-pod1/storage/fio_vm.yaml @@ -0,0 +1,49 @@ +Scenario: + benchmark: fio + host: machine_1, machine_2 + server: + +Context: + Host_Machines: + + Virtual_Machines: + virtualmachine_1: + availability_zone: computer1 + public_network: 'admin_floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + virtualmachine_2: + availability_zone: computer2 + public_network: 'admin-floating_net' + OS_image: QTIP_CentOS + flavor: m1.large + role: host + + Proxy_Environment: + http_proxy: http://10.20.0.1:8118 + https_proxy: http://10.20.0.1:8118 + no_proxy: localhost,127.0.0.1,10.20.*,192.168.* + +Test_Description: + Test_category: "Storage" + Benchmark: "FIO" + Overview: > + '''This test will run the FIO benchmark in parallel on virtualmachine_1 and virtualmachine_2.\n + The fio job specifications can be found in qtip/benchmarks/fio_jobs/test_job. + The job conists of an fio load of: + 1.50% rand read 50% rand write + 2.Asynch engine + 3.Direct IO. + 4.Queing depth of 2 + + if you wish to add a virtual machine add the following information under the Virtual_Machine tag + + virtualmachine_3: + availability_zone: + public_network: + OS_image: + flavor: + role: + ''' + -- cgit 1.2.3-korg