forked from areznikov-kabam/ephemeral_lvm
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy path.kitchen.yml
More file actions
89 lines (86 loc) · 2.46 KB
/
.kitchen.yml
File metadata and controls
89 lines (86 loc) · 2.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
---
driver_plugin: vagrant
driver_config:
require_chef_omnibus: 11.6.0
platforms:
- name: centos-5.9
driver_config:
box: opscode-centos-5.9
- name: centos-6.5
driver_config:
box: opscode-centos-6.5
- name: centos-7.0
driver_config:
box: opscode-centos-7.0
attributes:
ephemeral_lvm:
filesystem: xfs
- name: centos-7.1
driver_config:
box: opscode-centos-7.1
attributes:
ephemeral_lvm:
filesystem: xfs
- name: debian-7.2.0
driver_config:
box: opscode-debian-7.2.0
- name: rhel-6.5
driver_config:
box: local-rhel-6.5
box_url: file://<%= File.expand_path('~') %>/opscode_rhel-6.5_chef-provisionerless.box
- name: rhel-7.1
driver_config:
box: opscode-rhel-7.1
box_url: https://s3.amazonaws.com/st-vagrant-boxes/opscode_rhel-7.1_chef-provisionerless.box
attributes:
ephemeral_lvm:
filesystem: xfs
- name: ubuntu-10.04
driver_config:
box: opscode-ubuntu-10.04
- name: ubuntu-12.04
driver_config:
box: opscode-ubuntu-12.04
- name: ubuntu-14.04
driver_config:
box: opscode-ubuntu-14.04
suites:
# This test suite mimics the behavior of being in a cloud which supports block device mapping
# The loopback devices given in block_device_mapping_ephemeral<N> should be included in
# the test/cookbooks/fake cookbook's attributes so they get created while running
# the test. EC2 and openstack clouds follow this format.
#
- name: default
run_list: ["recipe[fake]", "recipe[ephemeral_lvm]"]
attributes:
cloud:
provider: vagrant
vagrant:
block_device_mapping_ephemeral0: loop0
block_device_mapping_ephemeral1: loop1
# This test mimics the behavior of being in a google compute engine. The ephemeral disks
# are mapped to /dev/disk/by-id/google-ephemeral-disk-<N>. Loopback device matching the
# device index should be set in the test/cookbooks/fake cookbook's attributes
# so they get created. For example, the following attributes will require the creation of
# loopback devices "/dev/loop0" and "/dev/loop1"
#
- name: gce
run_list: ["recipe[fake::gce]", "recipe[ephemeral_lvm]"]
attributes:
cloud:
provider: gce
gce:
attached_disks:
disks:
- deviceName: boot
index: 0
mode: READ_WRITE
type: EPHEMERAL
- deviceName: ephemeral-disk-0
index: 1
mode: READ_WRITE
type: EPHEMERAL
- deviceName: ephemeral-disk-1
index: 2
mode: READ_WRITE
type: EPHEMERAL