Skip to content

Commit 19deddd

Browse files
ktoliverktoliver
authored
Merge pull request #44243 from Meghna-Chauhan/patch-1
AddNode.ps1 execution parameters modified
2 parents ffb7031 + 4421533 commit 19deddd

File tree

1 file changed

+47
-27
lines changed

1 file changed

+47
-27
lines changed

‎articles/service-fabric/service-fabric-cluster-windows-server-add-remove-nodes.md

Lines changed: 47 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
---
1+
---
22
title: Add or remove nodes to a standalone Service Fabric cluster
33
description: Learn how to add or remove nodes to an Azure Service Fabric cluster on a physical or virtual machine running Windows Server, which could be on-premises or in any cloud.
44
author: dkkapur
@@ -12,36 +12,56 @@ After you have [created your standalone Service Fabric cluster on Windows Server
1212

1313
## Add nodes to your cluster
1414

15-
1. Prepare the VM/machine you want to add to your cluster by following the steps outlined in [Plan and prepare your Service Fabric cluster deployment](service-fabric-cluster-creation-for-windows-server.md)
16-
2. Identify which fault domain and upgrade domain you are going to add this VM/machine to
17-
3. Remote desktop (RDP) into the VM/machine that you want to add to the cluster
18-
4. Copy or [download the standalone package for Service Fabric for Windows Server](https://go.microsoft.com/fwlink/?LinkId=730690) to the VM/machine and unzip the package
19-
5. Run Powershell with elevated privileges, and navigate to the location of the unzipped package
20-
6. Run the *AddNode.ps1* script with the parameters describing the new node to add. The example below adds a new node called VM5, with type NodeType0 and IP address 182.17.34.52, into UD1 and fd:/dc1/r0. The *ExistingClusterConnectionEndPoint* is a connection endpoint for a node already in the existing cluster, which can be the IP address of *any* node in the cluster.
15+
1. Prepare the VM/machine you want to add to your cluster by following the steps outlined in [Plan and prepare your Service Fabric cluster deployment](service-fabric-cluster-standalone-deployment-preparation.md).
2116

22-
```
23-
.\AddNode.ps1 -NodeName VM5 -NodeType NodeType0 -NodeIPAddressorFQDN 182.17.34.52 -ExistingClientConnectionEndpoint 182.17.34.50:19000 -UpgradeDomain UD1 -FaultDomain fd:/dc1/r0 -AcceptEULA
24-
```
25-
Once the script finishes running, you can check if the new node has been added by running the [Get-ServiceFabricNode](/powershell/module/servicefabric/get-servicefabricnode?view=azureservicefabricps) cmdlet.
17+
2. Identify which fault domain and upgrade domain you are going to add this VM/machine to.
2618

27-
7. To ensure consistency across different nodes in the cluster, you must initiate a configuration upgrade. Run [Get-ServiceFabricClusterConfiguration](/powershell/module/servicefabric/get-servicefabricclusterconfiguration?view=azureservicefabricps) to get the latest configuration file and add the newly added node to "Nodes" section. It is also recommended to always have the latest cluster configuration available in the case that you need to redeploy a cluster with the same configuration.
19+
If you use certificates to secure the cluster, certificates are expected to be installed in the local certificate stores in preparation for the node to join the cluster. The analog is applicable when using other forms of security.
20+
21+
3. Remote desktop (RDP) into the VM/machine that you want to add to the cluster.
22+
23+
4. Copy or [download the standalone package for Service Fabric for Windows Server](https://go.microsoft.com/fwlink/?LinkId=730690) to the VM/machine and unzip the package.
24+
25+
5. Run PowerShell with elevated privileges and go to the location of the unzipped package.
26+
27+
6. Run the *AddNode.ps1* script with the parameters describing the new node to add. The following example adds a new node called VM5, with type NodeType0 and IP address 182.17.34.52, into UD1 and fd:/dc1/r0. `ExistingClusterConnectionEndPoint` is a connection endpoint for a node already in the existing cluster, which can be the IP address of *any* node in the cluster.
28+
29+
Unsecure (prototyping):
30+
31+
```
32+
.\AddNode.ps1 -NodeName VM5 -NodeType NodeType0 -NodeIPAddressorFQDN 182.17.34.52 -ExistingClientConnectionEndpoint 182.17.34.50:19000 -UpgradeDomain UD1 -FaultDomain fd:/dc1/r0 -AcceptEULA
33+
```
34+
35+
Secure (certificate-based):
36+
37+
```
38+
$CertThumbprint= "***********************"
39+
40+
.\AddNode.ps1 -NodeName VM5 -NodeType NodeType0 -NodeIPAddressorFQDN 182.17.34.52 -ExistingClientConnectionEndpoint 182.17.34.50:19000 -UpgradeDomain UD1 -FaultDomain fd:/dc1/r0 -X509Credential -ServerCertThumbprint $CertThumbprint -AcceptEULA
41+
42+
```
43+
44+
When the script finishes running, you can check whether the new node has been added by running the [Get-ServiceFabricNode](/powershell/module/servicefabric/get-servicefabricnode?view=azureservicefabricps) cmdlet.
45+
46+
7. To ensure consistency across different nodes in the cluster, you must initiate a configuration upgrade. Run [Get-ServiceFabricClusterConfiguration](/powershell/module/servicefabric/get-servicefabricclusterconfiguration?view=azureservicefabricps) to get the latest configuration file and add the newly added node to the "Nodes" section. It is also recommended to always have the latest cluster configuration available in case you need to redeploy a cluster that has the same configuration.
47+
48+
```
49+
{
50+
"nodeName": "vm5",
51+
"iPAddress": "182.17.34.52",
52+
"nodeTypeRef": "NodeType0",
53+
"faultDomain": "fd:/dc1/r0",
54+
"upgradeDomain": "UD1"
55+
}
56+
```
2857

29-
```
30-
{
31-
"nodeName": "vm5",
32-
"iPAddress": "182.17.34.52",
33-
"nodeTypeRef": "NodeType0",
34-
"faultDomain": "fd:/dc1/r0",
35-
"upgradeDomain": "UD1"
36-
}
37-
```
3858
8. Run [Start-ServiceFabricClusterConfigurationUpgrade](/powershell/module/servicefabric/start-servicefabricclusterconfigurationupgrade?view=azureservicefabricps) to begin the upgrade.
3959

40-
```
41-
Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath <Path to Configuration File>
60+
```
61+
Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath <Path to Configuration File>
62+
```
4263

43-
```
44-
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-​Service​Fabric​Cluster​Upgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps)
64+
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-ServiceFabricClusterUpgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps).
4565

4666
### Add nodes to clusters configured with Windows Security using gMSA
4767
For clusters configured with Group Managed Service Account(gMSA)(https://technet.microsoft.com/library/hh831782.aspx), a new node can be added using a configuration upgrade:
@@ -61,7 +81,7 @@ For clusters configured with Group Managed Service Account(gMSA)(https://technet
6181
```
6282
Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath <Path to Configuration File>
6383
```
64-
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-​Service​Fabric​Cluster​Upgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps)
84+
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-ServiceFabricClusterUpgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps)
6585

6686
### Add node types to your cluster
6787
In order to add a new node type, modify your configuration to include the new node type in "NodeTypes" section under "Properties" and begin a configuration upgrade using [Start-ServiceFabricClusterConfigurationUpgrade](/powershell/module/servicefabric/start-servicefabricclusterconfigurationupgrade?view=azureservicefabricps). Once the upgrade completes, you can add new nodes to your cluster with this node type.
@@ -99,7 +119,7 @@ Add the "NodesToBeRemoved" parameter to "Setup" section inside "FabricSettings"
99119
Start-ServiceFabricClusterConfigurationUpgrade -ClusterConfigPath <Path to Configuration File>
100120

101121
```
102-
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-​Service​Fabric​Cluster​Upgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps)
122+
You can monitor the progress of the upgrade on Service Fabric Explorer. Alternatively, you can run [Get-ServiceFabricClusterUpgrade](/powershell/module/servicefabric/get-servicefabricclusterupgrade?view=azureservicefabricps).
103123

104124
> [!NOTE]
105125
> Removal of nodes may initiate multiple upgrades. Some nodes are marked with `IsSeedNode=”true”` tag and can be identified by querying the cluster manifest using `Get-ServiceFabricClusterManifest`. Removal of such nodes may take longer than others since the seed nodes will have to be moved around in such scenarios. The cluster must maintain a minimum of 3 primary node type nodes.

0 commit comments

Comments
 (0)