You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-concept-resource-model.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ ms.custom: sfrev
8
8
9
9
# Service Fabric application resource model
10
10
11
-
You have multiple options for deploying Service Fabric applications on your Service Fabric cluster. We recommend using Azure Resource Manager. If you use Resource Manager, you can describe applications and services in JSON, and then deploy them in the same Resource Manager template as your cluster. Unlike using PowerShell or Azure CLI to deploy and manage applications, if you use Resource Manager, you don't have to wait for the cluster to be ready; application registration, provisioning, and deployment can all happen in one step. Using Resource Manager is the best way to manage the application life cycle in your cluster. For more information, see [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources).
11
+
You have multiple options for deploying Azure Service Fabric applications on your Service Fabric cluster. We recommend using Azure Resource Manager. If you use Resource Manager, you can describe applications and services in JSON, and then deploy them in the same Resource Manager template as your cluster. Unlike using PowerShell or Azure CLI to deploy and manage applications, if you use Resource Manager, you don't have to wait for the cluster to be ready; application registration, provisioning, and deployment can all happen in one step. Using Resource Manager is the best way to manage the application life cycle in your cluster. For more information, see [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources).
12
12
13
13
Managing your applications as resources in Resource Manager can help you gain improvements in these areas:
14
14
@@ -33,7 +33,7 @@ The high-level steps you take to deploy an application and its services by using
33
33
34
34
For more information, view [Package an application](service-fabric-package-apps.md#create-an-sfpkg).
35
35
36
-
Then, you create a Resource Manager template, update the parameters file with application details, and then deploy the template on the Service Fabric cluster. Explore [samples](https://github.com/Azure-Samples/service-fabric-dotnet-quickstart/tree/master/ARM).
36
+
Then, you create a Resource Manager template, update the parameters file with application details, and deploy the template on the Service Fabric cluster. [Explore samples](https://github.com/Azure-Samples/service-fabric-dotnet-quickstart/tree/master/ARM).
37
37
38
38
### Create a storage account
39
39
@@ -180,7 +180,7 @@ Get information about the application resource model:
180
180
* [Model an application in Service Fabric](service-fabric-application-model.md)
181
181
* [Service Fabric application and service manifests](service-fabric-application-and-service-manifests.md)
182
182
* [Best practices: Infrastructure as code](service-fabric-best-practices-infrastructure-as-code.md#azure-service-fabric-resources)
183
-
* [Manage applications and services as Azure Resources](service-fabric-best-practices-infrastructure-as-code.md)
183
+
* [Manage applications and services as Azure resources](service-fabric-best-practices-infrastructure-as-code.md)
0 commit comments