Add unit test file for ArithmeticRunner

* Initial test: test ArithmeticRunner._run_benchmark called arguments

JIRA: YARDSTICK-1245

Change-Id: Id18c36bd1345052863ab777bf899c00fe66fd713
Signed-off-by: Miikka Koistinen <miikka.koistinen@nokia.com>

Merge "Enable "wait_until_true" when used ouf the main thread"

Merge "NSB TREX RFC2544 scenario fails with correlated traffic"

Merge "Make injection time configurable for IXIA RFC2544 test cases"

Enable "wait_until_true" when used ouf the main thread

"util.wait_until_true" uses "util.Timer" to create an active wait for a
condition. "Timer" class uses "signal" to create a watchdog to track the
time lapsed.

When used out of the main thread, "Timer" raises the following error:
  ValueError: signal only works in main thread

To make "util.wait_until_true" usable always, a new waitting method is
implemented.

JIRA: YARDSTICK-1358

Change-Id: Ifb5ba0b17b5beca0af5ceab4f6431d58b7928762
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

NSB TREX RFC2544 scenario fails with correlated traffic

When correlated traffic TC is running, the traffic is
running only on uplink ports instead of both type of ports
(yardstick/network_services/traffic_profile/rfc2544.py +113).

Trex TG fails to get samples on downlink ports.

JIRA: YARDSTICK-1357

Change-Id: I66d78b73f2dc5bb531fe8607d0e46f60b828953e
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Make injection time configurable for IXIA RFC2544 test cases

JIRA: YARDSTICK-1196

Change-Id: I77b4772b9224ff5cd21fd9fc67eb7e4b821fcf77
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

kubernetes_utils: avoid 404 error code in delete_config_map()

JIRA: YARDSTICK-1318

Change-Id: I0c04bd2928d5a4166b483f0c4f9f75fa9e5e00d2
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

kubernetes_utils: avoid 404 error code in delete_replication_controller()

JIRA: YARDSTICK-1319

Change-Id: I8370c5ef4e43e58a8bb9c3aac60a089b0981dda0
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Merge "Fix typo in classname AclUknownActionTemplate"

IxNetwork IPv4 mask format is x.x.x.x

When updating the IP packet in IxNextgen library, the IPv4 mask should
be defined in the following format: x.x.x.x

This mask defines the number of lower bits used to generate a random IP.
For example:
  - mask length: 16
  - mask string: 0.0.255.255

JIRA: YARDSTICK-1351

Change-Id: Ie3cbf0205aac83aea8d7f665bc068e8566238055
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Fix typo in classname AclUknownActionTemplate

AclUknownActionTemplate -> AclUnknownActionTemplate

JIRA: YARDSTICK-1334
Change-Id: I796e080078c657c5e0e59144d24ec797e244a8f7
Signed-off-by: Emma Foley <emma.l.foley@intel.com>

Merge changes from topics 'YARDSTICK-1351', 'YARDSTICK-1339'

* changes:
  Add IP mask to IxNetwork configuration
  Improve NetworkServiceTestCase._get_ip_flow_range() function

Merge changes from topics 'YARDSTICK-1346', 'YARDSTICK-1345', 'YARDSTICK-1344'

* changes:
  Add pktgen test case base files
  Add pktgen traffic profile
  Add DPDK pktgen traffic generator

Merge "kubernetes_utils: avoid 404 error code in delete_network()"

kubernetes_utils: avoid 404 error code in delete_network()

JIRA: YARDSTICK-1316

Change-Id: I792c873b42aba80be62ff7a93f6d02ea89e42356
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Merge changes from topics 'YARDSTICK-1343', 'YARDSTICK-1342'

* changes:
  Cleanup EnvironmentTestCase unit tests
  Cleanup Testcase unit tests

Merge "Cleanup Ansible common unit tests"

Add IP mask to IxNetwork configuration

Assign the IP mask to IxNetwork configuration, depending on the IP range
provided by the user in the traffic profile. In case of single IP, a
default mask will be provided:
  - IP_VERSION_4_MASK = 24
  - IP_VERSION_6_MASK = 64

JIRA: YARDSTICK-1351

Change-Id: I029473ab8b9966a76cf559ffef53b34ca11462ad
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Bugfix: yardstick env grafana return http error"

Merge "Adjust timeouts for installing requrements"

Add pktgen test case base files

