x
/
bareon-allocator
Code Issues Proposed changes

Add single disk integration tests

This commit is contained in:
Evgeniy L 2016-02-17 17:52:34 +03:00
parent 5de533857e
commit 3cac7dfc60
10 changed files with 230 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
bareon_dynamic_allocator/tests/fixtures/single_disk_max_min.yaml vendored Normal file
View File

@ -0,0 +1,32 @@
name: First is max, second is min
dynamic_schema:
- id: lv1
type: lv
max_size: 20
- id: lv2
type: lv
min_size: 20
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
- space_id: lv1
size: 20
- space_id: lv2
size: 80
- space_id: unallocated
size: 0

31
bareon_dynamic_allocator/tests/fixtures/single_disk_max_none.yaml vendored Normal file
View File

@ -0,0 +1,31 @@
name: First space has max, second had no preferable sizes
dynamic_schema:
- id: lv1
type: lv
max_size: 20
- id: lv2
type: lv
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
- space_id: lv1
size: 20
- space_id: lv2
size: 80
- space_id: unallocated
size: 0

0
bareon_dynamic_allocator/tests/fixtures/max_only.yaml → bareon_dynamic_allocator/tests/fixtures/single_disk_max_only.yaml vendored
View File

33
bareon_dynamic_allocator/tests/fixtures/single_disk_min_max.yaml vendored Normal file
View File

@ -0,0 +1,33 @@
name: First is min, second is max
dynamic_schema:
- id: lv1
type: lv
min_size: 20
- id: lv2
type: lv
max_size: 20
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
# TODO figure out if this is expected behaviour
- space_id: lv1
size: 100
- space_id: lv2
size: 0
- space_id: unallocated
size: 0

38
bareon_dynamic_allocator/tests/fixtures/single_disk_min_max_size.yaml vendored Normal file
View File

@ -0,0 +1,38 @@
name: First is max, second is min, third has specific size
dynamic_schema:
- id: lv1
type: lv
max_size: 20
- id: lv2
type: lv
min_size: 20
- id: lv3
type: lv
size: 50
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
- space_id: lv1
size: 20
- space_id: lv2
size: 30
- space_id: lv3
size: 50
- space_id: unallocated
size: 0

32
bareon_dynamic_allocator/tests/fixtures/single_disk_min_none.yaml vendored Normal file
View File

@ -0,0 +1,32 @@
name: First min, second has no size preferences
dynamic_schema:
- id: lv1
type: lv
min_size: 20
- id: lv2
type: lv
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
# TODO figure out if this is expected behaviour
- space_id: lv1
size: 100
- space_id: lv2
size: 0
- space_id: unallocated
size: 0

0
bareon_dynamic_allocator/tests/fixtures/min_only.yaml → bareon_dynamic_allocator/tests/fixtures/single_disk_min_only.yaml vendored
View File

32
bareon_dynamic_allocator/tests/fixtures/single_disk_none_max.yaml vendored Normal file
View File

@ -0,0 +1,32 @@
name: First had no preferable sizes, second space has max
dynamic_schema:
- id: lv1
type: lv
- id: lv2
type: lv
max_size: 20
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
# TODO figure out if this is expected behaviour
- space_id: lv1
size: 100
- space_id: lv2
size: 0
- space_id: unallocated
size: 0

32
bareon_dynamic_allocator/tests/fixtures/single_disk_none_min.yaml vendored Normal file
View File

@ -0,0 +1,32 @@
name: First has no size preferences, second is min
dynamic_schema:
- id: lv1
type: lv
- id: lv2
type: lv
min_size: 20
- id: vg1
type: vg
contains:
- lv1
- lv2
hw_info:
disks:
- id: sda
size: 100
expected:
- disk_id: sda
size: 100
spaces:
# TODO figure out if this is expected behaviour
- space_id: lv1
size: 80
- space_id: lv2
size: 20
- space_id: unallocated
size: 0

0
bareon_dynamic_allocator/tests/fixtures/size_only.yaml → bareon_dynamic_allocator/tests/fixtures/single_disk_size_only.yaml vendored
View File