Avid Interplay Central Services 1.8 User guide

Brand: Avid

Model: Interplay Central Services 1.8

Category: Database software

Type: User guide

Avid Interplay

Central Services 1.8 Upgrading

Guide

Document Version: 1.0.0

This document is a guide to upgrading to Interplay Central 1.8 from previous version of

Interplay Central. Depending on which version you are upgrading from, the upgrade process

varies. It also includes instructions on migrating the UMS database from a production

system to a test system.

Note: Interplay Central Services 1.8 supports Interplay Central 1.8, Sphere (latest plug-in for

Media Composer 6.5.x and 7.0.x and corresponding NewsCutter versions), and Interplay MAM

4.3.x.

Important Information

Avid

recommends that you read all the information in this upgrade guide thoroughly

before installing or using the corresponding software release.

Important: Search the Avid Knowledge Base at http://www.avid.com/support

for the most

up-to-date ReadMe, which contains the latest information that might have become

available after the documentation was published. The ICS 1.8.x documentation can be found

here:

http://avid.force.com/pkb/articles/en_US/readme/Avid-Interplay-Central-Services-Version-

1-8-Documentation

Revision History

Date Revised

Version

Changes Made

March 26, 2014 1.0.0 First publication.

Interplay Central Services 1.8 Upgrading Guide

Contents

Important Information ....................................................................................................................... 1

Revision History .................................................................................................................................. 1

Contents ..................................................................................................................................................... 2

Overview .................................................................................................................................................... 4

How Do I Use This Guide? .......................................................................................................................... 4

What Operating System Do I Need? .......................................................................................................... 4

Before You Begin: An Important Note on SSL Certificate Passwords ........................................................ 5

Before You Begin: Removing the ICS 1.6 Player Demonstration Web Page .............................................. 6

Mounting and Unmounting the USB Key ................................................................................................... 6

Backing Up and Restoring System Settings and the ICS Database ............................................................ 8

Upgrading Paths ....................................................................................................................................... 11

Upgrading from 1.2.x or 1.3.x to ICS 1.8 .............................................................................................. 11

Upgrading to ICS 1.8 for Interplay Central ........................................................................................... 11

Upgrading to ICS 1.8 for Interplay Sphere............................................................................................ 12

Upgrading to ICS 1.8 for Interplay MAM .............................................................................................. 12

Upgrading from Interplay Central Services 1.6.x/1.7.x to Interplay Central Services 1.8 ....................... 13

Before You Begin .................................................................................................................................. 13

After You Finish .................................................................................................................................... 13

Upgrading a Single Server System from 1.6.x/1.7.x to 1.8 ................................................................... 14

Upgrading a Cluster System from 1.6.x/1.7.x to 1.8 ............................................................................ 16

Reconfiguring ICS for Interplay MAM or Interplay Sphere .................................................................. 18

Upgrading from Interplay Common Services 1.4.x/1.5.x to Interplay Central Services 1.8 .................... 20

Before You Begin .................................................................................................................................. 20

Upgrading a Single Server System ........................................................................................................ 20

Upgrading a Cluster System ................................................................................................................. 21

Mounting the Cache in a 1.4.x/1.5.x to 1.8 Upgrade ........................................................................... 25

Reconfiguring Gluster in a 1.4.x/1.5.x to 1.8 Upgrade ......................................................................... 26

Backing Up and Restoring SSL Private Keys ............................................................................................. 27

Appendix A: Frequently Asked Questions................................................................................................ 29

Appendix B: Migrating the UMS Database to a Test Node ...................................................................... 30

Migrating the 1.6.x (or later) UMS Database ....................................................................................... 30

Migrating the 1.4.x/1.5.x UMS Database ............................................................................................. 31

Interplay Central Services 1.8 Upgrading Guide

Appendix C: Glossary ............................................................................................................................... 33

Interplay Central ................................................................................................................................... 33

Interplay Sphere ................................................................................................................................... 33

Interplay MAM ..................................................................................................................................... 33

Interplay Central Services (ICS) ............................................................................................................ 33

Interplay Central Playback Service (ICPS) ............................................................................................. 33

ICS System Settings .............................................................................................................................. 34

ICS Platform Settings ............................................................................................................................ 34

