aboutsummaryrefslogtreecommitdiffstats
path: root/install.sh
AgeCommit message (Collapse)AuthorFilesLines
2018-04-26Migrate install.sh script to ansibleJohn O Loughlin1-1/+1
Ansible scripts to install yardstick. These scripts will take a few options: INSTALLATION_MODE : Container or Baremetal YARDSTICK_DIR: Location of Yardstick directory VIRTUAL_ENVIRONMENT: Should a virtual environment be used NSB_DIR: Location of NSB directory JIRA: YARDSTICK-1126 Change-Id: I4a13e07e96650ffd971dfb18472f2563cfd51aa9 Signed-off-by: John O Loughlin <john.oloughlin@intel.com>
2018-03-28Fix RabbitMQ service installation and initializationRodolfo Alonso Hernandez1-3/+4
RabbitMQ service added in [1] is not correctly installed and initialized: - There is an error during the installation process ("\" character missing). - In the installation script, the service needs to be started first. - In the container installation, the service needs to be started via supervisor. [1]https://gerrit.opnfv.org/gerrit/#/c/53597/ JIRA: YARDSTICK-1103 Change-Id: Iade3d6ce4b522e6f576af71b7afe5559081f7929 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-21Install RabitMQ for RPC messaging between processesRodolfo Alonso Hernandez1-0/+5
In NetworkServices Tescases, the TGs (traffic generators) run the traffic in a separate process. In order to synchronize the traffic injection and the runner interval loops, an RPC server is needed to publish/subscribe events. RabbitMQ is a well supported MQ in Linux (used in OpenStack or collectd) and supported by Python implemented projects like oslo.messaging [1]. RabbitMQ default configuration: - Port: 5672 - User/password: yardstick/yardstick [1]https://github.com/openstack/oslo.messaging JIRA: YARDSTICK-1068 Change-Id: I15db294ee430fb38e574a59b9ce1bf0f8b651a67 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2018-03-20Enforce pip version during installationRodolfo Alonso Hernandez1-1/+1
Currently there is a reported problem in pip library [1]. To avoid this problem, the pip version should be enforced during the installation. [1]https://github.com/pypa/pip/issues/5079 JIRA: YARDSTICK-1087 Change-Id: I2ee28749f146cd3b0e1bf4ed92b51cbe6db8b2f3 Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
2017-11-20fix docker client don't have trex_clientAce Lee1-0/+7
JIRA: YARDSTICK-854 Add trex_client in docker, so we could run NSB testcase in docker container. Change-Id: Iac1393d6e3a175137973190936ab69a1f2ce8272 Signed-off-by: Ace Lee <liyin11@huawei.com>
2017-11-17update docker version to 16.04Ace Lee1-1/+3
JIRA: YARDSTICK-690 This patch is for Yardstick Docker base image upgrade to 16.04 This patch will enable ansible build image in yardstick env prepare. Add qemu-img convert to ansible build image. Change-Id: I43127b6020bd20bd9f4aac4fca0df75353b24346 Signed-off-by: Ace Lee <liyin11@huawei.com>
2017-10-17Added required ubuntu packages to run IxLoad clientMaciej Skrocki1-1/+3
To fully enable IxLoad, after installing the IXIA client, check /opt/ixia/ixload/<ver>/bin/ixloadpython and make sure you can run this cmd inside the yardstick container. Usually user is required to copy or link /opt/ixia/python/<ver>/bin/ixiapython to /usr/bin/ixiapython<ver>. Change-Id: I6bc633802ad6c70329581014ec89c75bb7f8d688 Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-08-11Merge "New storage test case: Bonnie++"Jing Lu1-0/+1
2017-08-03New storage test case: Bonnie++JingLu51-0/+1
JIRA: YARDSTICK-770 Bonnie++ is a disk and file system benchmarking tool for measuring I/O performance. With Bonnie++ you can quickly and easily produce a meaningful value to represent your current file system performance. This work is add new storage test case using Bonnie++. Change-Id: I752fee156707cda730962c68d17fda4d4e9cd472 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-08-02Merge "Fix adding right deb repo based on the distro we are running on"Ross Brattain1-6/+14
2017-08-01Add yardstick logo in GUIchenjiankun1-0/+1
JIRA: YARDSTICK-767 We have yardstick logo in opnfv community. We have the demand to display it in yardstick GUI. Change-Id: Ief5807c918754e679e95ae1d1f3a769ab2d6d4b2 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-27Yardstick GUI & GUI deploymentchenjiankun1-1/+4
JIRA: YARDSTICK-758 As E release plan, we have the need of yardstick GUI. This patch is GUI front end code and deployment. The backend code is yardstick API. Change-Id: Ib15f78bcc50168c7828beff97256e9939c6da809 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-17Fix adding right deb repo based on the distro we are running onDeepak S1-6/+14
JIRA: YARDSTICK-669 Change-Id: I0f3848b7803bc62c88effd00e850755e514893c4 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-07-03Yardstick: Aarch64 jenkins slave supportAlexandru Nemes1-12/+32
Change-Id: I2d58c38d75fc1fe036769340e9fb02932f543510 Signed-off-by: Alexandru Nemes <alexandru.nemes@enea.com>
2017-05-25Added arm condition in install.sh to avoid installation error on ubuntu.Maciej Skrocki1-2/+9
Change-Id: Iaa07a8d68a7dede6f2b42440be44ed07f035b1ca Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
2017-04-20Yardstick virtualenv supportchenjiankun1-3/+1
JIRA: YARDSTICK-620 In the patch, I separate python-setuptools from install.sh and separate appdirs from requirements.txt because there will be error when install them in virtualenv. Also I will update the documentation when this patch merged; Change-Id: I99a532d1851983775869e7c5e8e65fd0229e86df Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-04-06pip install yardstick failed in ApexJingLu51-1/+1
JIRA: YARDSTICK-625 In Apex, yardstick uninstall and install via pip failed. This bug blocks yardstick CI jobs. This patch enables pip install yardstick in editable mode. So the install_yardstick() in yardstick_verify is unnecessary. Change-Id: If290dac5fee5584601064ae9753ae2340643d3ca Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-04-01Yardstick virtualenv supportchenjiankun1-17/+28
JIRA: YARDSTICK-620 Currently we recommend using docker to run yardstick. And it is hard to use virtualenv to install yardstick. So I modify install.sh in yardstick root path. It will support using virtualenv to install yardstick(including API) in linux. In this patch, I make yardstick support read yardstick configuration have priority over constants. Change-Id: I9ea1241b228532a6497451e6c8f232173ddb783e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-02-23Merge "Update missing license headers"Rex Lee1-0/+10
2017-02-18Add python-pip & flake8 package to install.shDeepak S1-0/+2
On a fresh system, we need "python-pip & flake8" to run yardstick. Adding same to install.sh Change-Id: I3e13ffdf53eed7e976e55e2b23afd1b1ea50ec33 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-02-17Update missing license headersDeepak S1-0/+10
Change-Id: I063fd37fe25754c94d164ae5a209d15b69322093 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2016-12-03Making nginx and uwsgi service start when run docker by using supervisorchenjiankun1-0/+1
JIRA: YARDSTICK-444 We need web service start when docker run. But now we add command in bashrc, so the web service start only if we login in docker container. So I use supervisor to make the web service start when docker run. Change-Id: Ic77eb0e130ae7dbd82039c312649fed76b128513 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-30Create API and command to create a influxDB containerchenjiankun1-1/+1
JIRA: YARDSTICK-425 This API is used to create a influxDB Container Add command line to create a influxDB Container, too Change-Id: If9c2d04b779924d492a5d5ea91f7968fa959570e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-23Deployment for APIchenjiankun1-0/+3
JIRA: YARDSTICK-418 Set yardstick.conf in /etc/yardstick/ to config yardstick output way Set nginx config file Set nginx service and uwsgi service start when boot Change-Id: I5749042ae1b05feaf895cb0abffed7f9194b9cee Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-15Yardstick installation unified (pip/setup)chenjiankun1-0/+40
JIRA: YARDSTICK-394 Change-Id: I486aa24121b2ad8d66cd6df97ca86ef826862c91 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>