Added pktgen VNF topology, VNF descriptor and traffic profile files.

JIRA: YARDSTICK-1346

Change-Id: Ifb1824edb2dc8db1afa83a53573fb2ed1c2a79ea
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Add pktgen traffic profile

This new profile is based on the DPDK pktgen traffic generator. The traffic
generator is controlled using LUA [1]. Those string commands are sent to
the traffic generator using an open socket. Host address and open port are
needed parameters.

The following actions are implemented:
  - start injection
  - stop injection
  - change injection rate
  - clear all stats
  - help message command

[1] http://pktgen-dpdk.readthedocs.io/en/latest/lua.html

JIRA: YARDSTICK-1345

Change-Id: I560a168d194cedc9fdba312ec84437933efc8d9b
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Adjust timeouts for installing requrements

The time it takes to install the the requirements is different on the 2 build
servers we have for aarch64: on build4 it takes ~12min, on pod5 it takes <10min.
So the timeouts need to be adjusted again to bigger values to cover both servers.

JIRA: ARMBAND-391

Change-Id: Idd8f07e6f54d64a6cfaee0753ecd8efd141ff615
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>

Add DPDK pktgen traffic generator

Add DPDK pktgen traffic generator. This traffic generator is designed
only to work in with a MQ aware runner. Implements two consumer methods:
  - runner_method_start_iteration
  - runner_method_stop_iteration

"run_traffic" method will only initialize the traffic profile object.
This traffic generator uses a socket port (LUA port, default 22022) to
send the command messages.

Link: http://pktgen-dpdk.readthedocs.io/en/latest/index.html
JIRA: YARDSTICK-1344

Change-Id: I89bba0f462fa1c22b33f1253f67f7c41e6e721a5
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Cleanup TaskParseTestCase unit tests"

Cleanup EnvironmentTestCase unit tests

Removed unneeded output.

JIRA: YARDSTICK-1343

Change-Id: Ifad21a62ce1152976952a4b8c5a142fa5a544904
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Propose the backporting process"

Merge "Clean-up tests in test_vsperf_dpdk.py:VsperfDPDKTestCase"

Cleanup Testcase unit tests

Removed unneeded output.

JIRA: YARDSTICK-1342

Change-Id: I45ab14f854cd059625c1a96959b1cbd0a19f52a8
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Cleanup Ansible common unit tests

Removed unneeded output, use proper exception checks and remove
filesystem access.

JIRA: YARDSTICK-1341

Change-Id: I5c56e7b34d0e96946211e6172290bce24a156d68
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Improve NetworkServiceTestCase._get_ip_flow_range() function

Improve the method to calculate the CIDR IP address range (first one,
last one). IPv4Network or IPv6Network hosts() is an iterator throught
the list of valid IPs. If the network is too big, the generation of a
list [1] can be very expensive.

[1]https://github.com/opnfv/yardstick/blob/master/yardstick/benchmark/scenarios/networking/vnf_generic.py#L90

JIRA: YARDSTICK-1339

Change-Id: I9352b2e7ff4925c246df8b40ecf43e8dc96c42d2
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Increase rounding digits in IXIA RFC2544"

Merge "Accept line rate percentage or fps a initial rate for IXIA RFC2544"

Merge "kubernetes_utils: avoid 404 error code in delete_custom_resource_definition()"

Merge "kubernetes_utils: avoid 404 error code in delete_service()"

Cleanup TaskParseTestCase unit tests

Removed unneeded output.

JIRA: YARDSTICK-1340

Change-Id: I66c0902edfea5fad9282bcb36e57b67cd6c340ab
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Increase timeouts for installing requrements

Currently the docker images fails to build on aarch64 because the installation
of the requirements step fails. The failure is caused by the timers which expire
and don't mark the job as finished.

JIRA: ARMBAND-391

Change-Id: Ic84982f81d064af1c27cf776d12a57eadc20957a
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>

kubernetes_utils: avoid 404 error code in delete_custom_resource_definition()

JIRA: YARDSTICK-1317

Change-Id: I2dc924334199761d63dce9aebe9ce200ca0fddf8
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Increase rounding digits in IXIA RFC2544

Increase rounding digits in IXIA RFC2544 for:
  - Drop percentage: 6 digits
  - Rate: 5 digits, both for fps and % line rate.

JIRA: YARDSTICK-1338

