Support the new L vm series #107
Comments
What is all required for this? We are looking to setup a new cluster on L series |
Looking to add these now |
Any update on this? |
@shaharmor most of the work has been done in the feature/l-series branch. The way in which the number of nodes per storage account needs to changed to accommodate the Standard_L32s sku that can have up to 64 disks attached per VM. Right now, the implementation assumes the maximum for any sku is 40, using this as the basis for determining how many storage accounts are required for the nodes. A lot of this template complexity is alleviated by using managed disks, which also allows encryption at rest, something that cannot be achieved currently with the Azure Disk Encryption implementation limitations. The desire is to use managed disks for potentially all attached disks but we need to investigate this further. |
Why not release this with a limitation on the number of disks, so we can at least use this deployment with a lower number of disks? |
Is there any progress on this? The L-series are very useful for deploying elastic on and have been available for more than a year now. Even without allowing 64 disks, support would be helpful. (Support for 64 disks could be added later?) |
with the move to managed disks, support for L-series VMs is now much easier. I'll look to add support in the next release |
This commit adds other available VM SKUs such as L-Series VMs. Closes #107
This commit adds other available VM SKUs such as L-Series VMs. Closes #107
This commit adds other available VM SKUs such as L-Series VMs. Closes #107
No description provided.
The text was updated successfully, but these errors were encountered: