Skip to content

Commit 06a9772

Browse files
authored
Update disconnected-operations-deploy.md
Removed unnecessary spaces
1 parent 161cf38 commit 06a9772

File tree

1 file changed

+14
-16
lines changed

1 file changed

+14
-16
lines changed

azure-local/manage/disconnected-operations-deploy.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -103,20 +103,20 @@ To prepare each machine for the disconnected operations appliance, follow these
103103
104104
1. Check and make sure you have sufficient disk space for disconnected operations deployment.
105105
106-
Make sure you have at least 600 GB of free space on the drive you plan to use for deployment. If your drive has less space, use a data disk on each node and initialize it so each node has the same available data disks for deployment.
106+
Make sure you have at least 600 GB of free space on the drive you plan to use for deployment. If your drive has less space, use a data disk on each node and initialize it so each node has the same available data disks for deployment.
107107
108108
109109
Here’s how to initialize a disk on the nodes and format it for a D partition:
110110
111-
```powershell
112-
$availableDrives = Get-PhysicalDisk | Where-Object { $_.MediaType -eq "SSD" -or $_.MediaType -eq "NVMe" } | where -Property CanPool -Match "True" | Sort-Object Size -Descending
113-
$driveGroup = $availableDrives | Group-Object Size | select -First 1
114-
$biggestDataDrives = $availableDrives | select -First $($driveGroup.Count)
115-
$firstDataDrive= ($biggestDataDrives | Sort-Object DeviceId | select -First 1).DeviceId
116-
Initialize-Disk -Number $firstDataDrive
117-
New-partition -disknumber $firstDataDrive -usemaximumsize | format-volume -filesystem NTFS -newfilesystemlabel Data
118-
Get-partition -disknumber $firstDataDrive -PartitionNumber 2 | Set-Partition -NewDriveLetter D
119-
```
111+
```powershell
112+
$availableDrives = Get-PhysicalDisk | Where-Object { $_.MediaType -eq "SSD" -or $_.MediaType -eq "NVMe" } | where -Property CanPool -Match "True" | Sort-Object Size -Descending
113+
$driveGroup = $availableDrives | Group-Object Size | select -First 1
114+
$biggestDataDrives = $availableDrives | select -First $($driveGroup.Count)
115+
$firstDataDrive= ($biggestDataDrives | Sort-Object DeviceId | select -First 1).DeviceId
116+
Initialize-Disk -Number $firstDataDrive
117+
New-partition -disknumber $firstDataDrive -usemaximumsize | format-volume -filesystem NTFS -newfilesystemlabel Data
118+
Get-partition -disknumber $firstDataDrive -PartitionNumber 2 | Set-Partition -NewDriveLetter D
119+
```
120120
121121
1. On each node, copy the root certificate public key. For more information, see [PKI for disconnected operations](disconnected-operations-pki.md). Modify the paths according to the location and method you use to export your public key for creating certificates.
122122
@@ -240,8 +240,6 @@ To prepare the first machine for the disconnected operations appliance:
240240
$ingressCertFolderPath = "$certspath\IngressEndpointCerts"
241241
```
242242
243-
244-
245243
## Initialize the parameters
246244
247245
Populate the required parameters based on your deployment planning. Modify the examples to match your configuration.
@@ -453,8 +451,6 @@ Test-SSLCertificateSAN -HostName $HostName -SslCertificate $SslCertificate | Out
453451
Test-SSLCertificateChain -SslCertificate $SslCertificate | Out-Null
454452
Test-SslCertificateEnhancedKeyUsage -SslCertificate $SslCertificate | Out-Null
455453
Test-SslCertificateCrypto -SslCertificate $SslCertificate | Out-Null
456-
457-
458454
```
459455

460456
## Install and configure the appliance
@@ -599,7 +595,8 @@ Use the operator account to create an SPN for Arc initialization of each Azure L
599595
> Don't place the cluster resource in the operator subscription, unless you plan to restrict this to only operators with full access to other operations. You can create more subscriptions or place it in the starter subscription.
600596
601597
602-
### Initialize each node
598+
### Initialize each node
599+
603600
To initialize each node, follow these steps. Modify where necessary to match your environment details:
604601
605602
1. Set the configuration variable. Define the resource group, cloud name, configuration path, application ID, client secret, and appliance FQDN.
@@ -614,7 +611,6 @@ To initialize each node, follow these steps. Modify where necessary to match you
614611
615612
1. Initialize each node.
616613
617-
618614
```powershell
619615
Write-Host "az login to Disconnected operations cloud"
620616
az cloud set -n $applianceCloudName --only-show-errors
@@ -720,11 +716,13 @@ w32tm /query /peers
720716
Place them in a folder, e.g.C:\AzureLocalDisconnectedOperations\Certs\
721717

722718
Import the certs by running the following:
719+
723720
```powershell
724721
Import-Certificate -FilePath C:\AzureLocalDisconnectedOperations\Certs\MicCodSigPCA2011_2011-07-08.cer -CertStoreLocation Cert:\LocalMachine\Root -Confirm:$false
725722
Import-Certificate -FilePath C:\AzureLocalDisconnectedOperations\Certs\DigiCertGlobalRootCA.cer Cert:\LocalMachine\Root -Confirm:$false
726723
Import-Certificate -FilePath C:\AzureLocalDisconnectedOperations\Certs\DigiCertGlobalRootG2.cer -CertStoreLocation Cert:\LocalMachine\Root -Confirm:$false
727724
```
725+
728726
### Create the Azure Local instance (cluster)
729727

730728
With the prerequisites completed, you can deploy Azure Local with a fully air-gapped local control plane.

0 commit comments

Comments
 (0)