Top.Mail.Ru
Installing The Automation Module
CTRL+K

Installing the Automation Module

In this article
  • Installing the Automation Module
  • Running the Container (HTTP)
  • Running the Container in Docker Swarm (HTTP)
  • Running the Container in Docker Swarm (HTTPS)

The automation agent is included by default in the base Operavix image and is deployed automatically during installation. However, in some cases, you may need to deploy the agent on a separate server. Below are instructions for manually deploying the automation agent and configuring its connection.

Depending on the connection type, choose the appropriate container launch method.

Running the Container (HTTP)

If you are running the automation agent outside a clustered environment and do not intend to use a secure connection (HTTPS), run it as a Docker container.

# docker run --name=operavix-automation-agent \
 -e CL_NAME='2' -e CL_PORT='7000' \
 -e CL_REMOTE_NODES='192.168.1.1:7000' \
 --mount type=volume,src=operavix-automation-agent-log,target=/var/log/operavix/ \
 -p 0.0.0.0:7000:7000 -d --restart=always \
 dockerhub.office.operavix.com/operavix/operavix_automation-agent:da220803
Note

The image name and version shown are for example purposes only. Replace the version with the one you are installing.

Running the Container in Docker Swarm (HTTP)

If you are already using Docker Swarm or plan to scale the system, the automation agent can be deployed as a standalone service within the cluster.

  1. Initialize Docker Swarm:
    # docker swarm init --advertise-addr 127.0.0.1:2377 --listen-addr 127.0.0.1:2377
    
  2. Create a service:
    # docker service create --name operavix-automation-agent \
     -e CL_NAME='2' -e CL_PORT='7000' \
     -e CL_REMOTE_NODES='192.168.1.1:7000' \
     --publish published=7000,target=7000,mode=host \
     --mount type=volume,src=operavix-automation-agent-log,target=/var/log/operavix/ \
     --limit-memory 30G \
     --limit-cpu 2 \
     --restart-max-attempts 5 \
     --restart-condition "on-failure" \
     dockerhub.office.operavix.com/operavix/operavix_automation-agent:da220803
    
    Note: The image name with version is for example only. Replace it with the version you are currently installing.

Running the Container in Docker Swarm (HTTPS)

To run the container using Docker Swarm (HTTPS):

  1. Initialize Docker Swarm:
    # docker swarm init --advertise-addr 127.0.0.1:2377 --listen-addr 127.0.0.1:2377
    
  2. Create secrets:
    • configure the SSL node:
    # docker secret create operavix_app_automation_agent.crt ${PATH_FILE}
    
    # docker secret create operavix_app_automation_agent.key ${PATH_FILE}
    
    • configure the SSL connection to the main node:
    # docker secret create operavix_app_remote_main.crt ${PATH_FILE}
    
    • Note that when using secrets in cluster mode, you must use the method specifying source and destination with strict destination naming: cluster_current.crt — the node's primary certificate, cluster_current.key — the node's primary key, cluster_remote_node_*.crt — certificates of remote nodes, where * is replaced with the name of the remote node.
  3. Create a service:
    # docker service create --name operavix-automation-agent \
     -e CL_NAME='2' -e CL_PORT='7000' \
     -e CL_REMOTE_NODES='192.168.1.1:7000' \
     --secret source=operavix_app_automation_agent.crt,target=cluster_current.crt \
     --secret source=operavix_app_automation_agent.key,target=cluster_current.key \
     --secret source=operavix_app_remote_main.crt,target=cluster_remote_node_main.crt \
     --publish published=7000,target=7000,mode=host \
     --limit-memory 30G \
     --limit-cpu 2 \
     --restart-max-attempts 5 \
     --restart-condition "on-failure" \
     dockerhub.office.operavix.com/operavix/operavix_automation-agent:da220803
    
    Note: The image name with version is provided as an example. Replace it with the version you are installing.

If the certificates are issued for DNS names, replace:

-e CL_REMOTE_NODES='192.168.1.1:7000'

With this:

-e CL_REMOTE_NODES='n1.local:7000'

If necessary, also add the parameter:

--host n1.local:192.168.1.1

On the Cluster Mode Setup page, there is an example of generating self-signed certificates. If we assume:

  • n1.local — main server
  • n2.local — external agent

The correlation will be as follows:

  • n2.crtoperavix_app_automation_agent.crt
  • n2.keyoperavix_app_automation_agent.key
  • n1.crtoperavix_app_remote_main.crt

Was the article helpful?

Yes
No
Previous
Migrating the Operavix Server from Windows to Linux
We use cookies to improve our website for you.