Skip to content

Commit 2fe228d

Browse files
committed
more acrolinx
1 parent 189b583 commit 2fe228d

File tree

2 files changed

+13
-13
lines changed

2 files changed

+13
-13
lines changed

articles/service-fabric/overview-managed-cluster.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ ms.date: 03/12/2024
1313

1414
Service Fabric managed clusters are an evolution of the Azure Service Fabric cluster resource model that streamlines your deployment and cluster management experience.
1515

16-
The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, all of which must be "wired up" correctly (upon deployment and throughout the lifecycle of the cluster) in order for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
16+
The Azure Resource Model (ARM) template for traditional Service Fabric clusters requires you to define a cluster resource alongside a number of supporting resources, These resources must be configured correctly for the cluster and your services to function properly. In contrast, the encapsulation model for Service Fabric managed clusters consists of a single, *Service Fabric managed cluster* resource. All of the underlying resources for the cluster are abstracted away and managed by Azure on your behalf.
1717

1818
**Service Fabric traditional cluster model**
1919
![Service Fabric traditional cluster model][sf-composition]
2020

2121
**Service Fabric managed cluster model**
2222
![Service Fabric encapsulated cluster model][sf-encapsulation]
2323

24-
In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1000 lines required to define a typical Service Fabric cluster:
24+
In terms of size and complexity, the ARM template for a Service Fabric managed cluster is about 100 lines of JSON, versus some 1,000 lines required to define a typical Service Fabric cluster:
2525

2626
| Service Fabric resources | Service Fabric managed cluster resources |
2727
|----------|-----------|
@@ -49,7 +49,7 @@ Service Fabric managed clusters provide a number of advantages over traditional
4949
**Best practices by default**
5050
- Simplified reliability and durability settings
5151

52-
There is no additional cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric SLA applies for managed clusters.
52+
There's no extra cost for Service Fabric managed clusters beyond the cost of underlying resources required for the cluster, and the same Service Fabric Service Leval Agreement (SLA) applies for managed clusters.
5353

5454
> [!NOTE]
5555
> There is no migration path from existing Service Fabric clusters to managed clusters. You will need to create a new Service Fabric managed cluster to use this new resource type.
@@ -64,15 +64,15 @@ Service Fabric managed clusters are available in both Basic and Standard SKUs.
6464
| Feature | Basic | Standard |
6565
| ------- | ----- | -------- |
6666
| Network resource (SKU for [Load Balancer](../load-balancer/skus.md), [Public IP](../virtual-network/ip-services/public-ip-addresses.md)) | Basic | Standard |
67-
| Min node (VM instance) count | 3 | 5 |
67+
| Min node (virtual machine instance) count | 3 | 5 |
6868
| Max node count per node type | 100 | 1000 |
6969
| Max node type count | 1 | 50 |
7070
| Add/remove node types | No | Yes |
7171
| Zone redundancy | No | Yes |
7272

7373
## Feature support
7474

75-
The capabilities of managed clusters will continue to expand. See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
75+
See [managed cluster configuration options documentation](how-to-managed-cluster-configuration.md) or managedClusters [Bicep & ARM templates](/azure/templates/microsoft.servicefabric/allversions) for more information.
7676

7777

7878
## Next steps

articles/service-fabric/tutorial-managed-cluster-deploy.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Deploy a Service Fabric managed cluster
3-
description: In this tutorial, you will deploy a Service Fabric managed cluster for testing.
3+
description: In this tutorial, you deploy a Service Fabric managed cluster for testing.
44
ms.topic: tutorial
55
ms.author: tomcassidy
66
author: tomvcassidy
@@ -11,7 +11,7 @@ ms.date: 03/12/2024
1111

1212
# Tutorial: Deploy a Service Fabric managed cluster
1313

14-
In this tutorial series we will discuss:
14+
In this tutorial series, we discuss:
1515

1616
> [!div class="checklist"]
1717
> * How to deploy a Service Fabric managed cluster
@@ -31,7 +31,7 @@ This part of the series covers how to:
3131

3232
Before you begin this tutorial:
3333

34-
* Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) if you don't already have an Azure subscription
34+
* Create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) if you don't already have an Azure subscription.
3535

3636
* Install the [Service Fabric SDK and PowerShell module](service-fabric-get-started.md).
3737

@@ -62,14 +62,14 @@ New-AzResourceGroup -Name $resourceGroup -Location $location
6262

6363
### Create a Service Fabric managed cluster
6464

65-
In this step, you will create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
65+
In this step, you create a Service Fabric managed cluster using the New-AzServiceFabricManagedCluster PowerShell command. The following example creates a cluster named myCluster in the resource group named myResourceGroup. This resource group was created in the previous step in the eastus2 region.
6666

6767
For this step, provide your own values for the following parameters:
6868

6969
* **Cluster Name**: Enter a unique name for your cluster, such as *mysfcluster*.
70-
* **Admin Password**: Enter a password for the admin to be used for RDP on the underlying VMs in the cluster.
71-
* **Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you do not have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
72-
* **Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and do not allow for node type addition or removal.
70+
* **Admin Password**: Enter a password for the admin to be used for Remote Desktop Protocol (RDP) on the underlying VMs in the cluster.
71+
* **Client Certificate Thumbprint**: Provide the thumbprint of the client certificate that you would like to use to access your cluster. If you don't have a certificate, follow [set and retrieve a certificate](../key-vault/certificates/quick-create-portal.md) to create a self-signed certificate.
72+
* **Cluster SKU**: Specify the [type of Service Fabric managed cluster](overview-managed-cluster.md#service-fabric-managed-cluster-skus) to deploy. *Basic* SKU clusters are meant for test deployments only, and don't allow for node type addition or removal.
7373

7474
```powershell
7575
$clusterName = "<unique cluster name>"
@@ -82,7 +82,7 @@ New-AzServiceFabricManagedCluster -ResourceGroupName $resourceGroup -Location $l
8282

8383
### Add a primary node type to the Service Fabric managed cluster
8484

85-
In this step, you will add a primary node type to the cluster that you have just created. Every Service Fabric cluster must have at least one primary node type.
85+
In this step, you add a primary node type to the cluster that you created. Every Service Fabric cluster must have at least one primary node type.
8686

8787
For this step, provide your own values for the following parameters:
8888

0 commit comments

Comments
 (0)