Upgrading Cloudera Director

This section contains notes and procedures for upgrading Cloudera Director.

Before Upgrading Cloudera Director from 1.1.x to 1.5.x

Follow these steps before upgrading to Cloudera Director 1.5.x.

  1. Let running operations finish.

    For example, if Cloudera Director is setting up a Cloudera Manager or CDH cluster (indicated by a progress bar in the UI), an upgrade will not complete successfully. An error in the log file instructs to use the old version of Cloudera Director until all running operations are completed, and then perform the upgrade.

  2. Back up the Cloudera Director database that stores state information. By default, this is the embedded H2 database found at /var/lib/cloudera-director-server/state.h2.db.
    If you are using a MySQL database to store Cloudera Director state, use MySQL backup procedures to back up the Cloudera Director database. The following example shows how to do this using the mysqldump utility: 
    mysqldump --all-databases --single-transaction --user=root --password > backup.sql
    For more information on using mysqldump, see the MySQL documentation.
  3. Change your default encryption key.

    After an upgrade to Cloudera Director 1.5.0 and higher, any new data that Cloudera Director persists in its database is encrypted with a default encryption key. For increased security, Cloudera recommends that you change your encryption key in the application.properties file before performing the upgrade. The file is located at /etc/cloudera-director-server/application.properties.

    For more information about encryption and Cloudera Director data, see Cloudera Director Database Encryption.

Changes to the application.properties File in Cloudera Director 1.5.x

If you modified the application.properties file in Cloudera Director 1.1.x, the result of upgrading to Cloudera Director 1.5.x depends on which version of Linux you are using:
  • RHEL and CentOS - New properties introduced in Cloudera Director 1.5 are added to application.properties.rpmnew. The original application.properties file functions as before and is not overwritten with the new Cloudera Director 1.5.x version properties. You do not need to copy the new properties from application.properties.rpmnew to the old application.properties file.
  • Debian and Ubuntu - The modified Cloudera Director 1.1.x application.properties file is backed up to a file named application.properties.dpkg-old. The original application.properties file is then overwritten by the new application.properties file containing new Cloudera Director 1.5.x properties. After upgrading, copy your changes from application.properties.dpkg-old to the new application.properties file.

Upgrading Cloudera Director 1.1.x to Cloudera Director 1.5.x

The following sections describe steps for upgrading Cloudera Director 1.1.x to Cloudera Director 1.5.x on supported Linux operating systems.

RHEL and CentOS

  1. Stop the Cloudera Director server service by issuing the following command: 
    sudo service cloudera-director-server stop
  2. Open /etc/yum.repos.d/cloudera-director.repo. If the baseurl value in this file points to a specific minor or maintenance release version, like /1.1/ or /1.1.3/, update the URL to point to the new 1.5.x version, such as 1.5.1. If the URL points to /1/, you do not need to update this file.
  3. Issue the following commands: 
                  sudo yum clean all
              sudo yum update cloudera-director-server cloudera-director-client
              sudo service cloudera-director-server start

SLES

  1. Stop the Cloudera Director server service by issuing the following command: 
    sudo service cloudera-director-server stop
  2. Open /etc/zypp/repos.d/cloudera-director.repo. If the baseurl value in this file points to a specific minor or maintenance release version, like /1.1/ or /1.1.3/, update the URL to point to the new 1.5.x version, such as 1.5.1. If the URL points to /1/, you do not need to update this file.
  3. Issue the following commands: 
                  sudo zypper clean --all
              sudo zypper update cloudera-director-server cloudera-director-client
              sudo service cloudera-director-server start

Ubuntu

  1. Stop the Cloudera Director server service by issuing the following command: 
    sudo service cloudera-director-server stop
  2. Open /etc/apt/sources.list.d/cloudera-director.list. If the baseurl value in this file points to a specific minor or maintenance release version, like /wheezy-director1.1/ or /trusty-director1.1.3/, update the URL to point to the new version, 1.5.x. If the URL points to /1/, you do not need to update this file.
  3. Issue the following commands: 
    sudo apt-get clean
              sudo apt-get update 
              sudo apt-get dist-upgrade 
              sudo apt-get install cloudera-director-server cloudera-director-client
  4. If your original Cloudera Director 1.1.x application.properties file has not been modified, proceed to the next step. If your application.properties file was modified in Cloudera Director 1.1.x, the original properties file will be overwritten by the new properties file containing new Cloudera Director 1.5.x properties, as described in Upgrading Cloudera Director 1.1.x to Cloudera Director 1.5.x. After completing steps 1–3, copy your changes from application.properties.dpkg-old to the new application.properties file before restarting the server.
  5. Restart the Cloudera Director server: 
    sudo service cloudera-director-server start

Using IAM Policies with Cloudera Director 1.5 and Higher

In AWS, if you are using an IAM policy to control access to resources in the VPC, Cloudera Director 1.5 and higher requires permission for the method DescribeDBSecurityGroups. To give Cloudera Director permission for this method, add these values to your policy: 
{
            "Action": [ "rds:DescribeDBSecurityGroups" ],
            "Effect": "Allow",
            "Resource": ["*"]
            }

This permission is required because Cloudera Director 1.5 and higher includes early validation of RDS credentials when creating or updating an environment, whether or not RDS database servers are used.

For a sample IAM policy that includes this permission, see Example IAM Policy. For more information on AWS IAM, see the IAM User Guide in the AWS documentation.