Altus Director Upgrade

By default, Altus Director 6.0 creates clusters with Cloudera Manager 6.0 and CDH 6.0. When you upgrade to Director 6.0, you can continue to manage existing clusters with Cloudera Manager and CDH parcels 5.7 and higher.

Altus Director 6.0 has a number of changes that are not compatible with Altus Director 2.8. Before you start the upgrade process, review the list of changes in the release notes to understand the effects of upgrading to Altus Director 6.0. See Changes in Altus Director 6.0.

To upgrade to Altus Director 6.0, complete the following steps:
  1. Review the upgrade requirements.

    Altus Director 6.0 has different requirements than the previous version. Make sure that you understand the requirements before you start the upgrade process.

  2. Perform the tasks required for the upgrade.

    If your current Altus Director does not meet the Altus Director 6.0 requirements, the upgrade process will fail. For example, you cannot upgrade from an Altus Director version that is earlier than version 2.8. You must upgrade to Altus Director 2.8 before you start the upgrade to Altus Director 6.0.

  3. Upgrade to Altus Director 6.0.

    Follow the instructions for upgrading the Altus Director server and client on your operating system.

  4. Restore the settings to match the configuration of the previous version.

    If you customized the configuration of the Altus Director 2.8 instance, you can restore the configuration from your backup files and use the same configuration in Altus Director 6.0. Note that the names of some configuration properties have changed in Altus Director 6.0. Review the changes to verify that you are using the correct property names in Altus Director 6.0.

    Complete this step before you start the Altus Director 6.0 server.

  5. Restart the Altus Director 6.0 server.

Step 1: Review the Upgrade Requirements

Altus Director 6.0 has the following requirements:

Only Altus Director 2.8 can be upgraded to Altus Director 6.0.
You cannot upgrade to Altus Director 6.0 from any other Director version.
Altus Director 6.0 requires Oracle JDK version 8.
Altus Director 6.0 supports only Java 8. Altus Director 6.0 does not support earlier or later versions of Java.
Altus Director 6.0 requires Cloudera Manager version 5.7 or higher.
Altus Director 6.0 does not work with Cloudera Manager instances earlier than version 5.7.
Altus Director 6.0 supports RHEL and CentOS versions 6.7, 6.8, 7.2, 7.4, and 7.5 for Cloudera Manager and clusters.
Altus Director 6.0 supports installation of Cloudera Manager and clusters on the following OS versions:
  • For AWS and Google Cloud Platform only, Altus Director 6.0 now supports RHEL and CentOS version 7.5
  • For all cloud service providers, Altus Director 6.0 continues to support RHEL and CentOS versions 6.7, 6.8, 7.2, and 7.4

Altus Director 6.0 cannot create clusters on other versions of the operating systems. Likewise, Altus Director 6.0 does not work with existing Cloudera Manager and clusters that are running on other versions of the operating systems.

For the complete list of requirements for Altus Director, see Requirements and Supported Versions.

Step 2. Perform Tasks Required for the Upgrade

Complete all the necessary tasks to meet the upgrade requirements to ensure that you can successfully upgrade to Altus Director 6.0.

Before you upgrade to Altus Director 6.0, complete the following tasks:

Verify that you are upgrading from Director 2.8 to Altus Director 6.0.
Required.
You can upgrade to Altus Director 6.0 only from Altus Director 2.8. If you are upgrading from an Altus Director version that is earlier than version 2.8, you must upgrade to version 2.8 before you can upgrade to Altus Director 6.0.

The Altus Director 6.0 upgrade will not start if it detects that the Altus Director instance your are upgrading is not version 2.8.

For more information about upgrading to Altus Director 2.8, see the Altus Director 2.8 upgrade documentation.

Verify that your Java version is Oracle Java 8.
Required.
Altus Director 6.0 requires Oracle JDK version 8. It does not support other versions of the Oracle JDK. You must upgrade to Java 8 before you can upgrade to Altus Director 6.0.

For more information about Java installations, see the Oracle Java page.

Upgrade all Cloudera Manager instances that are older than version 5.7
Required.
Altus Director 6.0 supports Cloudera Manager version 5.7 or higher. Verify that all Director deployments are running Cloudera Manager version 5.7 or higher and upgrade any Cloudera Manager version 5.6 or earlier.

Altus Director 6.0 will not start if it detects a deployment running Cloudera Manager 5.6 or earlier.

Back up the Altus Director 2.8 properties file.
Recommended.
If you have modified the Director 2.8 application.properties file, back up the file before you start the upgrade.

The application.properties is located in the following directory: /etc/cloudera-director-server/

After the upgrade, you can use the settings in the backup file to set the same configuration in Altus Director 6.0.

Back up the configuration files for the Altus Director 2.8 plug-ins.
Recommended.
Altus Director includes configuration files that enable you to configure how the Altus Director plug-ins work. If you have modified the Altus Director 2.8 plug-in configuration files, back up the configuration files before you start the upgrade. After the upgrade, you can copy the plug-in configuration files from your backup and use the same configuration files for the Altus Director 6.0 plug-ins.

The Altus Director plug-in files are in the following directory: /var/lib/cloudera-director-plugins/

The directory contains a separate versioned subdirectory for each plug-in. Back up the directory for the plug-in where you modified the configuration file. Or, if you modified the configuration files for multiple plug-ins, back up the main /cloudera-director-plugins directory.