Change-Id: Iae6e49dd3d15035452f28976af0b16222fa8e23c
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Accept line rate percentage or fps a initial rate for IXIA RFC2544

Accept line rate percentage or fps a initial rate for IXIA RFC2544 traffic profile:
  traffic_profile:
    traffic_type : IXIARFC2544Profile
    frame_rate : 100%

  traffic_profile:
    traffic_type : IXIARFC2544Profile
    frame_rate : 5000fps

JIRA: YARDSTICK-1336

Change-Id: I85b3dd0daf563bb7af098a3aa5bb872961fb009b
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Create Dockerfile to create a yardstick-image of docker"

Add "stdin" and "tty" parameters to Kubernetes container

JIRA: YARDSTICK-1330

Change-Id: I05303a1d0783421472883806f97441dd63f7f740
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

kubernetes_utils: avoid 404 error code in delete_service()

JIRA: YARDSTICK-1321

Change-Id: Id0f3a5d93f11674fd3908a7f5cf7214afcfa3600
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Accept strings and lists as container "args" and "commands"

Accept strings and list of strings as "args" and "commands"
in a Kubernetes container.

JIRA: YARDSTICK-1329

Change-Id: I56470741072fb7f9a62d695c51fcb0cc3f3ff1b9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Create Dockerfile to create a yardstick-image of docker

this Dockerfile target to generate a image with testing tool
installed, similar to yardstick-image for VM. The docker image
is used by k8s to start pods and test.

JIRA: YARDSTICK-1287

Change-Id: Id09a3fb6d880869c8f523d688b2ef641fb434541
Signed-off-by: rexlee8776 <limingjiang@huawei.com>

Merge "Add "imagePullPolicy" parameter in Kubernetes container"

Merge "Kubernetes NodePort must have 'name' if multiple created"

Bugfix: yardstick env grafana return http error

It returns "HTTPError: 404 Client Error: Not Found for url" when creating Grafana dashboard.
The log shows it failed when create "tc058" dashboard.

JIRA: YARDSTICK-1333

Change-Id: I14a275a31f019a7dc66a531a85314cc098e0f4c9
Signed-off-by: rexlee8776 <limingjiang@huawei.com>

Add "imagePullPolicy" parameter in Kubernetes container

The configuration parameter "imagePullPolicy" defines how Kubernetes
retrieves de image. By default, Kubernetes will always try to pull the
latest image from the repository [1]. Three possible arguments are accepted:
  - Always
  - IfNotPresent
  - Never

Example of Kubernetes pod definition:
  containers:
    - name: vcmts-pktgen-pod-0
      image: openretriever/yardstick
      imagePullPolicy: IfNotPresent

Example of Yardstick definition:
  context:
    name: k8syardstick
    type: Kubernetesservers:
    vnf:
      image: openretriever/yardstick
      imagePullPolicy: IfNotPresent

[1] https://kubernetes.io/docs/concepts/containers/images/

JIRA: YARDSTICK-1328

Change-Id: I83bfb01670eef22218b1affd7d37af14e32a622e
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Kubernetes NodePort must have 'name' if multiple created

In Kubernetes context, service NodePort can contain more than one port
defined. Actually, by default port SSH (22) is always created. If more
than one port is defined in the service template, 'name' parameter is
mandatory.

Names must be lowercase, containing alphanumeric characters or '-'.

Verification regex used by Kubernetes: [a-z0-9]([-a-z0-9]*[a-z0-9])?

JIRA: YARDSTICK-1324

Change-Id: I82791761d8eae24196c2f16aee9900af28d44c57
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

NodePort information returned in context should be a dictionary

In Kubernetes context, NodePort information returned in context should be
a dictionary. In [1], the node information is dumped in a yaml file. The
NodePort object doesn't have a serialize implementation; instead of
returning the object, an equivalent dictionary should be returned.

[1]https://github.com/opnfv/yardstick/blob/f6fa0d7422f0669d049dbf07a51eb39b1dc25830/yardstick/benchmark/scenarios/networking/vnf_generic.py#L293

JIRA: YARDSTICK-1323

Change-Id: If4844c9b074920a7a7d8c1a424b681f9f8a4b0c5
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "add support of dpdk for bottlenecks_ping"

add support of dpdk for bottlenecks_ping

This patch is supposed to be coordinated with
https://gerrit.opnfv.org/gerrit/59901
to support dpdk scenario for Bottlenecks

JIRA: YARDSTICK-1332

