Upgrading Greenplum Command Center

This section provides steps for upgrading Pivotal Greenplum Command Center to a new version.

Upgrading Greenplum Command Center requires installing the new distribution, and then migrating Command Center instances from a previous installation.

A new Greenplum Command Center software release may be installed in the same parent directory as the current release, by default /usr/local. The installer updates the symbolic link greenplum-cc-web to point to the new release directory and leaves the old release directory in place. After the software is installed, run the gpcmdr --migrate command to recreate your Command Center instances.

Install the New Software Release

  1. Log in as the gpadmin user.
  2. Source the greenplum_path.sh and gpcc_path.sh files from the current release:

    $ source /usr/local/greenplum-db/greenplum_path.sh
    $ source /usr/local/greenplum-cc-web/gpcc_path.sh
    
  3. Download the latest Command Center release from Pivotal Network. Installer files are available for Linux 64-bit platforms, and have names in the format:

    greenplum-cc-web-X.X.X-PLATFORM.zip
    
  4. Unzip the installer file. For example:

    # unzip greenplum-cc-web-X.X.X-PLATFORM.zip
    
  5. Launch the installer for the new release with the bash shell:

    $ /bin/bash greenplum-cc-web-X.X.X-PLATFORM.bin
    

    Note: The installer requires write permission in the installation directory (/usr/local, by default). If the gpadmin user does not have write permission in the installation directory, run the installation as root. You will need to change file ownership and permissions after the software is installed.

  6. Read through the license agreement. When you reach the bottom, type yes to accept the license agreement.

  7. The installer prompts you to provide an installation path. Enter a full path or press ENTER to accept the default, /usr/local. You must have write permission in the directory you specify.

  8. If you ran the installation as root or any user other than gpadmin, change the ownership and permissions of the installation directory:

    # chown -R gpadmin:gpadmin /usr/local/greenplum-cc-web-versionx.x
    # chmod -R 755 /usr/local/greenplum-cc-web-versionx.x
    

    Change to the gpadmin user before you continue to the next step:

    # su - gpadmin
    
  9. Ensure that you have a current host file listing the names of all of the other hosts participating in the Greenplum Database cluster, including the standby master host. The host names must be resolvable in DNS.

  10. As gpadmin, run the gpccinstall utility to install the new Command Center files on all hosts listed in the host file:

    $ gpccinstall -f hostfilename
    

    where hostfilename is the name of the host file you created.

Migrate Command Center Instances

After the new Command Center software is installed, migrate your instances by running the gpcmdr --migrate command.

To migrate all instances from a previous installation, run gpcmdr --migrate with no arguments. For example:

$ gpcmdr --migrate 

To migrate a single instance, run gpcmdr --migrate <instance_name> and, when prompted, provide its full installation path. For example:

$ gpcmdr --migrate myinstance

Custom changes to the ssh-wrapper file are not handled by instance migration. See Configuration File Reference for information about the ssh-wrapper file. If you have set a custom ssh path in this file, you must copy it to the current installation.

For example:

cp /usr/local/greenplum-cc-web-3.0.0/bin/ssh-wrapper /usr/local/greenplum-cc-web/bin

See Creating Greenplum Command Center Console Instances for instructions to create new instances with gpcmdr --setup.