summaryrefslogtreecommitdiffstats
path: root/ansible
AgeCommit message (Collapse)AuthorFilesLines
2017-09-19Fixed few gaps when running on a minimal version of systemMaciej Skrocki2-1/+2
- we need to make sure we have lsof installed - we need to update cache inside the image, because we are unable to install some of them Change-Id: Ic555489779e9096540001cb9c62ea2ab25c1ae90 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-09-13Removed special networking from yardstick container when started by nsb_setup.Maciej Skrocki1-1/+0
Change-Id: Ief1cfd7c018948a9125549400bb5bf0e5c20d730 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-09-06Merge "decrease default hugepages, depends on VNF of course"Ross Brattain1-1/+1
2017-09-06ansible: update package proxy codeRoss Brattain4-84/+66
re-enable retries Change-Id: I77738250e8aa8de3c8a8a1019093af04ce785ae0 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-05ansible: remove default openrc_fileRoss Brattain1-1/+0
when clause is re-evaluated after default Change-Id: I2f9b093a4cb0e2d024f8d6beb935f336ac1df637 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-05ansible: fix corrupt /etc/fstab boot errorRoss Brattain1-1/+7
Change-Id: I71fdef5deff75cad434bf19f0a7e507c1dcc4ed3 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-05Introduced ansible playbook to setup NSB.Maciej Skrocki18-95/+205
Change-Id: I5865cd50d5fde26e9e9fc265d4385372d668413f Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-09-01decrease default hugepages, depends on VNF of courseRoss Brattain1-1/+1
Change-Id: I5e8d1461e158c0b499a8864099fbb218965a429f Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-31Introduced default values and remove unnecessary ones from ansible code ↵Maciej Skrocki6-34/+11
image build code. Change-Id: Id711d6fdacaddeafb8550290503d6cb6c814ea70 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-08-25Merge "ansible: update dpdk, trex and samplevnf install"Ross Brattain38-420/+315
2017-08-24Added proxy setup for standard cloudimage playbooks.Maciej Skrocki2-0/+4
Change-Id: I4f29f584395d58b2fcece1ca8fcbda78a64e3a66 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-08-23ansible: update dpdk, trex and samplevnf installRoss Brattain38-420/+315
we now clone samplevnf from git repo made install_samplevnf role that takes as parameter VNF name added ubuntu_server_cloudimg_modify_samplevnfs playbook Change-Id: I5724e3b844b3137542a5c293516893a5c80f5c61 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-14Ansible typo fix, whitespaceRoss Brattain3-2/+1
Change-Id: I3639ab84ab5b9e802e1bbd23674b0fbda46fdc66 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-08yardstick setup ansible, including load_imagesMalanik Jan125-0/+5175
also update to cirros 0.3.5 added PROX compilation add create_node_pod_yaml role JIRA: YARDSTICK-639 Change-Id: If5999841287a54c7e5c64a7cc487c6394df90424 Signed-off-by: Malanik Jan <janx.malanik@intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-02Merge "Add spec cpu2006 test case"Jing Lu7-0/+134
2017-07-31Add spec cpu2006 test caseJingLu58-0/+138
JIRA: YARDSTICK-764 This work is about support run SPEC CPU2006 benchmark. users must get a "cpu2006-1.2.iso" from the SPEC website, save it under the /home/opnfv/yardstick/yardstick/resources folder (e.g. /home/opnfv/yardstick/yardstick/resources/cpu2006-1.2.iso), user may also supply a runspec cfg file (e.g. /home/opnfv/yardstick/yardstick/resources/files/yardstick_spec_cpu2006.cfg). Change-Id: If4aecc1c14635a07589555196d2edc8bd37d7bdb Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-26Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migrationchenjiankun10-1/+203
JIRA: YARDSTICK-174 This live migration test case is based on share storage, default share storage is enabled. This test case will do some config work. And do live migration and calculate the migration time and downtime. Change-Id: I6601601edebdd0ac6434ba632b1eba9e9bd4fda0 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-04-13Bugfix: fix typoJingLu52-1/+1
Change-Id: I9b7cd5f94b1663af3b807ce24c941868b10d85d1 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-20Merge "Add NUMA pinning support for node context"Jing Lu4-0/+160
2017-03-13Add CPU pinning support for node contextJingLu514-0/+272
JIRA: YARDSTICK-573 Since the yardstick framework now has supported an improved node type context, this patch adds support for VM vcpu pinning ability in the node type context. It provides several scripts that can be used to configurate the controller and compute nodes. Change-Id: If2c6e7b1b85ff78b9d2a5997bf03bdc6877aaf74 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-03-08Add NUMA pinning support for node contextJingLu54-0/+160
JIRA: YARDSTICK-574 Since the yardstick framework now has supported an improved node type context, this patch adds support for VM NUMA pinning ability in the node type context. It provides several scripts that can be used to configurate the controller and compute nodes Change-Id: If5eafdca6df1b1196bc17bfdd12aea9f4016752f Signed-off-by: JingLu5 <lvjing5@huawei.com>
| | | The examples of monitors show as follows, there are four | | | instance of the "openstack-cmd" monitor, in order to check | | | the database connection of different OpenStack components. | | | | | | monitor1: | | | -monitor_type: "openstack-cmd" | | | -api_name: "openstack image list" | | | monitor2: | | | -monitor_type: "openstack-cmd" | | | -api_name: "openstack router list" | | | monitor3: | | | -monitor_type: "openstack-cmd" | | | -api_name: "openstack stack list" | | | monitor4: | | | -monitor_type: "openstack-cmd" | | | -api_name: "openstack volume list" | | | monitor5: | | | -monitor_type: "process" | | | -process_name: "mysql" | | | -host: node1 | | | | +--------------+--------------------------------------------------------------+ |metrics | In this test case, there are two metrics: | | | 1)service_outage_time: which indicates the maximum outage | | | time (seconds) of the specified OpenStack command request. | | | 2)process_recover_time: which indicates the maximum time | | | (seconds) from the process being killed to recovered | | | | +--------------+--------------------------------------------------------------+ |test tool | Developed by the project. Please see folder: | | | "yardstick/benchmark/scenarios/availability/ha_tools" | | | | +--------------+--------------------------------------------------------------+ |references | ETSI NFV REL001 | | | | +--------------+--------------------------------------------------------------+ |configuration | This test case needs two configuration files: | | | 1) test case file: opnfv_yardstick_tc090.yaml | | | -Attackers: see above "attackers" description | | | -waiting_time: which is the time (seconds) from the process | | | being killed to stopping monitors the monitors | | | -Monitors: see above "monitors" description | | | -SLA: see above "metrics" description | | | | | | 2)POD file: pod.yaml | | | The POD configuration should record on pod.yaml first. | | | the "host" item in this test case will use the node name in | | | the pod.yaml. | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | start monitors: | | | each monitor will run with independently process | | | | | | Result: The monitor info will be collected. | | | | +--------------+--------------------------------------------------------------+ |step 2 | do attacker: connect the host through SSH, and then execute | | | the kill process script with param value specified by | | | "process_name" | | | | | | Result: Process will be killed. | | | | +--------------+--------------------------------------------------------------+ |step 3 | stop monitors after a period of time specified by | | | "waiting_time" | | | | | | Result: The monitor info will be aggregated. | | | | +--------------+--------------------------------------------------------------+ |step 4 | verify the SLA | | | | | | Result: The test case is passed or not. | | | | +--------------+--------------------------------------------------------------+ |post-action | It is the action when the test cases exist. It will check the| | | status of the specified process on the host, and restart the | | | process if it is not running for next test cases | | | | +--------------+--------------------------------------------------------------+ |test verdict | Fails only if SLA is not passed, or if there is a test case | | | execution problem. | | | | +--------------+--------------------------------------------------------------+