jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilkka Salento <notificati...@github.com>
Subject Re: [jclouds/jclouds-labs] JCLOUDS-664 Azurecompute-arm DeploymentApi OSImageApi VMSizeApi (#273)
Date Thu, 26 May 2016 09:57:21 GMT
> +      variables.put("osDiskName", osDiskName);
> +
> +      OSDisk osDisk = OSDisk.builder()
> +              .name("[variables('osDiskName')]")
> +              .vhd(
> +                      VHD.create("[concat('http://',variables('storageAccountName'),'.blob.core.windows.net/',variables('storageAccountContainerName'),'/',variables('osDiskName'),'.vhd')]")
> +              )
> +              .caching("ReadWrite")
> +              .createOption("FromImage")
> +              .build();
> +
> +
> +      //Create Data Disk(s) and add to list
> +      final String dataDiskName = name + "datadisk";
> +      variables.put("dataDiskName", dataDiskName);
> +      final String dataDiskSize = "100";

Hi, Yes eventually data disk information (number of disks and their sizes) should be set using
template option. In Azure the number of supported data disks depends on hardware in use, but
the max size for singe disk is 1023 GB. Should we just drop data disk creation until Azure
template option has support for it or create a singe data disk using 1023 as default size?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/273/files/74f8e9bf66e7427298c5c3c9567aa7d8284e0987#r64720067
Mime
View raw message