Cut the heat flavor
1024Mb memory is too much for single instance.
approximately 4 GiB memory used even without a booted VM.
The heat auto-scaling scenario needs to boot 3 VM
(currently disabled), if any other test running in parallel
and boots up a vm it would easily can cause OOM an
issue.
The heat-slow job can work with 128 MiB instance memory,
but this change reduces it just to 512 MiB (safer for the guest),
and enough to avoid OOM issues on the host,
and let us to heve more vm at the same time.
The m1.tiny flavor is not good because now it has a hard coded
1 GiB disk limit and the f20 image requires 2 GiB.
Setting the disk size to '0' -> automatically use the virtual size
of the image.
Using multiple cores does not really helps in boot time :(,
but it might cause higher host load. (More locking)
Reducing the core number to 1.
Change-Id: Ice7c1253d15e91fd1c02bc8c6809335aaebfff4a
Attila Fazekas authored on 2014/06/13 23:09:37Showing 1 changed files
| ... | ... |
@@ -316,10 +316,10 @@ function configure_tempest {
|
| 316 | 316 |
if [[ ! -z "$HEAT_CFN_IMAGE_URL" ]]; then |
| 317 | 317 |
iniset $TEMPEST_CONFIG orchestration image_ref $(basename "$HEAT_CFN_IMAGE_URL" ".qcow2") |
| 318 | 318 |
fi |
| 319 |
- # build a specialized heat flavor that is likely to be fast |
|
| 319 |
+ # build a specialized heat flavor |
|
| 320 | 320 |
available_flavors=$(nova flavor-list) |
| 321 | 321 |
if [[ ! ( $available_flavors =~ 'm1.heat' ) ]]; then |
| 322 |
- nova flavor-create m1.heat 451 1024 0 2 |
|
| 322 |
+ nova flavor-create m1.heat 451 512 0 1 |
|
| 323 | 323 |
fi |
| 324 | 324 |
iniset $TEMPEST_CONFIG orchestration instance_type "m1.heat" |
| 325 | 325 |
iniset $TEMPEST_CONFIG orchestration build_timeout 900 |