Change-Id: I4ae3d05523d0624d689702cb8eb23be364830de1
Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com>

Merge "Improve VMs spawning for OpenStack"

Merge "Fix CGNAPT VNF name in install.yaml"

kubernetes_utils: avoid 404 error code in delete_pod()

JIRA: YARDSTICK-1320

Change-Id: I5b762d4732440008630093e1d0952f7e41a8a191
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Fix CGNAPT VNF name in install.yaml

JIRA: YARDSTICK-1325

Change-Id: Idc56237f3a8435c6636be2a6e7c6b04662d831ee
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Clean-up tests in test_vsperf_dpdk.py:VsperfDPDKTestCase

* Move some common mocking into the setUp()
  The same return values was being set for moch_ssh
  in each test method.
* Remove duplicate statements in test_vsperf_dpdk.py:VsperfDPDKTestCase
  The same assert* were being called for multiple methods,
  which were checking that setup worked as expected.
  These checks are not required each time.

Change-Id: I325fc98ee569dcf7988951c82da0c02d5e465a16
Signed-off-by: Emma Foley <emma.l.foley@intel.com>

Propose the backporting process

Change-Id: I0b0fddf8dfdd68fa144b28dba911352e9a4974fd
JIRA: YARDSTICK-1253
Signed-off-by: Emma Foley <emma.l.foley@intel.com>

Create a SampleVNF MQ consumer class

This new class is designed to be used in a ``GenericVNF`` object (VNF
or traffic generator) in a builder pattern. This consumer class will
be instantiated when initializing the ``GenericVNF`` derived object.
The ``GenericVNFConsumer`` endpoint is the ``GenericVNF``derived object
itself.

``GenericVNFEndpoint`` is an interface class to be inherited in a
``GenericVNF`` child object; the VNF object will implement the endpoints
methods.

  NewVNF(GenericVNF, GenericVNFEndpoint):
    def __init__(self, name, vnfd, task_id):
      ...
      self._consumer = vnf_base.GenericVNFConsumer([task_id], self)
      self._consumer.start_rpc_server()

JIRA: YARDSTICK-1293

Change-Id: I1bcd980352099e9ebefdab0c96d51aa46f6a1e54
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Add service NodePort information in server description

Kubernetes context provides a list of NodePort services to each
replication controller. "_get_server" should return this information
in the server description dictionary:

  server: { ...
    'service_ports': <list of NodePort objects>
  }

Relevant NodePort object attributes:
  - port
  - node_port
  - target_port
  - protocol
  - name

JIRA: YARDSTICK-1313

Change-Id: Ie481cdea4761f162e3b3329e4e2c5a982faea9e9
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Add interface and network information to Kubernetes context

Add to "Kubernetes" context the "interfaces" information when retrieving
a server. This information is needed for NSPerf test cases.

The interface information comes from the resource controller network list.
Each replication controller will have one port per network defined.

JIRA: YARDSTICK-1303

Change-Id: Ifb0e17df295c042a643128c705a93876af999bad
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "nsb_setup.sh fails to build DPDK"

Merge "Cleanup TG IxLoad test cases"

Merge "Omit functional tests from coverage report analysis"

Merge "Fix "id" retrieval from MQ producer in GenericTrafficGen"

Merge ""install_dpdk" ansible role fails if DPDK version has revision number"

nsb_setup.sh fails to build DPDK

Some DPDK archive releases have different prefix in the
unzipped archived folder name. Fixed scripts to determine
the DPDK path using find.

JIRA: YARDSTICK-1307

Change-Id: Id50bc1256f458e94aa7d4050a0f8ea3462fe9083
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Merge "Make uwsgi app to not demonize"

Merge "Add ACL sample config file"

Merge "Improve "get_server" function in Kubernetes context"

Improve "get_server" function in Kubernetes context

When a kubernetes context is returning the node info it is
assumed that the first port defined is the ssh port which may
not be the case. This patch will address this issue by looking
for a defined port 22.

JIRA: YARDSTICK-1301

Change-Id: I65dee1bcf62f21ebcaefeaa2666bb0ad53f3876c
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>

"install_dpdk" ansible role fails if DPDK version has revision number

In [1], the DPDK version string is converted to a number to be compared.
If DPDK version format is "major.minor.revision", this conversion will fail.

[1] https://github.com/opnfv/yardstick/blob/master/ansible/roles/install_dpdk/tasks/main.yml#L119

