Manually deploying agents - Installer-No Services or tarball installations

Install agents on nodes running Cassandra or DataStax Enterprise clusters.

address.yaml 

The location of the address.yaml file depends on the type of installation:

  • Installer-Services or package installations: /var/lib/datastax-agent/conf/address.yaml
  • Installer-No Services or tarball installations: install_location/conf/address.yaml

opscenterd.conf 

The location of the opscenterd.conf file depends on the type of installation:

  • Installer-Services or package installations: /etc/opscenter/opscenterd.conf
  • Installer-No Services or tarball installations: install_location/conf/opscenterd.conf
  • Windows installations: Program Files (x86)\DataStax Community\opscenter\conf\opscenterd.conf

Prerequisites

  • The Cassandra or DataStax Enterprise cluster is up and running.
  • OpsCenter is installed and configured.
  • JMX connectivity is enabled on each node in the cluster.
  • The OpsCenter diagnostic tarball feature requires a GNU tar version 1.16 or above. CentOS/RHEL version 5.x does not include the required tar version. For those running on CentOS or RHEL version 5, either upgrade OpsCenter to CentOS or RHEL version 6 or above, or download and compile an acceptable version of tar.
  • SYSSTAT Utilities (needed for the collection of I/O metrics).

Procedure

  1. Download the DataStax agent tarball, expand and unarchive it. 
    $ curl -L http://downloads.datastax.com/community/datastax-agent-version_number.tar.gz | tar xz
  2. Change into the agent directory. 
    $ cd datastax-agent-version_number
  3. In address.yaml set stomp_interface to the IP address that OpsCenter is using. (You may have to create the file.) 
    $ echo "stomp_interface: reachable_opscenterd_ip" >> ./conf/address.yaml
  4. If SSL communication is enabled in opscenterd.conf, use SSL in address.yaml. 
    $ echo "use_ssl: 1" >> ./conf/address.yaml
  5. Start the agent. 
    $ bin/datastax-agent
    Use the -f flag to run in the foreground.