aboutsummaryrefslogtreecommitdiffstats
path: root/yardstick/tests/p2p_rfc2544_throughput_sample.yaml
blob: 32b42187355f8ce12c8fff604fcd00a2e98f9dc5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
# Copyright 2016 Intel Corporation.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# VSPERF specific configuration file for execution of RFC2544 throughput
# traffic. Traffic executed by traffic generator is forwarded directly
# between interfaces connected to the traffic generator. So test will only
# benchmark the performance of OVS external bridge at controller node.
# Details about supported test options and test case execution can be
# found in VSPERF documentation:
#
#   http://artifacts.opnfv.org/vswitchperf/docs/userguide/yardstick.html

schema: "yardstick:task:0.1"

scenarios:
-
  type: Vsperf
  options:
    testname: 'p2p_rfc2544_throughput'
    frame_size: '64'
    test_params: 'TRAFFICGEN_DURATION=30;TRAFFIC={"traffic_type":"rfc2544_throughput"}'
    trafficgen_port1: 'eth1'
    trafficgen_port2: 'eth3'
    external_bridge: 'br-ex'
    conf_file: '~/vsperf-yardstick.conf'

  host: vsperf.demo

  runner:
    type: Sequence
    scenario_option_name: frame_size
    sequence:
    - 64
    - 128
    - 512
    - 1024
    - 1518
  sla:
    # The throughput SLA (or any other SLA) cannot be set to a meaningful
    # value without knowledge of the server and networking environment,
    # possibly including prior testing in that environment to establish
    # a baseline SLA level under well-understood circumstances.
    metrics: 'throughput_rx_fps'
    throughput_rx_fps: 500000
    action: monitor

context:
  name: demo
  image: vsperf
  flavor: vsperf-flavor
  user: ubuntu

  placement_groups:
    pgrp1:
      policy: "availability"

  servers:
    vsperf:
      floating_ip: true
      placement: "pgrp1"

  networks:
    test:
      cidr: '10.0.0.0/24'
pan class="nt">subarches: "*" labels: daily 2: release: xenial os: ubuntu arches: amd64 subarches: "*" labels: daily # Virsh power settings # Specifies the uri and keys to use for virsh power control of the # juju virtual machine. If the uri is omitted, the value for the # --remote is used. If no power settings are desired, then do not # supply the virsh block. virsh: rsa_priv_key: /home/ubuntu/.ssh/id_rsa rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub uri: qemu+ssh://ubuntu@172.16.50.51/system # Defines the IP Address that the configuration script will use to # to access the MAAS controller via SSH. ip_address: 172.16.50.50 # This section allows the user to set a series of options on the # MAAS server itself. The list of config options can be found in # the upstream MAAS documentation: # - http://maas.ubuntu.com/docs/api.html#maas-server settings: main_archive: http://us.archive.ubuntu.com/ubuntu upstream_dns: 8.8.8.8 maas_name: juniperpod1 # kernel_opts: "console=tty0 console=ttyS1,115200n8" # ntp_server: ntp.ubuntu.com # This section is used to define the networking parameters for when # the node first comes up. It is fed into the meta-data cloud-init # configuration and is used to configure the networking piece of the # service. The contents of this section are written directly to the # /etc/network/interfaces file. # # Please note, this is slightly different than the # node-group-interfaces section below. This will configure the # machine's networking params, and the node-group-interfaces will # configure the maas node-group interfaces which is used for # controlling the dhcp, dns, etc. network_config: | auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 172.16.50.50 netmask 255.255.255.0 network 172.16.50.0 broadcast 172.16.50.255 dns-nameservers 8.8.8.8 127.0.0.1 auto eth1 iface eth1 inet static address 10.10.15.50 netmask 255.255.240.0 network 10.10.0.0 broadcast 10.10.15.255 gateway 10.10.10.1 # The node-group-interfaces section is used to configure the MAAS # network interfaces. Basic configuration is supported, such as which # device should be bound, the range of IP addresses, etc. # Note: this may contain the special identifiers: # ${maas_net} - the first 3 octets of the ipv4 address # ${maas_ip} - the ip address of the MAAS controller node_group_ifaces: - device: eth0 ip: 172.16.50.50 subnet_mask: 255.255.255.0 broadcast_ip: 172.16.50.255 router_ip: 172.16.50.50 static_range: low: 172.16.50.60 high: 172.16.50.90 dynamic_range: low: 172.16.50.91 high: 172.16.50.254 # Defines the physical nodes which are added to the MAAS cluster # controller upon startup of the node. nodes: - name: 2-R4N4B2-control tags: control architecture: amd64/generic mac_addresses: - "0c:c4:7a:16:2a:70" power: type: ipmi address: 10.10.7.92 user: ADMIN pass: ADMIN driver: LAN_2_0 - name: 3-R4N3B1-compute tags: compute architecture: amd64/generic mac_addresses: - "0c:c4:7a:53:57:c2" power: type: ipmi address: 10.10.7.84 user: ADMIN pass: ADMIN driver: LAN_2_0 - name: 4-R4N4B4-control tags: control architecture: amd64/generic mac_addresses: - "0c:c4:7a:16:22:9c" power: type: ipmi address: 10.10.7.95 user: ADMIN pass: ADMIN driver: LAN_2_0 - name: 5-R4N3B2-compute tags: compute architecture: amd64/generic mac_addresses: - "0c:c4:7a:53:57:16" power: type: ipmi address: 10.10.7.85 user: ADMIN pass: ADMIN driver: LAN_2_0 - name: 6-R4N4B3-control tags: control architecture: amd64/generic mac_addresses: - "0c:c4:7a:16:2a:0a" power: type: ipmi address: 10.10.7.93 user: ADMIN pass: ADMIN driver: LAN_2_0 # Contains the virtual machine parameters for creating the Juju bootstrap # node virtual machine juju-bootstrap: name: bootstrap interfaces: ['bridge=brAdm,model=virtio', 'bridge=brPublic,model=virtio'] memory: 4096 vcpus: 2 arch: amd64 pool: default disk_size: 120G