Skip to content

Commit e52a712

Browse files
Include review comments
1 parent dca56a9 commit e52a712

File tree

1 file changed

+12
-33
lines changed

1 file changed

+12
-33
lines changed

azure-managed-lustre/create-file-system-resource-manager.md

Lines changed: 12 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -12,33 +12,22 @@ ms.reviewer: mayabishop
1212

1313
# Create an Azure Managed Lustre file system by using Azure Resource Manager templates
1414

15-
You can automate the creation of an Azure Managed Lustre file system by using [Azure Resource Manager templates (ARM templates)](/azure/azure-resource-manager/templates/). This article explains the basic procedure and gives examples of the files that you need.
15+
You can automate the creation of an Azure Managed Lustre file system by using [Azure Resource Manager (ARM) templates](/azure/azure-resource-manager/templates/). This article explains the basic procedure and gives examples of the files that you need.
1616

17-
For more information about the templates, see [Azure Resource Manager templates](/azure/azure-resource-manager/templates/).
17+
This article gives examples of two different methods for creating ARM templates:
1818

19-
This article gives examples of two different methods for creating Azure Resource Manager templates:
20-
21-
* Use JSON to create Azure Resource Manager templates directly. To learn more, see [JSON template syntax](/azure/azure-resource-manager/templates/syntax).
22-
* Use [Bicep](/azure/azure-resource-manager/bicep/overview?tabs=bicep), which uses simpler syntax to supply the configuration details. When you deploy the template, the Bicep files are converted into Azure Resource Manager template files. To learn more, see [Bicep documentation](/azure/azure-resource-manager/bicep/).
19+
* Use JSON to create ARM templates directly. To learn more, see [JSON template syntax](/azure/azure-resource-manager/templates/syntax).
20+
* Use [Bicep](/azure/azure-resource-manager/bicep/overview?tabs=bicep), which uses simpler syntax to supply the configuration details. When you deploy the template, the Bicep files are converted into ARM template files. To learn more, see [Bicep documentation](/azure/azure-resource-manager/bicep/).
2321

2422
To learn more about these options, see [Comparing JSON and Bicep for templates](/azure/azure-resource-manager/bicep/compare-template-syntax).
2523

2624
## Choose file system type and size
2725

2826
Before you write a template, you must make some decisions about your Azure Managed Lustre file system. To learn more about the configuration options, see the setup details in [Create an Azure Managed Lustre file system](create-file-system-portal.md).
2927

30-
When you use a template, specify a **SKU name** to define the basic type of Azure Managed Lustre system to create. If you use the Azure portal to create your Azure Managed Lustre, you specify the system type indirectly by selecting its capabilities.
31-
32-
In Azure, the term **SKU** defines a set of features for the resource being created. For an Azure Managed Lustre file system, the SKU sets system properties such as the type of disks used, the amount of storage supported, and the maximum throughput capacity.
33-
34-
Currently, the following SKUs are supported:
35-
36-
* AMLFS-Durable-Premium-40
37-
* AMLFS-Durable-Premium-125
38-
* AMLFS-Durable-Premium-250
39-
* AMLFS-Durable-Premium-500
28+
When you use a template, specify a *SKU* name to define the basic type of Azure Managed Lustre file system to create. The SKU represents a product tier. It sets system qualities such as the type of disks, the supported amount of storage, and the maximum throughput capacity. If you use the Azure portal to create your Azure Managed Lustre file system, you specify the system type indirectly by selecting its capabilities.
4029

41-
These SKUs create a file system that uses durable SSD storage. The following table shows the throughput and storage size values for each SKU:
30+
The following table shows the values for throughput and storage size in each supported SKU. These SKUs create a file system that uses durable SSD storage.
4231

4332
| SKU | Throughput per TiB storage | Storage minimum | Storage maximum | Increment |
4433
|----------|-----------|-----------|-----------|-----------|
@@ -49,17 +38,15 @@ These SKUs create a file system that uses durable SSD storage. The following tab
4938

5039
If you require storage values larger than the listed maximum, you can [open a support ticket](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) to explore options.
5140

52-
You can use the [create workflow](create-file-system-portal.md) in Azure portal to check SKU capabilities. SKU-specific settings are on the **Basics** tab under **File system details**.
41+
To check SKU capabilities, you can use the [workflow for creating a Managed Lustre file system by using the Azure portal](create-file-system-portal.md). SKU-specific settings are on the **Basics** tab under **File system details**.
5342

5443
## Create a template file
5544

56-
Once you decide on configuration options, you can create a template file. The template file is a JSON or Bicep file that contains the configuration details for your Azure Managed Lustre file system. This section explains the property values you can use to configure your file system for deployment.
57-
58-
For example files that contain all possible configuration options, see [JSON example](#json-example) and [Bicep example](#bicep-example).
45+
After you decide on configuration options, you can create a template file. The template file is a JSON or Bicep file that contains the configuration details for your Azure Managed Lustre file system.
5946

6047
### Template property values
6148

62-
This section describes the information you need to include in your Azure Resource Manager template files to create an Azure Managed Lustre file system. The exact syntax is different between Bicep and JSON, so consult the examples for the literal values.
49+
To create an Azure Managed Lustre file system by using an ARM template, you need to include the following information in your template file. The exact syntax is different between Bicep and JSON, so consult the examples for the literal values.
6350

6451
#### File system
6552

@@ -137,15 +124,7 @@ This section describes the information you need to include in your Azure Resourc
137124

138125
## Deploy the file system by using the template
139126

140-
The following example steps use Azure CLI commands to create a new resource group and create an Azure Managed Lustre file system.
141-
142-
Before you deploy, make sure you complete the following steps:
143-
144-
* [Choose a file system type and size](#choose-file-system-type-and-size)
145-
* [Create a template file](#create-a-template-file)
146-
* Ensure that all [prerequisites](amlfs-prerequisites.md) are met.
147-
148-
Follow these steps to deploy the file system using the template:
127+
The following example steps use Azure CLI commands to create a new resource group and create an Azure Managed Lustre file system in it. The steps assume that you already [chose a file system type and size](#choose-file-system-type-and-size) and [created a template file](#create-a-template-file), as described earlier in this article. Also make sure that you meet all [prerequisites](amlfs-prerequisites.md).
149128

150129
1. Set your default subscription:
151130

@@ -185,7 +164,7 @@ Follow these steps to deploy the file system using the template:
185164

186165
## JSON example
187166

188-
This section shows sample contents for a JSON template file. You can remove optional parameters when creating your own Azure Resource Manager template.
167+
This section shows example contents for a JSON template file. You can remove optional parameters when creating your own ARM template.
189168

190169
```json
191170
{
@@ -251,7 +230,7 @@ This section shows sample contents for a JSON template file. You can remove opti
251230

252231
## Bicep example
253232

254-
This section shows sample contents for a Bicep file. You can remove optional parameters when creating your own.
233+
This section shows example contents for a Bicep file. You can remove optional parameters when creating your own.
255234

256235
```bicep
257236
resource filesystem 'Microsoft.StorageCache/amlFilesystems@2024-03-01' = {

0 commit comments

Comments
 (0)