Launching the Worker Node VMs in Azure

You add capacity to an existing cluster by launching additional VMs for the DL-worker and DA-worker nodes. As with the DL-m and DA-m, you launch Azure VMs by running an installation script in the Azure Cloud Shell rather than by stepping through a console wizard.

You use the same DP image and the same installation script for a worker node that you used for the DL-m and DA-m. There is no separate image or instance type for a worker. The node becomes a DL-worker or a DA-worker when you assign its role later, in the CLI and the Stellar Cyber user interface.

Use our example as a guideline, as you might be using a different software version.

Run the installation script once for each worker node you are adding:

Log in to the Azure Portal.
Click the Cloud Shell button to bring up a PowerShell window.
Paste the contents of the Azure Installation Script into a text editor.
Customize the script with variable definitions that match your Azure subscription and networking environment for the items listed in Variables for the Azure Installation Script. Use the same Resource Group, virtual network, subnet, and Network Security Group you used for the DL-m and DA-m.
Set the $stellarInstanceType variable for a Data Processor. Uncomment the line with $stellarInstanceType set to "Stellar-DataProcessor" and comment out the line with $stellarInstanceType set to "Stellar-ModularSensor-Gen2". For example:
Copy
```
#$stellarInstanceType = "Stellar-ModularSensor-Gen2"
$stellarInstanceType = "Stellar-DataProcessor"
```
Set $vmNamePrefix to a meaningful name that reminds you of the node's intended role. For example, dl-worker or da-worker.
Provision the VM according to the specifications for the type of node you are launching (DL-worker or DA-worker) in VM Specifications for Public Cloud Deployments (AWS, Azure, GCP, OCI).

Stellar Cyber only supports full-SSD deployments. Spinning-disk-based storage (HDD) and hybrid drives (SSHD) are not supported. All deployments must adhere to this SSD-only policy in order to qualify for performance guarantees and technical support.
Refer to Stellar Cyber Requires Full SSD Disks for further details.

Storage must meet or exceed the following sustained minimum performance metrics for 4KB random data operations:
- Write IOPS: > 30,000
- Read IOPS: > 60,000
- Throughput: > 500 MB/s (read/write)
Copy and paste the customized script into the Azure Cloud Shell to create the VM.
If you are launching a DL-worker, add a second storage disk sized between 8-16 TB, as stated in VM Specifications for Public Cloud Deployments (AWS, Azure, GCP, OCI).
Repeat this procedure for each additional worker node in your deployment, changing $vmNamePrefix and the provisioning to match.

The worker node VMs are now running in the Azure cloud. The next step is to configure them in their respective CLIs.