[
https://issues.apache.org/jira/browse/JCLOUDS-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260452#comment-16260452
]
Ignasi Barrera commented on JCLOUDS-1359:
-----------------------------------------
The {{minDisk}} attribute is used for image and hardware profile selection. In
many clouds, hardware profiles define the disk layout, and the {{minDisk}}
attribute is meant to let users select a hardware profile that provides the
configured minimum disk space. It is just for hardware profile selection.
In the case of GCE, that means jclouds will only take into account
{{MachineType}} objects that preconfigure disks with the given space, and the
same for Azure ARM and AWS.
Does this make more sense? With this in mind, are you experiencing issues with
hardware selection, where a hardware profile with "less disk than configured"
is selected?
> minDisk has no effect
> ---------------------
>
> Key: JCLOUDS-1359
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1359
> Project: jclouds
> Issue Type: Bug
> Reporter: Duncan Godwin
>
> It appears that {{minDisk}} has no effect when provisioning a machine. I
> expected it to produce a VM with the specified disk size on some clouds. I
> tested on AWS, GCE and Azure.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
