README.md in chef-provisioning-vsphere-0.7.2 vs README.md in chef-provisioning-vsphere-0.8.0
- old
+ new
@@ -82,11 +82,11 @@
- `[:num_cpus]` - number of cpus to allocate to machine
- `[:network_name]` - array of network names to use. A NIC will be added for each
- `[:memory_mb]` - number of megabytes to allocate for machine
- `[:host]` - `{cluster}`/`{host}` to use during provisioning
- `[:resource_pool]` - `{cluster}`/`{resource pool}` to use during provisioning
-- `[:additional_disk_size_gb]` - if provided an additional disk will be added with the specified number of gigabytes (*his requires a datastore to be specified*)
+- `[:additional_disk_size_gb]` - an array of numbers, each signifying the number of gigabytes to assign to an additional disk (*his requires a datastore to be specified*)
- `[:ssh][:user]` user to use for ssh/winrm (defaults to root on linux/administrator on windows)
- `[:ssh][:password]` - password to use for ssh/winrm
- `[:ssh][:paranoid]` - specifies the strictness of the host key verification checking
- `[:ssh][:port]` port to use for ssh/winrm (defaults to 22 for ssh or 5985 for winrm)
- `[:convergence_options][:install_msi_url]` - url to chef client msi to use (defaults to latest)
@@ -111,11 +111,11 @@
- `create_timeout` - number of seconds to wait for a machine to be accessible after initiating provisioning (default 10 minutes)
- `ready_timeout` - number of seconds to wait for customization to complete and vmware tools to come on line (default 5 minutes)
## More config examples
-### Static IP and an additional 50GB disk
+### Static IP and two additional disks of 20 and 50GB
```
with_machine_options :bootstrap_options => {
use_linked_clone: true,
num_cpus: 2,
@@ -123,10 +123,10 @@
network_name: ["vlan_20_172.21.20"],
datacenter: 'datacenter_name',
resource_pool: 'cluster',
template_name: 'path to template',
datastore: "my_data_store",
- additional_disk_size_gb: 50,
+ additional_disk_size_gb: [50,20],
customization_spec: {
ipsettings: {
ip: '192.168.3.4',
subnetMask: '255.255.255.0',
gateway: ["192.168.3.1"],