Install Reorc agent
Data Plane of Reorc consists of multiple worker hosts to run the data jobs orchestrated from the Control Plane.
Each worker contains a service called Reorc Agent that communicates with Control Plane and manages execution environments on the host. Some rules for setting workers are as follows:
Multiple workers can be set up for horizontal scalability.
Workers can be installed in different places across the Internet.
Workers that are meant for a single environment must be able to communicate with each other. Therefore, it is recommended that workers for the same environment be located in the same local network, for maximum connection stability and minimum latency.
This guide shows you how to set up Reorc agent.
Requirements
Your worker hosts should meet these requirements.
Hardware:
Depending on the usage, your setup can follow these configuration ranges to optimize the performance with Reorc.
Minimum
1
2
4
20
Recommended
2+
4
16
100
Software:
Operating System: Linux (RHEL and Ubuntu are tested).
Python: 3.9+, we recommend using a newer version and virtual environment if feasible.
Docker: 20.10.0+, with Docker Compose installed.
Make sure the user runs the Reorc agent has access to docker cli. This command might be helpful. You may need to logout and re-login to the terminal session after modifying the user's group.
Set up Reorc Agent
Follow these steps:
On the left sidebar of Reorc, click on the Organization icon and select Environment & Workers.
Click Deploy Agent and follow the on-screen instructions to deploy the agent.
Alternatively, follow the steps below.
Refresh the page to see the newly deployed host. The status should be Online.
Allocate the agent to an environment.
Once the agent is running with the Online status, click action > Join Environment and select the environment to allocate. When the agent successfully joins the environment, you should see the Active status.
Note:
The
recurve agent startcommand starts the agent in the foreground, and will terminate after the terminal session closed. For production deployment, you should let the agent run in the background. For more details, refer to Run Agent in Background.Both
devandprodmust have at least one agent running.
Actions on an agent
Once the agent is up and running, there are some key actions that you can perform with the service. Click on the action button of an agent:
Here you can:
Upgrade Service: Upgrade the worker service to the latest version.
Restart Service: restart the agent service; the agent will still join the environment after restarting.
Stop Service: stop the agent service; the agent will become inactive.
Leave Environment: remove the agent service from the current environment.
Run the agent in the background
There are multiple ways to run an agent in the background with systemd.
Upgrade the agent
Keeping the Recurve agent updated is always recommended.
To upgrade the agent , follow these steps:
Stop the agent service.
Depending on the way you manage the service, you may need to run one of these commands to stop the process:
Upgrade and re-login.
Start the agent.
Last updated
