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 Instances

  2. Configure the DL-worker Node in the CLI

  3. Configure the DA-Worker Node in the CLI

Get IP Addresses for Instances

When the instances for your deployment are up and running, you are ready to log in to their consoles and assign roles.

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

  1. Log in to your OCI Console.

  2. Navigate to Compute | Instances. The active instances appear.

  3. Copy the Public IP and Private IP for the DL-master, DL-worker, and DA-worker instances.

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 instance using an SSH connection to the public IP address you copied in the previous procedure. For example, from Windows PowerShell:

    PS > ssh -i <ssh-key> aella@<public ip address>

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

  1. Access the console of the DL-worker instance 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.

    The system closes your connection automatically.

  4. Reconnect to the DL-m instance using the new password you just set.
  5. The prompt changes to DataProcessor>.

  6. Enter the following command:

    show hostname

  7. The hostname is set to the name you configured for the instance. You can change it using the set hostname <hostname> command, if you want. 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 instance to resource as follows:

    DataProcessor> set role resource

    The prompt changes to DataProcessor(resource)> to indicate the role change.

    Make sure you set the role to resource! You'll change the role for this resource in the Stellar Cyber user interface in Configure the DL-worker Node in the CLI

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

  10. Configure the DL-worker instance to use the block volume you attached in OCI 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 OCI Console.

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

      DataProcessor> set cm <private_ip_address of DL-m>

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

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

  14. Verify that everything is installed, ready, and running with the show role command. When the system reports resource, the installation of the DL-worker instance 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 DL-m instance using an SSH connection to the public IP address you copied in Get IP Addresses for Instances.. For example, from Windows PowerShell:

    PS > ssh -i <ssh-key> aella@<public ip address>

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

  3. Change the password.

    The system closes your connection automatically.

  4. Reconnect to the DL-m instance using the new password you just set.
  5. The prompt changes to DataProcessor>.

  6. Enter the following command:

    show hostname

  7. The hostname is set to the name you configured for the instance. You can change it using the set hostname <hostname> command, if you want. 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 instance to resource as follows:

    DataProcessor> set role resource

    The prompt changes to DataProcessor(resource)> to indicate the role change.

    Make sure you set the role to resource! You'll change the role for this resource in the Stellar Cyber user interface in Configure the DL-worker Node in the CLI

  9. OCI automatically configures DNS and NTP settings for the instance. 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. Refer to the private IP address of the DL-m you copied in Get IP Addresses for Instances.

    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 with an uppercase YES. 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 instance 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 Adding Worker Nodes in the Stellar Cyber User Interface