JIRA: YARDSTICK-1306

Change-Id: Id8d32f28627ff5a0ff8d4fb604282ba2d9931c25
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Fix "id" retrieval from MQ producer in GenericTrafficGen

"GenericTrafficGen.get_mq_producer_id" uses a wrong method to retrieve
the MQ producer ID. "MessagingProducer" ID is a property called "id".

JIRA: YARDSTICK-1312

Change-Id: Id72836b1cde59059359907bd3a315a1abb55778e
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Do not request NFVi metrics from empty nodes"

Merge "Make context types constants"

Cleanup TG IxLoad test cases

Refactor SSH handling and library mocks.

JIRA: YARDSTICK-1236

Change-Id: I591601f8ea8bf4bbd5c43300ff29d7930af5c3c6
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Omit functional tests from coverage report analysis

Coverage report will also search for new code introduced in
/yardstick/tests/functional. Any modification in functional
test cases must be omitted from coverage report.

JIRA: YARDSTICK-1308

Change-Id: Ib9c48102340f70d8d79f78dc81cbfe7b29c81115
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Change "monitor" to "assert" in SLA"

Merge "Revert "vPE Sample VNF is missing in the installation scripts""

Revert "vPE Sample VNF is missing in the installation scripts"

SampleVNF source tree doesn't contain vPE VNF sources, thus the
installation of the vPE sampleVNF fails because of the changes.
Reverting.

This reverts commit 5bb855a82d960a4fb796e801ec9a9a22dc40b1ca.

Change-Id: I27e929e813a28847c2ca725031ec767633a36954
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Change "monitor" to "assert" in SLA

Change "monitor" to "assert" in SLA to make an Overall testcase
to fail if a subtest Scenario fails

JIRA: YARDSTICK-1305

Change-Id: I90f5c95f0ddace160d751a435d60ae09a42101f2
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>

Add ACL sample config file

The acl_rules.yaml is unused, so renamed it to sample config.
Updated the config with example of possible ACL configuration.

JIRA: YARDSTICK-1304

Change-Id: If0537cf55f4c96f57844caed5bf1c9050647e0d5
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Do not request NFVi metrics from empty nodes

In Collector class [1], the information from the nodes is retrieved to
create a ResourceProfile object per node. If the node information is
empty, Collector should skip this node.

[1] https://github.com/opnfv/yardstick/blob/master/yardstick/network_services/collector/subscriber.py#L34

JIRA: YARDSTICK-1302

Change-Id: I84dff3e20881352263736b682a60a4f382960153
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge "Add network elements as a dict in Kubernetes context"

Make uwsgi app to not demonize

Supervisord doesn't support demonize applications, thus we have to
make the uwsgi application to run not in background.

