@aledsage This adds support for hardwareId, so by default jclouds will now use hardwareProfile defined as usual.
It also introduces VCloudTemplateOptions.memory and `VCloudTemplateOptions.virtualCpus custom template options. These are intended to give fine-grain control on the hardware spec.
If hardwareId and VCloudTemplateOptions.memory or VCloudTemplateOptions.virtualCpus are defined, VCloudTemplateOptions will override the values of the hardwareId
Notice an hardwareId is always chosen by jclouds under the covers.
@aledsage This adds support for hardwareId, so by default jclouds will now use hardwareProfile defined as usual. It also introduces
VCloudTemplateOptions.memory
and`VCloudTemplateOptions.virtualCpus
custom template options. These are intended to give fine-grain control on the hardware spec.If
hardwareId
andVCloudTemplateOptions.memory
orVCloudTemplateOptions.virtualCpus
are defined,VCloudTemplateOptions
will override the values of thehardwareId
Notice anhardwareId
is always chosen by jclouds under the covers.