Storage Account Limitation

[benofben]

We understand that storage accounts have a limit of 40 attached drives. This is forcing us to break nodes over different subnets for clusters greater than 40 nodes and introduces a lot of complexity.

We would really like to see this limitation abstracted away/otherwise removed in Azure as it will simplify the templates substantially.

[benofben]

We're working around this in main by generating the vm resources in Python. We no longer have the multiple subnet issue, but eliminating the 40 node restriction (or automatically allocating OS disks) would simplify things considerably.

[benofben]

It sounds like the need to manually specify a storage account for a VM is going away in the future, so this issue will become moot/abstracted away.

[benofben]

We're expecting the 40 drive storage account limitation to be abstracted away by a future release of vm scalesets. This is not yet available.

[benofben]

Apparently managed disks will fix this.

[benofben]

Managed disks are in preview right now. We need to assign someone to testing this.

[benofben]

Now wondering if the new H series machines will allow us to just sidestep this issue by using ephemeral.

[benofben]

It seems like the H8 and H16 might end up being our all around choice. The memory is still a bit high, but the disk sizes are good. https://azure.microsoft.com/en-us/blog/availability-of-h-series-vms-in-microsoft-azure/

[benofben]

We're doing a refactor to managed disks on 2/23/17 for OS disks. That should (finally) resolve this.