Adding a worker

Arcfra Migration Tool does not support adding or deleting worker nodes via the web console. To manage workers, modify the configuration file on the controller machine and restart the service.

Workers are classified into the following two types:

• Local worker: Deployed on the same machine as the controller and automatically configured during system initialization, with one per environment.
• Remote worker: Deployed on another machine as an independent Arcfra Migration Tool service node and registered with the controller through the configuration file. Each environment can add a maximum of 19 remote workers, that is, the system allows up to 20 workers with the local worker included. Note that the added remote workers cannot be used as a controller.

Local worker

The credentials of the local worker are automatically written to the configuration file during system initialization. You do not need to add them manually.

To view or modify the connection credentials of the local worker, edit the following configuration file:

/etc/v2v-controller/backend/controller.env

The configuration items related to the local worker are as follows:

Information:

If the preceding credentials in the configuration file are displayed as __PENDING_INIT__, it indicates that the system has not completed initialization. The local worker will take effect automatically after initialization is complete. Refer to Logging in to the migration tool to complete initialization.

After modifying the configuration, run the following command to restart the controller service for the change to take effect:

systemctl restart v2v-controller.service

Remote worker

Prerequisite

• Arcfra Migration Tool is successfully deployed on the remote machine. For details, refer to the Deploying Arcfra Migration Tool section.
• You have accessed the web console of the remote machine in a browser, completed system initialization, and recorded the following information:
  • IP address of the remote worker
  • Username and password configured during initialization

Note

To avoid affecting migration efficiency, plan the number of remote workers to add based on the migration network bandwidth. For details, refer to Limitations for migrating virtual machines.

Procedure

1. Log in to the machine hosting the controller as a user with sudo privileges.

2. Edit the remote worker configuration file:

   /etc/v2v-controller/backend/servers.yaml

3. Delete [] from the configuration file, and then add worker entries to the file. Each remote worker corresponds to one group of configurations:

   - name: worker-remote-a
     host: 10.0.0.10
     username: admin
     password: YourPassword
   

   The configuration parameters are described as follows:

   Parameter	Required	Description
   name	No	Custom name of the worker, used to identify the node in the console
   host	Yes	IP address of the remote worker, which cannot overlap with that of any other worker.
   username	Yes	Username configured during initialization of the remote worker
   password	Yes	Password configured during initialization of the remote worker

   To add multiple remote workers simultaneously, add list items in sequence:

   - name: worker-remote-a
     host: 10.0.0.10
     username: admin
     password: YourPassword1
   
   - name: worker-remote-b
     host: 10.0.0.11
     username: admin
     password: YourPassword2
   

   Note:

   • The host of each remote worker cannot be duplicated and cannot conflict with the address of the local worker.
   • The username and password must be the actual account and password that can be used to log in after finishing initialization in the remote worker.
   • You can add a maximum of 19 remote workers, that is, the system allows up to 20 workers with the local worker included.

4. Save the file. Run the following command to restart the controller service for the configuration to take effect:

   systemctl restart v2v-controller.service

After the restart is complete, navigate to the WORKERS page and confirm whether the newly added worker is online and running properly.

Troubleshooting

If the worker does not appear after the restart, or if its connection status is displayed as Unreachable, check the following items in order: