You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ platforms:
64
64
### Configure Transport
65
65
66
66
In case you need to create both Linux and Windows machines, then different transport types have to be used(ssh for linux and winrm for windows).
67
-
For easier maintenance and cleaner configuration you can create global kitchen configuration under $HOME/<username>/.kitchen/config.yml with following contents:
67
+
For easier maintenance and cleaner configuration you can create global kitchen configuration under $HOME/[username]/.kitchen/config.yml with following contents:
68
68
69
69
```yaml
70
70
<% WINRM_USERNAME = 'winrm_user' %>
@@ -79,7 +79,7 @@ transport:
79
79
# example: winrm_transport
80
80
```
81
81
82
-
Then in your kitchen.yml specify transport either for platform or suite
82
+
Then in your cookbook specific kitchen.yml configure transport either for platform or suite
83
83
```yaml
84
84
suites:
85
85
- name: windows-basic
@@ -136,6 +136,17 @@ suites:
136
136
vm_name: 'my-vm-in-vmm'
137
137
```
138
138
139
+
* #### vm_name_prefix
140
+
141
+
Prefix for VM name, all created VMs are going to have name prepended with the specified prefix.
142
+
143
+
```yaml
144
+
driver_config:
145
+
...
146
+
vm_name_prefix: tst-
147
+
```
148
+
149
+
139
150
* #### vm_hardware_profile
140
151
141
152
Specify alternate HW profile that should be used instead of the one provided in your original template.
0 commit comments