Setting up Aspera Cluster Manager

For overview information about Aspera Cluster Manager (ACM), see Aspera Cluster Manager for Orchestrator (Overview).

Configuring ACM

Execute the following commands on both Orchestrator servers:

# cd /opt/aspera
# ln –s /acm_files/acm ./acm

Running an ACM Sanity Check

The acmctl command has an option to check that the necessary configurations have been made that allow the acm4orchestrator script to run appropriately. You should make sure that each server passes the sanity test.

Run the acmctl command with the -s option on both nodes to verify the basic ACM prerequisites:

# /opt/aspera/acm/bin/acmctl –s

ACM sanity check
----------------
Checking if the database.yml symbolic link exists   OK Checking if the database.yml symbolic link points to the right location    OK Checking if an entry for ACM seems to exist in the crontab                 KO Checking that the orchestrator master service is disabled in chkconfig           OK Checking that SE Linux mode is not set to enforcing                        OK

Note:

The status of the Checking if an entry for ACM seems to exist in crontab displays as KO, not OK, in the example above because the user has not yet created the crontab entry that will run the ACM software on each server.

Correct any task that does not pass the sanity check (except for tasks with crontab status; those tasks are addressed in the next section).

Configuring the crontab Entry to Run ACM

Configure ACM services in crontab on both nodes so that the acm4orchestrator script is launched every minute.

Use the crontab –e command to configure your entry as follows.

# crontab –e
* * * * * /opt/aspera/acm/bin/acm4orchestrator ip_address  device_number > /dev/null 2>&1

Two parameters must be entered in crontab: the IP address of the host where the script is running and the device number of the partition where the ACM files are located. These parameters are passed to the acm4orchestrator script.

In the example below, the IP address is 10.0.71.21 and the device number is 20.

# crontab –e
* * * * * /opt/aspera/acm/bin/acm4orchestrator 10.0.71.21  20 > /dev/null 2>&1

Once configured in crontab, the acm4orchestrator script runs regularly to determine the active node and start the required Orchestrator services on both the active and passive nodes, depending on their current status (active or passive).

Obtaining the crontab Parameter Values

To list the IP addresses available on a system, run the following command:

# ip addr | grep "inet"
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
inet 10.0.75.21/16 brd 10.255.255 scope global eth0

To determine the correct value to use for the device number, run the following command:

# stat -c "%d" /acm_files
20

/acm_files is a placeholder for your shared storage mount point that contains ACM files.

Identifying the Status of ACM on Each Orchestrator Server

The /opt/aspera/acm/bin/acmctl -i command (addressed on the next page) can be used to identify which Orchestrator server is active and which is passive.

Connecting to Orchestrator with the VIP

If the services are running properly, you can now connect to the Orchestrator application using the virtual IP address (VIP) assigned to the ACM cluster.

If the load balancer is correctly configured, you should now be able to connect to the Orchestrator web application using the URL pointing to the VIP

Parent topic: High Availability Installation