Age | Commit message (Collapse) | Author | Files | Lines |
|
Bug fix in script "build_yardstick_image.yml", to
- Use option "-a" to list all used loop devices, to be more compatible.
- Ignore the error and continue, if the debug command failed.
JIRA: YARDSTICK-1121
Change-Id: I24aaebb2ffe3107ca5c619401725aa8c8e1af295
Signed-off-by: ting wu <ting.wu@enea.com>
|
|
the full path probably isn't matching, so just grep
for the basename
JIRA: YARDSTICK-1096
JIRA: YARDSTICK-1054
Change-Id: I403a7f51310c0856fae0f79d115ba0786b7c417c
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
CI is failing due to unable to find loop device for kpartx
"cmd": [
"kpartx",
"-l",
"/tmp/workspace/yardstick/yardstick-xenial-server.raw"
]
"stderr": "mount: could not find any device /dev/loop#Bad address\ncan't set up loop",
This error occurs when kpartx can't find any loop devices to use
https://build.opnfv.org/ci/job/yardstick-compass-virtual-daily-master/3261/console
JIRA: YARDSTICK-1054
JIRA: YARDSTICK-1096
Change-Id: Ib6131ce29c4f9e81386eb5471dd6107825798620
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
parted doesn't handle growing GPT partition correctly, so switch to
growpart
see https://github.com/opnfv/fuel/blob/master/mcp/scripts/lib.sh#L133
for example
If the yardstick image uses GPT then parted complains about the GPT
table
The warning is "Warning: Not all of the space available to
DEVICE appears to be used, you can fix the GPT to use all
of the space (an extra 500 blocks) or continue with the
current setting?"
The backup GPT table is not at the end of the
disk, as it should be. This might mean that
another operating system believes the disk is
smaller. Fix, by moving the backup to the end
(and removing the old backup)?
echo 'f' to fix the GPT table
Instead use growpart
JIRA: YARDSTICK-1058
Change-Id: Ib0e90feef1e3766408b4f742036f2a48af942f32
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
JIRA: YARDSTICK-879
Add some image build vars
Add automatic image build of nsb
yardstick_image: ansible-playbook -e img_property="normal" -vvv -i inventory.ini build_yardstick_image.yml
nsb_image_build: ansible-playbook -e img_property="nsb" -vvv -i inventory.ini build_yardstick_image.yml
prepare for yardstick image uploading
Change-Id: I9fdf30084511ca9a008df3b53887b06273bbd549
Signed-off-by: Ace Lee <liyin11@huawei.com>
|
|
JIRA: YARDSTICK-893
- hosts and plays in ansible/nsb_setup.yml refactored
Fixed proxy configuration from env or /etc/environment in nsb_setup.sh
Fixed ansible parameter 'environment: "{{ proxy_env }}"' in:
- roles for components download.
- roles for components dependencies install.
Now, you can use ansible to modify all yardstick-standalone hosts at once.
1) Configure http[s]_proxy in
- /etc/environment
or
- env variables
2) Modify ansible/yardstick-install-inventory.ini:
[jumphost]
localhost ansible_connection=local
[yardstick-standalone]
yardstick-standalone-node ansible_host=192.168.1.2
yardstick-standalone-node-2 ansible_host=192.168.1.3
[all:vars]
ansible_user=root
ansible_pass=root
3) start:
./nsb_setup.sh # for baremetal/sriov
./nsb_setup.sh <path to admin-openrc.sh> #for openstack heat
Change-Id: I167db8bae8303210f21e8ae6f3870ef054bbedce
Signed-off-by: Malanik Jan <janx.malanik@intel.com>
|
|
Variable "img_modify_playbook" is being assigned in first context of
./ansible/build_yardstick_image.yml [1]. However this variable is never used.
In second context [2], the variable used is a CLI input variable.
[1]https://github.com/opnfv/yardstick/blob/stable/euphrates/ansible/build_yardstick_image.yml#L187
[2]https://github.com/opnfv/yardstick/blob/stable/euphrates/ansible/build_yardstick_image.yml#L205
JIRA: YARDSTICK-871
Change-Id: I7bd5063c5e86520abcafdc782222ee53faf58f45
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
|
|
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>
|
|
|
|
Change-Id: I71fdef5deff75cad434bf19f0a7e507c1dcc4ed3
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
When compiling Trex, DPDK, collectd and all the SampleVNFs
we use more than the 2.2GB size of the original Ubuntu cloud image.
Accordingly we need to resize the image.
If we were not inside a docker container we would use virt-resize
to automatically handle all the cases, but virt-resize launches qemu.
Instead we can use qemu-img to add extra space, then
luckily we can use parted to resize the partition and finally
resize2fs to resize the filesystem.
This limits us to only ext3/4 images, but if we need to
we could add support for other filesystems by checking
file system type.
Change-Id: Iac84b8e6967af5be64c280a7b1eaaf09f5d6b3aa
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: I5865cd50d5fde26e9e9fc265d4385372d668413f
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
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>
|
|
Change-Id: I3639ab84ab5b9e802e1bbd23674b0fbda46fdc66
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
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>
|