summaryrefslogtreecommitdiffstats
path: root/samples/bonnie++.yaml
blob: 5c85eb20e50ee85d84f1a6ddbd7e01ab37329095 (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
##############################################################################
# Copyright (c) 2017 Huawei Technologies Co.,Ltd and others.
#
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Apache License, Version 2.0
# which accompanies this distribution, and is available at
# http://www.apache.org/licenses/LICENSE-2.0
##############################################################################
---
# Sample benchmark task config file
# measure storage and file system performance using bonnie++

schema: "yardstick:task:0.1"

{% set provider = provider or none %}
{% set physical_network = physical_network or 'physnet1' %}
{% set segmentation_id = segmentation_id or none %}

scenarios:
-
  type: Bonnie++
  options:
    file_size: 1024
    ram_size: 512
    test_dir: /tmp
    #test_user: root
    concurrency: 1

  host: bonnie.demo

  runner:
    type: Iteration
    iterations: 1

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

  servers:
    bonnie:
      floating_ip: true

  networks:
    test:
      cidr: '10.0.1.0/24'
      {% if provider == "vlan" %}
      provider: {{provider}}
      physical_network: {{physical_network}}
        {% if segmentation_id %}
      segmentation_id: {{segmentation_id}}
        {% endif %}
      {% endif %}
ned outgoing network interface. * *Traffic Rule Application*: The process of packet tagging, based on a predefined set of rules. Packet tagging may include e.g. Type of Service (:term:`ToS`) field modification. Architecture ============ The Traffic Inspection module is the most computationally intensive component of the :term:`VNF`. It implements filtering and packet matching algorithms in order to support the enhanced traffic forwarding capability of the :term:`VNF`. The component supports a flow table (exploiting hashing algorithms for fast indexing of flows) and an inspection engine for traffic classification. The implementation used for these experiments exploits the nDPI library. The packet capturing mechanism is implemented using libpcap. When the :term:`DPI` engine identifies a new flow, the flow register is updated with the appropriate information and transmitted across the Traffic Forwarding module, which then applies any required policy updates. The Traffic Forwarding moudle is responsible for routing and packet forwarding. It accepts incoming network traffic, consults the flow table for classification information for each incoming flow and then applies pre-defined policies marking e.g. :term:`ToS`/Differentiated Services Code Point (:term:`DSCP`) multimedia traffic for Quality of Service (:term:`QoS`) enablement on the forwarded traffic. It is assumed that the traffic is forwarded using the default policy until it is identified and new policies are enforced. The expected response delay is considered to be negligible, as only a small number of packets are required to identify each flow. Graphical Overview ================== .. code-block:: console +----------------------------+ | | | Virtual Traffic Classifier | | | | Analysing/Forwarding | | ------------> | | ethA ethB | | | +----------------------------+ | ^ | | v | +----------------------------+ | | | Virtual Switch | | | +----------------------------+ Install ======= run the vTC/build.sh with root privileges Run === :: sudo ./pfbridge -a eth1 -b eth2 .. note:: Virtual Traffic Classifier is not support in OPNFV Danube release. Development Environment ======================= Ubuntu 14.04 Ubuntu 16.04