Upgrading DSE OpsCenter tarball installations

Steps for upgrading OpsCenter using the 6.7 tarball.

These steps provide information on upgrading to OpsCenter 6.7.1 using the OpsCenter tarball and restarting the opscenterd daemon.

Important: Upgrading from OpsCenter 6.1 to 6.7.1 requires an interim upgrade to OpsCenter 6.5. Upgrade from OpsCenter 6.1 to the most current release of OpsCenter 6.5 before upgrading to OpsCenter 6.7.1.
OpsCenter version DSE version
6.7 6.7, 6.0, 5.1
6.5 6.0, 5.1, 5.0 (EOL)
6.1 5.1, 5.0 (EOL), 4.8 (EOSL)
6.0 5.0 (EOL), 4.8 (EOSL), 4.7 (EOSL)

cluster_name.conf

The location of the cluster_name.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf

Prerequisites

Review Upgrade considerations for changes in configuration files, metrics, and APIs that affect upgrades to OpsCenter 6.7.1.
Important: Before upgrading, back up your OpsCenter keyspace if you anticipate, plan, or need to downgrade to an earlier version of OpsCenter. Downgrading OpsCenter is a very manual and case-specific process. If you require a downgrade, contact DataStax Support for assistance before proceeding.

Additionally, view the compatibility table to ensure that OpsCenter is compatible with your version of DataStax Enterprise.

Procedure

  1. If you previously configured the api_port under the [cassandra] or [cassandra_storage] headers in cluster_name.conf, delete the entries and insert them under the [agents] header.

    If this entry still exists under the [cassandra] or [cassandra_storage] headers, OpsCenter will not start.

  2. Download and extract the new tarball.
  3. Copy the following files and directories from the old tarball installation directory to the new one:
    conf/clusters/*
    conf/event-plugins/*
    conf/install_id
    conf/logback.xml
    conf/opscenterd.conf
    ./passwd.db
    ./lcm.db
    ./keys/lcm.key

    For example, the following command copies the files in the /conf/clusters/* directory from the old tarball location to the new one:

    scp -r old_tarball_directory/conf/clusters/* new_tarball_directory/conf/clusters/*
  4. If SSL is enabled, copy the contents of the SSL configuration directory: install_location/ssl/*.
  5. If opscenterd is running, stop the instance and start it from the new tarball installation directory.

What's next

Upgrade DataStax Agents manually from tarballs.