ICS Database ......................................................................................................................................... 34

Interplay Central User Management Database.................................................................................... 34

Corosync ............................................................................................................................................... 34

Distributed Replicated Block Device (DRBD) ........................................................................................ 34

Copyright and Disclaimer ......................................................................................................................... 35

Interplay Central Services 1.8 Upgrading Guide

Overview

Upgrading to Interplay Central Services (ICS) 1.8 for Interplay Central, Interplay Sphere, and

Interplay MAM, in some cases involves significant changes to the hardware topology of the

system. In all cases it involves the migration of settings and data along with the software

upgrade. Depending on the upgrade path you are faced with, the migration of settings and

data is manual or automated.

Note: Beginning with version 1.6, the term “Interplay Central Services” replaces “Interplay

Common Services.” In addition, the term “Interplay Central Playback Service” replaces

“Interplay Common Playback Service.”

How Do I Use This Guide?

This guide must be used in conjunction with the ICS 1.8 Installation & Configuration Guide.

In this guide, the different supported upgrade scenarios are described, and the overall

upgrade process is documented. However, for each step in the overall upgrade process, this

document either:

• Includes the step-by-step instructions for the step, or

• Cross-references a section in the ICS 1.8 Installation & Configuration Guide

In the second case, the heading of the relevant section in the ICS 1.8 Installation &

Configuration Guide is provided. Since direct page references are unreliable, you must scan

the table of contents in that guide to find the heading and page.

What Operating System Do I Need?

ICS 1.8 requires RHEL 6.3. The ICS installer requires the RHEL 6.3 ISO to be mounted, so you

must obtain the RHEL 6.3 ISO, even if you are not upgrading the OS.

Interplay Central Services 1.8 Upgrading Guide

Before You Begin: An Important Note on SSL Certificate

Passwords

Interplay Central uses the Secure Sockets Layer (SSL) for its server to browser connections.

Default passwords are used by the system to automatically generate and use self-signed

certificates. Customized certificates can also be used, including those that have been issued

by a Certificate Authority (CA).

When customized or CA-signed certificates are used, the ICS 1.8 Installation and

Configuration Guide explains that the SSL passwords must be written to the user-available

Application Properties file in the following directory:

/opt/avid/etc/avid/avid-interplay-central/config/application.properties

This should not be confused with the system-reserved Application Properties file, in the

following location:

/opt/avid/avid-interplay-central/config/application.properties

Caution: The user-available Application Properties file is backed up and restored by the system-

backup script. The system-reserved Application Properties file is not backed up. If the SSL

passwords are in the wrong file, SSL configuration will be broken by the upgrade.

To avoid mishaps, double-check the contents of the system-reserved Application Properties

file before proceeding with the upgrade.

To double-check the system-reserved Application Properties file:

1. List the contents of the Application Properties file reserved for use by the system:

less /opt/avid/avid-interplay-central/config/application.properties

2. Look for the following two lines (they might not be next to each other):

system.org.ops4j.pax.web.ssl.password=OBF\:1lfc1n7n1l1618qm18qo1kxw1n3v1lc6

system.org.ops4j.pax.web.ssl.keypassword=OBF\:1lfc1n7n1l1618qm18qo1kxw1n3v1l

The obfuscated passwords shown above (in bold) are the default system passwords.

3. If the passwords you see match the above, this is correct, and nothing more needs to be

done.

4. If the passwords you see are different, it indicates the file has been edited. This is incorrect,

and you must copy the two modified lines into the following file (you might need to create

the file):

/opt/avid/etc/avid/avid-interplay-central/config/application.properties

Copying the modified lines to the user-available Application Properties file ensures they are

preserved during the upgrade.

Interplay Central Services 1.8 Upgrading Guide

Before You Begin: Removing the ICS 1.6 Player

Demonstration Web Page

If you are upgrading from ICS 1.6 (or earlier) that made use of the player demonstration web

