summaryrefslogtreecommitdiffstats
path: root/xci/installer/kubespray/playbooks/configure-targethosts.yml
blob: 2fde9877e4f928aaad7795f2ede6f29c11fd1a69 (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
---
- hosts: k8s-cluster
  remote_user: root
  vars_files:
    - "{{ xci_path }}/xci/var/opnfv.yml"

  pre_tasks:
    - name: Load distribution variables
      include_vars:
        file: "{{ item }}"
      with_items:
        - "{{ xci_path }}/xci/var/{{ ansible_os_family }}.yml"

  roles:
    - role: bootstrap-host

  tasks:
    - name: Manage SSH keys
      include_tasks: "{{ xci_path }}/xci/playbooks/manage-ssh-keys.yml"

    - name: Install dbus
      package:
        name: "{{ (ansible_pkg_mgr == 'zypper') | ternary('dbus-1', 'dbus') }}"
        state: present
        update_cache: "{{ (ansible_pkg_mgr in ['apt', 'zypper']) | ternary('yes', omit) }}"

- hosts: kube-master
  remote_user: root
  vars_files:
    - "{{ xci_path }}/xci/var/opnfv.yml"
  pre_tasks:
    - name: Load distribution variables
      include_vars:
        file: "{{ xci_path }}/xci/var/{{ ansible_os_family }}.yml"
  roles:
    - role: "keepalived"
      when:  xci_flavor == 'ha'
    - role: "haproxy_server"
      haproxy_service_configs: "{{ haproxy_default_services}}"
      when:  xci_flavor == 'ha'
------+--------------------------------------------------------------+ |configuration | The L2FWD test cases are listed below: | | | | | | * tc_prox_baremetal_l2fwd-2.yaml | | | * tc_prox_baremetal_l2fwd-4.yaml | | | * tc_prox_baremetal_l2fwd_pktTouch-2.yaml | | | * tc_prox_baremetal_l2fwd_pktTouch-4.yaml | | | * tc_prox_baremetal_l2fwd_multiflow-2.yaml | | | * tc_prox_baremetal_l2fwd_multiflow-4.yaml | | | * tc_prox_heat_context_l2fwd-2.yaml | | | * tc_prox_heat_context_l2fwd-4.yaml | | | * tc_prox_heat_context_l2fwd_pktTouch-2.yaml | | | * tc_prox_heat_context_l2fwd_pktTouch-4.yaml | | | * tc_prox_heat_context_l2fwd_multiflow-2.yaml | | | * tc_prox_heat_context_l2fwd_multiflow-4.yaml | | | | | | Test duration is set as 300sec for each test. | | | Packet size set as 64 bytes in traffic profile | | | These can be configured | | | | +--------------+--------------------------------------------------------------+ |test tool | PROX | | | PROX is a DPDK application that can simulate VNF workloads | | | and can generate traffic and used for NFVI characterization | | | | +--------------+--------------------------------------------------------------+ |applicability | The PROX L2FWD test cases can be configured with different: | | | | | | * packet sizes; | | | * test durations; | | | * tolerated loss; | | | | | | Default values exist. | | | | +--------------+--------------------------------------------------------------+ |pre-test | For Openstack test case image (yardstick-samplevnfs) needs | |conditions | to be installed into Glance with Prox and Dpdk included in | | | it. | | | | | | For Baremetal tests cases Prox and Dpdk must be installed in | | | the hosts where the test is executed. The pod.yaml file must | | | have the necessary system and NIC information | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | For Baremetal test: The TG and VNF are started on the hosts | | | based on the pod file. | | | | | | For Heat test: Two host VMs are booted, as Traffic generator | | | and VNF(L2FWD workload) based on the test flavor. | | | | +--------------+--------------------------------------------------------------+ |step 2 | Yardstick is connected with the TG and VNF by using ssh. | | | The test will resolve the topology and instantiate the VNF | | | and TG and collect the KPI's/metrics. | | | | +--------------+--------------------------------------------------------------+ |step 3 | The TG will send packets to the VNF. If the number of | | | dropped packets is more than the tolerated loss the line | | | rate or throughput is halved. This is done until the dropped | | | packets are within an acceptable tolerated loss. | | | | | | The KPI is the number of packets per second for 64 bytes | | | packet size with an accepted minimal packet loss for the | | | default configuration. | | | | +--------------+--------------------------------------------------------------+ |step 4 | In Baremetal test: The test quits the application and unbind | | | the dpdk ports. | | | | | | In Heat test: Two host VMs are deleted on test completion. | | | | +--------------+--------------------------------------------------------------+ |test verdict | The test case will achieve a Throughput with an accepted | | | minimal tolerated packet loss. | +--------------+--------------------------------------------------------------+