Back up the Altus Director 2.8 database that stores state information.
Recommended.
The Altus Director 6.0 upgrade overwrites the state information in the Altus Director database. Back up the database before you start the upgrade process. If the upgrade fails and you decide to revert back to the previous version, you can restore the data.
By default, Altus Director stores state information in the embedded H2 database named state.h2.db in the following directory: /var/lib/cloudera-director-server/. If you are using the default database, back up the state.h2.db file.
If you are using a MySQL database to store the Altus Director state, use MySQL backup procedures to back up the Altus Director database. The following example shows how to back up a MySQL database using the mysqldump utility: 
mysqldump --all-databases --single-transaction --user=root --password > backup.sql
For more information on using mysqldump, see the MySQL documentation.

Step 3. Upgrade to Altus Director 6.0

The upgrade procedure differs based on the operating system where the current Altus Director is installed.

RHEL and CentOS

  1. Stop the Altus Director server service by running the following command: 
    sudo service cloudera-director-server stop

    Before you proceed, verify that the Altus Director instance that you are upgrading meets all upgrade requirements. See Step 1: Review the Upgrade Requirements.

  2. Download the Altus Director cloudera-director.repo file for Altus Director 6.0.

    The cloudera-director.repo file is the YUM repository configuration file for Altus Director. The base URL in the latest cloudera-director.repo file points to the Altus Director 6.0 repository.

    Run the following commands to download the latest Altus Director cloudera-director.repo file :

    RHEL and CentOS 7.x: 
    cd /etc/yum.repos.d/
sudo wget "https://username:password@archive.cloudera.com/p/director6/6.0.0/redhat7/cloudera-director.repo"
    RHEL and CentOS 6.x: 
    cd /etc/yum.repos.d/
sudo wget "https://username:password@archive.cloudera.com/p/director6/6.0.0/redhat6/cloudera-director.repo"
  3. Run the following commands to upgrade the Altus Director server and client: 
    sudo yum clean all
sudo yum update cloudera-director-server cloudera-director-client

    The Altus Director upgrade installs all required plug-in packages.

    After the Altus Director server and client upgrade completes, rerun the service manager in the operating system.

  4. Run the following command to re-execute the systemd manager: 
    sudo systemctl daemon-reexec

Ubuntu

  1. Stop the Altus Director server service by running the following command: 
    sudo service cloudera-director-server stop

    Before you proceed, verify that the Altus Director instance that you are upgrading meets all upgrade requirements. See Step 1: Review the Upgrade Requirements.

  2. Download the Altus Director cloudera-director.list file for Altus Director 6.0.

    The cloudera-director.list file is the repository configuration file for Altus Director. The base URL in the latest cloudera-director.list file points to the Altus Director 6.0 repository.

    Run the following commands to download the latest Altus Director cloudera-director.list file :

    Ubuntu 14.04 
    cd /etc/apt/sources.list.d/
sudo curl -L "http://username:password@archive.cloudera.com/p/director6/6.0/ubuntu1404/cloudera-director.list" -O
    Ubuntu 16.04: 
    cd /etc/apt/sources.list.d/
sudo curl -L "http://username:password@archive.cloudera.com/p/director6/6.0/ubuntu1604/cloudera-director.list" -O
  3. Run the following commands to upgrade the Altus Director server and client: 
    sudo apt-get clean
sudo apt-get update 
sudo apt-get dist-upgrade 
sudo apt-get install cloudera-director-server cloudera-director-client

    The Altus Director upgrade installs all required plug-in packages.

Step 4. Restore the Configuration

If you want Altus Director 6.0 to have the same configuration as the previous version, restore the configuration settings from the backup files. Do not restart the Altus Director 6.0 server until you have updated the configuration files.

Complete the following tasks:
Restore the Altus Director configuration.
If you modified the application.properties file in the previous version, you can use the same configuration in Altus Director 6.0. Restore the configuration from the backup file.
In Altus Director 6.0, the names of the following properties in the application.properties have changed:
Old property name New property name
lp.terminate.deployment.clouderaManagerServerStopWaitTimeInMs lp.cleanup.cm.stopWaitTimeInMs
lp.terminate.deployment.timeBetweenConnectionRetriesInMs lp.cleanup.cm.timeBetweenConnectionRetriesInMs

Before you overwrite the application.properties file in Altus Director 6.0, check whether you have modified any of the properties that have new names. Update the application.properties backup file before you copy it to the /etc/cloudera-director-server/ directory in Altus Director 6.0.

Restore the plug-in configuration files.
If you modified the configuration files for any of the Altus Director plug-ins in the previous version, restore the configuration files to the Altus Director 6.0 plug-in directory before you restart the Altus Director 6.0 server.

The Altus Director plug-in files are in the following directory: /var/lib/cloudera-director-plugins/

The directory contains a separate versioned subdirectory for each plug-in. Although the version suffix in the subdirectory names changes for every version, the plug-in directory structure and plug-in configuration file names in Altus Director 6.0 is the same as in previous versions.

You can copy the plug-in configuration files from your backup and overwrite the corresponding configuration files in the Altus Director 6.0 plug-in directory.

Step 5. Restart Director

To start Altus Director 6.0, run the following command: 
sudo service cloudera-director-server start

The command to start Altus Director is the same in RHEL, CentOS, and Ubuntu.