page (http://<host-domain>/player/index.html), you must perform additional steps prior to

beginning the upgrade. You must remove the earlier player demo package, maxcut-dev.

If you do not remove the package, and an earlier version of the player demo page is present,

the upgrade installation will fail with a “Transaction Check” error message. The error is a

result of the renaming of the player demo web page package, which took place in ICS 1.7.

Note: The player demonstration web page distributed with ICS 1.8 has a name of the following

form: maxcut-devel-<version>-<build>.x86_64.rpm. Note the prefix has changed from “maxcut-

dev” (1.6 and earlier) to “maxcut-devel” (1.7 and later).

To successfully upgrade to ICS 1.8 (from 1.6 or earlier) you must uninstall the obsolete

player demo page first. Clean installs are not affected. Upgrades from ICS 1.7 to ICS 1.8 are

not affected.

To uninstall the previous player demo package:

1. Log in to the master node as root.

2. Verify the maxcut packages installed on the server:

rpm -qa | grep maxcut

The system responds by listing all the packages found containing the string

“maxcut”. If “maxcut-dev” is present, it must be uninstalled.

3. Remove the files relating to the old player demo web page by deleting the

corresponding RPM:

rpm -e maxcut-dev

4. Proceed to upgrade to ICS 1.8 as instructed in the ICS 1.8 Upgrading Guide (this

guide) and the ICS 1.8 Installation and Configuration Guide.

Mounting and Unmounting the USB Key

At various times during the upgrade, you will need to mount the USB key. Refer to the

instructions below when the need arises.

To mount and unmount the USB key:

1. Insert the USB key into the ICS server.

2. Verify the name of the device using the dmesg command:

dmesg

Linux information relating to hardware appears on the screen.

Interplay Central Services 1.8 Upgrading Guide

Information for the USB key will appear near the end of the output, near the list of SCSI

devices. The name of the USB key is found inside square brackets (e.g. sdc). This is the

name you use to mount the key.

3. If needed, create a mount point for the USB key:

mkdir /media/usb

4. Mount the USB key at the mount point you just created:

mount /dev/sdc1 /media/usb

Note the name of the USB key, sdc (in this case), takes a 1 (one) in the mount command.

This simply indicates a partition exists on the USB key. When the USB key was

formatted, the partition was created.

The USB key is now mounted and available for use.

5. Verify the USB key has been mounted:

df -h

Information is displayed about all mounted filesystems and devices, and should include

information about the USB key, similar to the following (other output has been omitted,

for clarity):

Filesystem Size Used Avail Use% Mounted on

/dev/sdc1 7.5G 4.5G 3.0G 61% /media/usb

6. To change to the mount point:

cd media/usb

7. To unmount the USB key when finished, ensure you are not currently on it by changing

directories:

Note: In Linux the cd command without any arguments takes you directly to the user’s home

directory. If you are logged in as root, it takes you to the /root directory. You must be off the

USB key to unmount it.

8. Unmount the USB key:

umount /media/usb

The USB key is now available for use in another server.

If you receive an error message that the USB device is busy, it typically indicates the

Linux ISO on the USB key was automounted. Verify what is mounted using the df -h

command and/or the mount command. Then, dismount the Linux ISO first, followed by

the USB device:

umount /sysinstall

umount /media/usb

Interplay Central Services 1.8 Upgrading Guide

9. Remove the USB key from the server.

Removing the USB key prevents accidental rebooting and re-imaging of the system disk.

Backing Up and Restoring System Settings and the ICS

Database

Before performing an upgrade it is recommended — and sometimes required — that you

back up the ICS server system settings using the system-backup script. Depending on the

upgrade path, you may also be required to restore the backed up system settings after.

The system-backup script provided for this task backs up important files and directories,

including NIC card settings, DNS settings, and so on. In addition, the script calls the avid-db

command, which dumps and backs up the contents of the ICS database. The ICS database

contains ACS (Avid Common Services, “the bus”), UMS (User Management Services) and

ICPS (Interplay Central Playback Services) data. It collects all this information and backs it up

to the USB key itself.

Note: In a cluster, the ICS database is replicated across the master and slave node, but it is

only mounted on the master. Thus, the ICS database is only available for dumping and

backup on the master node.

If you are backing up multiple nodes in a cluster, rename the backup file for each node before

proceeding to the next node. If you do not rename the backup file obtained from the master

node, it will be overwritten by the backup from a non-master node and the contents of the

ICS database will be lost (including user information).

The following table lists the files and directories backed up and restored by the system-

backup script.

Note: RHEL user names and passwords (such as the root user) are not backed up or restored

by the system-backup script. After the upgrade, logging in as “root” requires the default

password. For the default root user password, contact your Avid representative.

Directory/File Description

/etc/sysconfig/*

Network settings

/etc/fstab (restored in /root)

Filesystem settings

/etc/resolv.conf

DNS config file

/etc/ntp.conf

Network Time Protocol config file

/etc/snmp/snmpd.conf

Simple Network Management Protocol

(network monitor)

/usr/maxt/maxedit/etc/*

Maxedit settings (used by ICPS)

/etc/udev/rules.d/70-persistent-net.rules

NIC card settings

/usr/maxt/maxedit/share/MPEGPresets/MPEG2TS.

Defines encoding for iOS playback

Interplay Central Services 1.8 Upgrading Guide

Directory/File Description

mpegpreset

/etc/localtime

Time zone info

/etc/sudoers

List of users with sudo privileges

/opt/avid/etc/avid/avid-interplay-

central/ssl/jetty.keystore

/opt/avid/etc/avid/avid-interplay-

central/config/application.properties

Jetty keystore and SSL certificates and

usage passwords.

Pacemaker configuration

(restored as /root/pcmk.conf)

Pacemaker configuration

/etc/corosync/corosync.conf

Corosync config file

/etc/drbd.d/r0.res

DRDB config file

ICS database

ICS database (ACS, UMS and ICPS

data). This includes user information.

RHEL user names and passwords

*** Not backed up. ***

To back up the system settings and ICS database:

1. Mount the USB key containing the system-backup script.

In this document, see “Mounting and Unmounting the USB Key” on page 6

2. Change to the mount point. For example:

cd /media/usb

3. Back up the ICS settings and database using the backup script.

./system-backup.sh –b

A backup file is written to the USB key:

/media/usb/sys-backup/ics_setup_files.tar.gz

Since the system-backup script also calls the avid-db command, a backup of the ICS

database is also written to the following directory (on the ICS server):

/var/lib/avid/db/dumps

The backup file on the server has a name has the following form:

ALL-YYYYMMDD_HHMMSSZ.sql.gz.cr

Note: Note the time stamp appended to the file name uses the Universal Time Code

(UTC), not the local time.

Interplay Central Services 1.8 Upgrading Guide

The following message indicates success:

Backup setup successful!

4. Rename the backup file using the Linux mv command. For example:

mv sys-backup sys-backup-<nodename>

The above command renames the directory containing the backup file just created. The

backup file itself (ics_setup_files.tar.gz) remains unchanged inside the directory.

Note:

Renaming the backup file is particularly important if you are backing up multiple

nodes in a cluster. Only the master node backup contains a complete set of backup

information. If you do not rename the master node backup file, it will be overwritten by the

backup from a non-master node.

5. Once the settings are restored, unmount and remove the USB key.

In this document, see “Mounting and Unmounting the USB Key” on page 6

To restore the system settings and ICS database:

1. Mount the USB key containing the system-backup script.

In this document, see “Mounting and Unmounting the USB Key” on page 6

2. Change to the mount point. For example:

cd /media/usb

3. If you renamed the backup file, restore it to the original name.

mv sys-backup-<nodename> sys-backup

4. Restore the ICS settings and database using the backup script.

./system-backup.sh –r

You are asked to confirm the restoration of the ICS database:

Would you like to restore the database now? (y/n)

5. Type “y” (without the quotes) to confirm the action.

You are asked to confirm the shutting down of the Avid services:

All Avid services will be shut down before performing a database

restore operation.

Would you like to continue? [yes/no]

6. Type “yes” (spelled out in full, without the quotes) to confirm the action.

Note: Be careful when typing your response to this question. Typing anything other than

“yes” results in the script exiting without restoring the ICS database. Other items are

restored, but not the ICS database.

Interplay Central Services 1.8 Upgrading Guide

Services are shut down, the ICS database is restored, and services are restarted.

The ICS database service is stopped, and you are prompted to restore the database.

The following message indicates success:

Restoration done!

Your old fstab settings were saved in /root/fstab

Please remove the USB key and reboot the server.

Note: The filesystem table (fstab) file contains information to automate mounting

volumes at boot time. It is not restored automatically.

7. Once the settings are restored, unmount and remove the USB key.

In this document, see “Mounting and Unmounting the USB Key” on page 6

Upgrading Paths

If you are upgrading to Interplay Common Services, you are doing so to get the latest

version for your Interplay Central, Interplay Sphere, or Interplay MAM solution.

Upgrading from 1.2.x or 1.3.x to ICS 1.8

For Interplay Central and/or ICPS 1.2.x and 1.3.x upgrade options, please consult your Avid

representative.

Upgrading to ICS 1.8 for Interplay Central

Since ICS 1.3—which introduced the hardware consolidation and software service colocation

on Linux servers—in some respects Interplay Central Services and Interplay Central are the

same thing. Interplay Central uses all Interplay Central Services, and its version number

increases in lock step with Interplay Central Services.

The following list describes the supported upgrade paths:

• Interplay Central 1.4.x to Interplay Central 1.8.

See “

Upgrading from Interplay Common Services 1.4.x/1.5.x to Interplay Central Services

1.8” on page 20.

• Interplay Central 1.5 to Interplay Central 1.8.

See “

Upgrading from Interplay Common Services 1.4.x/1.5.x to Interplay Central Services

1.8” on page 20.

• Interplay Central 1.6.x/1.7.x to Interplay Central 1.8.

See “

Upgrading from Interplay Central Services 1.6.x/1.7.x to Interplay Central Services

1.8” on page 13.

Interplay Central Services 1.8 Upgrading Guide

Upgrading to ICS 1.8 for Interplay Sphere

The latest version of the Interplay Sphere plugin requires at least ICS 1.3. Upgrading to ICS

1.8 for Interplay Sphere does not add any new functionality, but you do get the benefit of

the latest bug fixes.

The following list describes the supported upgrade paths:

• Interplay Common Services 1.4.x to Interplay Central Services 1.8.

See “

Upgrading from Interplay Common Services 1.4.x/1.5.x to Interplay Central Services

1.8” on page 20.

• Interplay Common Services 1.5 to Interplay Central Services 1.8.

See “

Upgrading from Interplay Common Services 1.4.x/1.5.x to Interplay Central Services

1.8” on page 20.

• Interplay Common Services 1.6.x/1.7.x to Interplay Central Services 1.8.

See “

Upgrading from Interplay Central Services 1.6.x/1.7.x to Interplay Central Services

1.8” on page 13.

Upgrading to ICS 1.8 for Interplay MAM

The latest versions of Interplay MAM (4.2.x and 4.3.x) are compatible with Interplay Central

Services 1.8.

The following table describes Interplay MAM and ICPS/ICS compatibility.

Interplay MAM Version

ICPS/ICS Version

Interplay MAM 4.2.3

Interplay Central Services 1.6/1.7

Interplay MAM 4.3

Interplay Common Services 1.4.1

Interplay MAM 4.3.x

Interplay Central Services 1.6/1.7/1.8

Interplay MAM (other)

For ICS 1.8 compatibility with other Interplay MAM releases

please consult an Avid representative.

Note: ICS 1.3 is not supported by any version of Interplay MAM.

Interplay Central Services 1.8 Upgrading Guide

Upgrading from Interplay Central Services 1.6.x/1.7.x to

Interplay Central Services 1.8

Upgrading from ICS 1.6.x/1.7.x to ICS 1.8 requires an upgrade of the Interplay Central

Services, and has no impact on the hardware footprint of the system.

It is a true upgrade; that is, re-imaging the operating system and/or re-installing ICS from

scratch are not necessary. This is sometimes also called an overlay upgrade, since the

operating system (RHEL 6.3) and ICS (1.6.x or 1.7.x) are already present on the server, and

the new software is added to it.

The 1.6.x/1.7.x to 1.8 upgrade includes scripts to facilitate the upgrade process. The manual

backup and restoration of system settings is not required (though backing up is strongly

recommended).

Before You Begin

The ICS 1.6.x/1.7.x to 1.8 upgrade procedure follows a general pattern:

1. Back up system settings and database using the backup script (strongly

recommended)

2. Upgrade the server.

3. Remove the USB key and reboot the server.

Note: Where SSL certificates are in use, additional steps may be required to back up the

private key used to generate the certificate-signing request.

Note: In addition, verify the SSL passwords were placed in the correct file. Otherwise they will

not get backed up and restored. See “Before You Begin: An Important Note on SSL Certificate

Passwords” on page 5.

In the case of a cluster, the above pattern applies, but note the following too:

1. Upgrade the master node first.

2. Once all nodes in the cluster have been upgraded, reset the cluster using the

reactivate-cluster script provided.

3. There is no need to reboot during a cluster upgrade.

Note: This information is called-out in the instructions below.

After You Finish

Once you have upgraded, double check the following items:

• Verify that the /cache directory and subdirectories have the correct ownership.

See “Verifying Cache Directory Permissions” in the ICS 1.8 Installation and

Configuration Guide.

Interplay Central Services 1.8 Upgrading Guide

• Back up the ICS settings and database

See “Backing Up and Restoring System Settings and the ICS Database” on page 8

Upgrading a Single Server System from 1.6.x/1.7.x to 1.8

An upgrade from 1.6.x/1.7.x to 1.8 is a true upgrade. All Linux and ICS system settings

(including the ICS Database) are preserved (though backing up is strongly recommended).

You do not have to manually reconfigure system or network settings. However, you must

manually back up any private key associated with SSL certificates received from Certificate

Authority, if CA-signed certificates are in use.

Note: Before proceeding, back up any private key used to generate a Certificate Signing

Request. In this document, see “Backing Up and Restoring SSL Private Keys” on page 27

Expected downtime: 30 min.

Note: After running the installation script, remove the USB key before rebooting. Rebooting

with the USB key in the server will re-image the disk and all settings will be lost.

1. Prepare and insert the ICS Installation USB key.

In the ICS 1.8 Installation & Configuration Guide, see “Preparing the ICS Installation USB

Key”.

2. Mount the USB key:

In this document, see “Mounting and Unmounting the USB Key” on page 6.

3. Change to the mount point:

cd /media/usb

4. Back up the ICS settings and database using the backup script (optional, highly

recommended):

./system-backup.sh -b

The following message indicates success:

Backup setup successful!

For details on the system-backup script, including the list of what is backed up by the

system-backup script, see “

Backing Up and Restoring System Settings and the ICS

Database” on page 8.

5. Rename the backup file using the Linux mv command. For example:

mv sys-backup sys-backup-<nodename>

Note: Renaming the backup file is particularly important if you are backing up multiple nodes

in a cluster. Only the master node backup contains a complete set of backup information. If

you do not rename the master node backup file, it will be overwritten by the backup from a

non-master node.

Interplay Central Services 1.8 Upgrading Guide

6. Unzip the installation package:

tar -zxovf

Interplay_Central_Services_<version>_<build>_Linux.tar.gz

7. Change to the newly created installation directory:

cd Interplay_Central_Services_<version>_<build>_Linux

8. Run the installation script:

./install.sh

The installation script menu automatically detects if RHEL and a previous version of ICS

are already installed. If true, the script automatically performs an upgrade, stopping

services, upgrading, and restarting services as required.

Note: The upgrade script might appear to pause as it works. This is normal.

Note: Do not re-boot before removing the USB key. Rebooting with the USB key in the server

will re-image the disk and all settings will be lost.

7. Unmount and remove the USB key.

In this document, see “Mounting and Unmounting the USB Key” on page 6

8. With the USB key removed from the server, reboot as prompted by the installation

script.

Note: There is no need to reboot the servers during the cluster upgrade, and doing so while

the cluster is offline may introduce problems. Please ignore the instruction issued by the

installation script to reboot.

9. Once complete, verify version information of the installed ICS components:

ics_version

Service version numbers are returned as follows:

UMS Version: 1.8.x.x

IPC Version: 1.8.x.x

ICPS Version: 1.8.x.x

ICPS Manager Version: 1.8.x.x

ACS Version: 1.8.x.x

ICS installer: 1.8 (Build XX)

Created on <installer creation date>

Note: For version numbers for this release, see the ICS 1.8 ReadMe.

Note: In the case of a cluster upgrade, proceed to upgrade the next server.

10. If you are deploying ICS for Interplay MAM or Interplay Sphere, you must update

Interplay Central configuration settings.

In this document, see “Reconfiguring ICS for Interplay MAM” on page 18

In addition, see “After You Finish” on page 13.

Interplay Central Services 1.8 Upgrading Guide

Upgrading a Cluster System from 1.6.x/1.7.x to 1.8

As for a single server upgrade, Linux and ICS system settings (including the ICS Database) are

preserved (though backing up is strongly recommended). You do not have to manually

reconfigure system or network settings. However, you must manually back up any private

key associated with SSL certificates received from Certificate Authority, if CA-signed

certificates are in use.

Expected downtime: 1 hr. for 2 servers, + 30 min. for each additional server.

Note: Before proceeding, back up any private key used to generate a Certificate Signing

Request. In this document, see “Backing Up and Restoring SSL Private Keys” on page 27

Before you begin:

• Alert end-users to save their work and log out of Interplay Central. The update

terminates the service. Unsaved work might be lost.

• Identify the master, slave, and load-balancing nodes

• Bring the cluster off-line by putting all nodes into standby

To identify the master, slave, and load-balancing nodes:

Recall that there are three types of nodes in a cluster: master, slave, and load-balancing.

The master “owns” the cluster IP address. The slave assumes the role of master in the event

of a failover. Any extra nodes play a load-balancing role, but can never take on the role of

master.

1. Identify the master node of the cluster. Log into any machine in the cluster as root and

type:

crm_mon

2. In the output of that command, look for the line containing “AvidClusterIP”—this service

runs on the master server.

For example, if the crm_mon command output contains the line:

AvidClusterIP (ocf::heartbeat:IPaddr2): Started ics-1

…the master server is ics-1.

3. To identify the slave, look for the line containing “Master/Slave Set”.

For example, if the crm_mon command output contains the lines:

Master/Slave Set: ms_drbd_postgres [drbd_postgres]

Masters: [ ics-1 ]

Slaves: [ ics-2 ]

…the slave server is ics-2.

4. To identify the load-balancing nodes, look for the line containing “Clone Set”.

For example, if the crm_mon command output contains the lines:

Clone Set: AvidAllEverywhere [AvidAll]

Interplay Central Services 1.8 Upgrading Guide

Started: [ ics-1 ics-2 ics-3]

…the extra server in this case is ics-3.

To bring the cluster off-line:

1. Alert all end-users to save their work and log out of Interplay Central (if you have not

already done so).

2. Bring the cluster off-line by putting the load-balancing nodes into standby mode:

crm node standby <node name>

3. Next, put the slave node into standby mode:

crm node standby <node name>

4. Finally, put the master node into standby mode:

crm node standby <node name>

5. The upgrade can now be performed on the cluster.

To upgrade the cluster:

1. With all the nodes in standby mode, upgrade all machines in the cluster following the

instructions for upgrading a single node.

In this document, see “Upgrading a Single Server System from 1.6.x/1.7.x to 1.8

” on

page 14.

Note: There is no need to reboot the servers during the cluster upgrade, and doing so while

the cluster is offline may introduce problems. Please ignore the instruction issued by the

installation script to reboot.

2. Once you have upgraded all the machines, log in to the master node and restart the

cluster using the script provided:

sh /opt/avid/cluster/bin/reactivate-cluster

The reactivate-cluster script brings the nodes out of standby node and back online,

amongst other things.

3. Once the script completes, the cluster is ready for use. Restart the following services so

they register correctly on the newly created instance of the message bus:

service acs-ctrl-messenger restart

service avid-aaf-gen restart

service avid-mpd restart

Note: Restarting the Interplay Pulse (avid-mpd) service is only needed if Interplay Pulse

(separate installer) is installed on the system.

Interplay Central Services 1.8 Upgrading Guide

With the services restarted, the cluster is ready for use.

4. If you are deploying ICS for Interplay MAM or Interplay Sphere, you must update

Interplay Central configuration settings on the master node.

In this document, see “Reconfiguring ICS for Interplay MAM” on page 18

In addition, see “After You Finish” on page 13.

Reconfiguring ICS for Interplay MAM or Interplay Sphere

In previous releases, the ICPS Player embedded in the Interplay Central UI required its own

user name and password for communicating with the ICS server (from which it receives

video). In ICS 1.8 this is no longer the case. In ICS 1.8 the ICPS Player now uses the

credentials of the logged-in user.

As a result, if you have deployed ICS in support of Interplay MAM or Interplay Sphere, you

will need to reconfigure ICS to support these applications.

To reconfigure ICS for use with Interplay MAM:

1. With the server (or cluster) up and running, log in to Interplay Central as an

administrator level-user, using the host name or IP address of the server or cluster.

2. Select Users from the Layout selector.

3. Create a special role for the MAM user by clicking on the Create Role button in the Roles

pane.

4. Click the Create Role button.

5. In the Details pane, type the properties for the new role:

• Role name (e.g. MAM)

• Advance License

• Do not assign the MAM role any layouts

6. Click Apply to save your changes.

The new MAM role is added to the Roles pane.

7. Create a MAM user by clicking the Create User button.

8. In the Details pane, type the properties for the new user:

• User name (e.g. MAM)

• Password

• Uncheck “User must change password at next sign-in”

• Check “User cannot change password

9. Drag the MAM role from Roles pane to the Role section of the Details pane for the new

user.

Interplay Central Services 1.8 Upgrading Guide

10. Click Save to save your changes.

The new MAM user is added to the User Tree, as a top-level user.

For more information on creating users and roles, see the “Interplay Central Administration

Guide”.

To reconfigure ICS for use with Interplay Sphere:

1. With the server (or cluster) up and running, log in to Interplay Central using the host

name or IP address of the server or cluster.

2. Select System Settings from the Layout selector.

3. In the Settings pane, click Player.

4. Enter the user name and password reserved for Sphere (e.g. sphere).

5. Click Apply to save your changes.

Interplay Central Services 1.8 Upgrading Guide

Upgrading from Interplay Common Services 1.4.x/1.5.x to

Interplay Central Services 1.8

Upgrading from ICS 1.4.x/1.5 to ICS 1.8 requires an upgrade from Interplay Common

Services (ICS) 1.4.x/1.5 to Interplay Central Services 1.8 and has no impact on the hardware

footprint of the system. Upgrading a cluster requires some additional configuration steps

and rebuilding the cluster.

Before You Begin

The ICS 1.4.x/1.5.x to 1.8 upgrade procedure follows a general pattern:

1. Back up system settings and database.

2. Upgrade the server.

3. Restore the system settings and database.

Note: Where SSL certificates are in use, additional steps may be required to back up the

private key used to generate the certificate-signing request.

Note: In addition, verify the SSL passwords were placed in the correct file. Otherwise they will

not get backed up and restored. See “

Before You Begin: An Important Note on SSL Certificate

Passwords” on page 5.

In the case of a cluster, the above pattern applies, but note the following too:

1. Upgrade the master node first.

2. Re-start DRBD on the original master node first (i.e. don’t aim to create a new

master).

Recall that DRBD replicates the ICS database from master to slave node. It is thus

important that you start DRBD is on the original master node first. During the

upgrade process, it will be the only node with a database. If you set up DRBD on the

slave node first, it will become master, and will propagate an empty database.

Note: This information is called-out in the instructions below.

Upgrading a Single Server System

An ‘upgrade’ from ICS 1.4.x/1.5.x to 1.8 is actually a fresh software installation. Scripts are

provided to backup and restore ICS system settings and the ICS Database so you do not have

to manually reconfigure the system. However, you must manually back up any private key

associated with SSL certificates received from Certificate Authority, if CA-signed certificates

are in use.

Note: Before proceeding, back up any private key used to generate a Certificate Signing

Request. In this document, see “Backing Up and Restoring SSL Private Keys” on page 27

Expected downtime: 1 hr.

1. Prepare and insert the ICS Installation USB key.

Page is loading ...

Avid Interplay Central Services 1.8 User guide

Brand: Avid

Model: Interplay Central Services 1.8

Category: Database software

Type: User guide

Download PDF

report

Avid Interplay Central Services 1.8 User guide

Avid Interplay Central Services 1.8 User guide

Related papers

Other documents