- Fixed Yardstick API path.
- Fixed HttpClient class to raise correct exception when
  the HTML response (not JSON) like 4xx, 5xx is received.
  (http://docs.python-requests.org/en/master/user/quickstart/#json-response-content)

JIRA: YARDSTICK-1297

Change-Id: I4d1c1bb7266eeed0bd357bd28b91206d1580611f
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>

Add "tolerations" parameter in Kubernetes context

This new parameter, "torelations", is applied to pods and allow (but not
require) the pods to schedule onto node with matching tains [1].

Example of "tolerations" definition in a Kubernetes pod:

  spec:
    containers: [...]
    tolerations:
      - key: <key defined in the taint>
        value: <key value to match with the taint>
        effect: <effect in case of match>
        operator: <matching operator>
      - key: ...

Example of "tolerations" definition in a Yardstick test case:

  context:
    type: Kubernetes
    servers:
      host:
        containers: [...]
        tolerations:
          - key: ...
            value: ...
            effect: ...
            operator: ...

NOTE: if any toleration is defined, a default one will be applied in
order to allow any replication controller to create the pods in any
Kubernetes node. This default toleration is defined as:

  spec:
    tolerations:
      - operator: "Exists"

[1] https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/

JIRA: YARDSTICK-1254

Change-Id: I32fb9c7086b4218c323218738057f634eb6ffff4
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Add "ports" parameters in Kubernetes context

This new parameter, "ports", will allow the user to
automatically to add port variables in a pod definition:
context:
  type: Kubernetes
    servers:
        host:
            image: ...
            commands: ...
            ports:
                - containerPort: <port value>    # Mandatory
                  hostIP: <host IP>              # Optional
                  hostPort: <host port>          # Optional
                  name: <port name>              # Optional
                  protocol: <protocol name>      # Optional

The port type and the definition must be one of the supported ones
in Kubernetes [1].

Container port definition, V1 API, Kubernetes Python library v6.0.0 [2]

[1] https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/
[2] https://github.com/kubernetes-client/python/blob/6.0.0/kubernetes/client/models/v1_container_port.py

JIRA: YARDSTICK-1183

Change-Id: I3673dbeec8d380cb2f8b1dacf6c25c7cdbc37e28
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>

Add "restartPolicy" parameter in Kubernetes policy

This new parameter, "restartPolicy", will allow define the restart policy per pod.

Example of yaml definition in Kubernetes:
apiVersion: v1
kind: Pod
metadata:
  name: frontend
spec:
  containers:
    - name: db
      ...
  restartPolicy: Always  # Possible values: "Always", "OnFailure" and "Never"

Example of definition in a Yardstick context:
context:
  type: Kubernetes
    servers:
      host:
        containers:
          - name: ...
        restartPolicy: Always  # Default value: "Always"

Restart policy [1].
[1] https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy

JIRA: YARDSTICK-1175

Change-Id: Id4317b909f98422e89d6d4553e8cfb0e1f593355
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>

Merge "Add "resources" parameter in Kubernetes context"

Merge "Add send socket commands function"

Fix IXIA IxNetwork IMIX configuration

IxNet library is not setting correctly the IMIX definition per traffic
item. The correct input for "weightedRangePairs" parameter is:

  [[64, 64, 10], [128, 128, 15], [512, 512, 5]]

JIRA: YARDSTICK-1296

Change-Id: Idb4034ce817250da5b9a434230b1be6dae0d3ba3
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Merge changes from topics 'YARDSTICK-1286', 'YARDSTICK-1127'

* changes:
  Make "IterationIPC" MQ producer for VNF control messages
  Enable traffic generator PID in "NSPerf" scenario setup
  Enable the MQ producer in "SampleVNFTrafficGen" class
  Add "TrafficGeneratorProducer" for "GenericTrafficGen" instances
  Add "IterationIPC" runner

Add network elements as a dict in Kubernetes context

Like in Heat context, network elements should be defined in a
dictionary, using the network name as the entry key.

Previous implementation:
  context:
    networks:
      - name: ...
        plugin: ...
        args: ...

New implementation:
  context:
    networks:
      net_name_1:
        plugin: ...
        args: ...
      net_name_2: ...

JIRA: YARDSTICK-1160

Change-Id: I786b06555af509440604305e2c3c2c9fe521bef8
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>

Add "resources" parameter in Kubernetes context

This new parameter, "resources", will allow the user to automatically
add resources in a pod definition per container.

Example of yaml definition in Kubernetes:
apiVersion: v1
kind: Pod
metadata:
  name: frontend
spec:
  containers:
    - name: db
      image: mysql
      resources:
        requests:
          memory: "64Mi"
          cpu: "250m"
        limits:
          memory: "128Mi"
          cpu: "500m"

Example of definition in a Yardstick context:
context:
  type: Kubernetes
    servers:
        host:
            resources:    # There are two possible keys in this dict:
                          # "requests" and "limits".
              limits: <dictionary>
              requests: <dictionary>

Resources in containers [1].

[1] https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/

JIRA:YARDSTICK-1171

Change-Id: I163d72d9d3e88b538fca73eb4dbf38613aa23ff4
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>

Add "env" parameter in Kubernetes context

This new parameter, "env", will allow the user to
automatically to add environment variables in a pod definition

Example of definition in a context:
  context:
    type: Kubernetes
      servers:
        host:
            image: ...
            commands: ...
            env:
                - <variable name>: <variable value>
                - <variable name>: <variable value>

The volume type and the definition must be one of the supported
ones in Kubernetes [1].

[1] https://kubernetes.io/docs/concepts/storage/volumes/#types-of-volumes

JIRA: YARDSTICK-1161

Change-Id: Icf372a98c090063f10c9217755519ab92ba9b0ba
Signed-off-by: John O Loughlin <john.oloughlin@intel.com>

Merge "Create user defined "NodePort" services per pod"

Merge "Change "KubernetesObject" class name to "ReplicationController""

Merge "Specify the networks to be used per pod"