Merge pull request #102589 from erikadoyle/sf-ephemeraldisk

Add ephemeral disk SF usage info/examples

Author: ShannonLeavitt

articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md

@@ -36,18 +36,55 @@ See the minimum recommendations for [primary node types](service-fabric-cluster-
 
 Any more than the minimum number of nodes should be based on the number of replicas of the application/services that you want to run in this node type.  [Capacity planning for Service Fabric applications](service-fabric-capacity-planning.md) helps you estimate the resources you need to run your applications. You can always scale the cluster up or down later to adjust for changing application workload. 
 
-#### Use ephemeral OS disks for VM scale sets
+#### Use ephemeral OS disks for virtual machine scale sets
 
 *Ephemeral OS disks* are storage created on the local virtual machine (VM), and not saved to remote Azure Storage. They are recommended for all Service Fabric node types (Primary and Secondary), because compared to traditional persistent OS disks, ephemeral OS disks:
 
 * Reduce read/write latency to OS disk
 * Enable faster reset/reimage node management operations
 * Reduce overall costs (the disks are free and incur no additional storage cost)
 
-Ephemeral OS disks is not a specific Service Fabric feature, but rather a feature of the Azure *Virtual Machine scale sets* that are mapped to Service Fabric node types. See [Ephemeral OS disks for Azure VMs](../virtual-machines/windows/ephemeral-os-disks.md) for more info and instructions on configuring this VM feature.
+Ephemeral OS disks is not a specific Service Fabric feature, but rather a feature of the Azure *virtual machine scale sets* that are mapped to Service Fabric node types. Using them with Service Fabric requires the following in your cluster Azure Resource Manager template:
+
+1. Ensure your node types specify [supported Azure VM sizes](../virtual-machines/windows/ephemeral-os-disks.md) for  Ephemeral OS disks, and that the VM size has sufficient cache size to support its OS disk size (see *Note* below.) For example:
+
+    ```xml
+    "vmNodeType1Size": {
+        "type": "string",
+        "defaultValue": "Standard_DS3_v2"
+    ```
+
+    > [!NOTE]
+    > Be sure to select a VM size with a cache size equal or greater than the OS disk size of the VM itself, otherwise your Azure deployment might result in error (even if it's initially accepted).
+
+2. Specify a virtual machine scale set version (`vmssApiVersion`) of `2018-06-01` or later:
+
+    ```xml
+    "variables": {
+        "vmssApiVersion": "2018-06-01",
+    ```
+
+3. In the virtual machine scale set section of your deployment template, specify `Local` option for `diffDiskSettings`:
+
+    ```xml
+    "apiVersion": "[variables('vmssApiVersion')]",
+    "type": "Microsoft.Compute/virtualMachineScaleSets",
+        "virtualMachineProfile": {
+            "storageProfile": {
+                "osDisk": {
+                        "vhdContainers": ["[concat(reference(concat('Microsoft.Storage/storageAccounts/', parameters('vmStorageAccountName')), variables('storageApiVersion')).primaryEndpoints.blob, parameters('vmStorageAccountContainerName'))]"],
+                        "caching": "ReadOnly",
+                        "createOption": "FromImage",
+                        "diffDiskSettings": {
+                            "option": "Local"
+                        },
+                }
+            }
+        }
+    ```
+
+For more info and further configuration options, see [Ephemeral OS disks for Azure VMs](../virtual-machines/windows/ephemeral-os-disks.md) 
 
-> [!NOTE]
-> Be sure to select a VM size with a cache size equal or greater than the OS disk size of the VM itself, otherwise your ARM deployment might result in error (even if it's initially accepted).
 
 ### Select the durability and reliability levels for the cluster
 The durability tier is used to indicate to the system the privileges that your VMs have with the underlying Azure infrastructure. In the primary node type, this privilege allows Service Fabric to pause any VM level infrastructure request (such as a VM reboot, VM reimage, or VM migration) that impact the quorum requirements for the system services and your stateful services. In the non-primary node types, this privilege allows Service Fabric to pause any VM level infrastructure requests (such as VM reboot, VM reimage, and VM migration) that impact the quorum requirements for your stateful services.  For advantages of the different levels and recommendations on which level to use and when, see [The durability characteristics of the cluster][durability].