Configuring Worker Nodes in the CLI

Once you have launched instances for the DL and DA worker nodes, you are ready to configure them in the CLI:

  1. Get IP Addresses for VMs

  2. Configure the DL-Worker Node in the CLI

  3. Configure the DA-Worker Node in the CLI

Get IP Addresses for VMs

When the VMs for your deployment are up and running, you are ready to log in to CLIs and configure them.

First, however, you need the IP addresses that AWS assigned when you launched your instances:

  1. Log in to your EC2 Dashboard.

  2. Click on Instances. The active instances appear.

  3. Check the box for an instance to view its Details in the lower panel.

  4. Copy the Public IP, Private IP, and Private DNS.
  5. Repeat this procedure for the other instance.

Configure the DL-Worker Node in the CLI

Use the following procedure to configure the DL-Worker node in its CLI:

  1. Access the console of the DL-worker VM using the private IP address you copied in the previous procedure.

  2. Log in. The default user/password is aella/changeme. You are immediately prompted to change the password.

  3. Change the password.

  4. Reconnect to the DL-worker VM using the new password you just set.

  5. The prompt changes to DataProcessor>.

  6. Enter the following command:

    show hostname

  7. The default hostname in public cloud environments typically includes the private IP address of the host and may not be immediately meaningful when you see it later on in the Stellar Cyber user interface. You can change it to something meaningful using the set hostname <hostname> command. For example:

    DataProcessor> set hostname DL-worker

    If you do change the hostname, you must reboot the virtual machine to apply the change.

  8. Set the role of the VM to resource as follows:

    DataProcessor> set role resource

  9. AWS automatically configures DNS and NTP settings for the VM. You can verify the settings with the show dns and show ntp commands, respectively.

  10. Configure the DL-worker VM to use the secondary disk you attached in AWS as follows:

    1. Run the show storage command to get the name of the secondary disk. For example:

    2. Use the add storage blk <disk_name> command to add the secondary disk, followed by Y to confirm. For example:

    3. Use the show storage command to verify the newly added disk:

  11. Use the set cm <ip_address> command to set the IP address of the Data Lake master's management interface as follows:

    1. Retrieve the private IP address of the DL-Master using the Instances list in the AWS Console.

    2. Enter the following command using the IP address you just retrieved:

      DataProcessor> set cm <private_ip_address of DL-m>

  12. Enable the Maximized Data Storage (MDS) option:

    DataProcessor> set mode MDS enable

    You can use the show mode command to see the current setting for the MDS option.

    The MDS option specifies whether the node stores data itself (enabled) or only manages storage and ElasticSearch operations (disabled). As you scale up to a cluster deployment with three or more DL-worker nodes, you disable MDS on the DL-Master and provision it with less disk space. The DL-worker nodes have MDS enabled and handle the actual storage while the DL-master provides storage management and search.

  13. Use the reset command to apply your changes. This command starts all Stellar Cyber microservices using your new settings.

  14. Confirm the reset. The image is downloaded (which can take a while, depending on your network) and installed.

  15. Verify that everything is installed, ready, and running with the show role command. When the system reports resource, the installation of the DL-worker VM is complete. Next, we need to convert it from its current resource role to a DL-Worker from within the Stellar Cyber user interface. Refer to Adding Worker Nodes in the Stellar Cyber User Interface.

Configure the DA-Worker Node in the CLI

Use the following procedure to configure the DA-Worker node in the CLI:

  1. Access the console of the DA-Worker VM using the private IP address you copied in Get IP Addresses for VMs.
  2. Log in. The default user/password is aella/changeme. You are immediately prompted to change the password.
  3. Change the password.
  4. Reconnect to the DA-Worker VM using the new password you just set.
  5. The prompt changes to DataProcessor>.

  6. Enter the following command:

    show hostname

  7. The default hostname in public cloud environments typically includes the private IP address of the host and may not be immediately meaningful when you see it later on in the Stellar Cyber user interface. You can change it to something meaningful using the set hostname <hostname> command. For example:

    DataProcessor> set hostname DA-worker

    If you do change the hostname, you must reboot the virtual machine to apply the change.

  8. Set the role of the VM to resource as follows:

    DataProcessor> set role resource

    Make sure you set the role to resource! You'll change the role for this resource in the Stellar Cyber user interface in Adding Worker Nodes in the Stellar Cyber User Interface

  9. AWS automatically configures DNS and NTP settings for the VM. You can verify the settings with the show dns and show ntp commands, respectively.

  10. Use the set cm <ip_address> command to set the IP address of the Data Lake master's management interface as follows:

    1. Retrieve the private IP address of the DL-Master using the Instances list in the AWS Console.

    2. Enter the following command using the IP address you just retrieved:

      DataProcessor> set cm <private_ip_address of DL-m>

  11. Use the reset command to apply your changes. This command starts all Stellar Cyber microservices using your new settings.

  12. Confirm the reset. The image is downloaded (which can take a while, depending on your network) and installed.

  13. Verify that everything is installed, ready, and running with the show role command. When the system reports resource, the installation of the DA-worker VM is complete. Next, we need to convert it from its current resource role to a DA-worker from within the Stellar Cyber user interface.

Refer to Configuring the DL-m and DA-m in Stellar Cyber.