avid interplay central services 1.8 upgrading...

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.

http://www.avid.com/support

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

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

Interplay Central Services 1.8 Upgrading Guide

2

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


3

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


4

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.


5

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\:1lfc1n7n1l1618qm18qo1kxw1n3v1lc6

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.


6

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.


7

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:

cd

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


8

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


9

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.


10

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.


To restore the system settings and ICS database:

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


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.


11

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.


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.


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.


12

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.


13

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.


14

· 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:


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.


15

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.


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.


16

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.


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]


17

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:


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


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.


18

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.


19

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.


20

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.


Expected downtime: 1 hr.

1. Prepare and insert the ICS Installation USB key.


21


2. Mount the USB key:


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

From the directory to which you mounted the USB key, type:

./system-backup.sh –b The following message indicates success:


4. Install ICS 1.8.

In the ICS 1.8 Installation & Configuration Guide, see “Installing RHEL and the ICS Software”.

5. Restore the ICS settings and database using the restore script.


./system-backup.sh –r

6. (Interplay MAM) The ICS servers settings restore operation deposits a copy of the server’s previous fstab file, which may contain required mount points (for example mount points where Interplay MAM proxies are stored). You can copy the corresponding fstab entries to re-mount those volumes.

· Open the fstab backup residing at /root/fstab for editing · Copy the required mount point entries in that file · Paste them into the server’s current fstab file residing at /etc/fstab

11. It is a good idea to reboot after a system restore. Before you do that, unmount and remove the USB key.


12. Due to the host name change (a result of the upgrade) the major ICS services should be restarted:

avid-ics stop avid-ics start

Upgrading a Cluster System With the introduction of DRBD, upgrading from ICS 1.4.x/1.5.x to 1.8 requires configuring DRBD and rebuilding the cluster. As for a single server upgrade, a script is provided to back up and restore system and other settings. However, you must manually back up any private


22

key associated with SSL certificates received from Certificate Authority, if CA-signed certificates are in use.

Expected downtime: 3 hrs. for 2 servers, + 1 hr. for each additional server.


To prepare for the upgrade and shut down the cluster:

1. Prepare ICS 1.8 installation USB key.


2. Identify the master node of the cluster. Log into any machine in the cluster as root and type:

crm_mon

3. 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.

4. Insert the ICS installation USB key in the master server and mount it.


5. Back up the ICS server settings and database using the backup script.


./system-backup.sh -b



6. Shut down the cluster.

For a 1.4.x/1.5.x upgrade, on all nodes (slave first, then master), type:

service pacemaker stop service corosync stop

Note: Run the above command(s) on the slave node first, then on the master node second. If there are other nodes in the cluster, the commands must also be run on them, but in any order.


23

To upgrade the master node:

1. Install ICS 1.8 on the master node.


2. Restore the ICS server settings and database using the restore script.

From the directory to which you mounted the USB key, type: ./system-backup.sh -r

3. It is a good idea to reboot after a system restore. Before you do that, unmount and remove the USB key.


4. Verify if DRBD is running:

chkconfig –-list drbd There are two dashes (“- -“) with no space between them , in the above command.

5. If running, turn off DRBD:

chkconfig drbd off

6. Reboot the server.

7. (Interplay MAM) The ICS servers settings restore operation deposits a copy of the server’s previous fstab file, which may contain required mount points (for example mount points to where Interplay MAM proxies are stored).

Copy the corresponding fstab entries to re-mount those volumes:

· Open the fstab backup residing at /root/fstab for editing · Copy the required mount point entries in that file · Paste them into the server’s current fstab file residing at /etc/fstab

8. Restore the private key(s), if needed.

In this document, see “Backing Up and Restoring ” on page 27.

To upgrade the slave node:

1. Insert the ICS installation USB key in node #2 and mount it.


2. Backup the ICS system settings using the backup script.

From the directory to which you mounted the USB key, type: ./system-backup.sh -b

Note: Since corosync is not running on this node, no database is backed up.

3. Install ICS 1.8 on node #2.


24


4. Restore the ICS server settings using the restore script (in this case there is no database to restore).

From the directory to which you mounted the USB key, type: ./system-backup.sh -r

5. Before rebooting, unmount and remove the USB key.


6. Verify if DRBD is running:

chkconfig –-list drbd There are two dashes (“- -“) with no space between them , in the above command.

7. If running, turn off DRBD:

chkconfig drbd off

8. Reboot the server.

9. (Interplay MAM) The ICS servers settings restore operation deposits a copy of the server’s previous fstab file, which may contain required mount points (for example mount points to where Interplay MAM proxies are stored). You can copy the corresponding fstab entries to re-mount those volumes. · Open the fstab backup residing at /root/fstab for editing · Copy the required mount point entries in that file · Paste them into the server’s current fstab file residing at /etc/fstab

To upgrade nodes 3+:

· Repeat steps #1 through #9 in the above procedure for nodes #3+.

Omit the steps relating to DRBD. DRBD should not be running on the non-master, non-slave nodes.

To rebuild the cluster:

1. Set up DRBD on the master node.

Note: It is very important that you do this on the master node, since it is the only node with a database, restored in an earlier step. The slave node has no database. If you set up DRBD on the slave node first, it will become master, and will incorrectly propagate its empty database.

In the ICS 1.8 Installation & Configuration Guide, see “Setting Up DRBD”.

2. Set up DRBD on a second node (any other node).

In the ICS 1.8 Installation & Configuration Guide, see “Setting Up DRBD”.

3. If you have a RAID 5 cache set up for the ICS cache, you must mount the cache.


25

In this document, see “Mounting the Cache” on page 25.

4. If you have Gluster set up to replicate the ICS cache, you must reconfigure Gluster.

In this document, see “Reconfiguring Gluster” on page 26.

5. Set up Corosync and the cluster on the master node. Exclude DRBD from nodes #3+.

In the ICS 1.8 Installation & Configuration Guide, see “Starting the Cluster Services”.

Note: With ICS 1.6 a new parameter (“--rabbitmq_master-<master>”) was added to the setup-corosync command. The command now has the following general form:

/usr/maxt/maxedit/cluster/resources/cluster setup-corosync --corosync-bind-iface=eth0 --rabbitmq_master=<master>

…where <rabbitmq_master> is the master node (e.g. ics-dl360-1). This should be the same as the DRBD master node specified earlier.

6. Set up Corosync on the remaining nodes.

In the ICS 1.8 Installation & Configuration Guide, see “Joining the Cluster”.

Similarly, be sure to use the new form of the setup-corosync command as outlined above.

Mounting the Cache in a 1.4.x/1.5.x to 1.8 Upgrade Before you can begin reconfiguring Gluster, the RAID 5 cache must be mounted. This is done by adding an entry to the RHEL filesystem table (fstab). The system-backup script saved the filesystem table, and restored it to the root user home directory (/root).

1. Open the restored copy of the old filesystem table for editing:

vi /root/fstab

2. Copy the line that mounts /cache.

It should look like this:

/dev/mapper/vg_ics_cache-lv_ics_cache /cache ext4 rw 0 0

3. Open the current filesystem table and paste the information:

vi /etc/fstab

4. You may also wish to copy the lines that mount the other caches used by gluster.

They look like this (for a server named ics-dl360-1):

ics-dl360-1:/gl-cache-dl /cache/download glusterfs defaults 0 0 ics-dl360-1:/gl-cache-fl /cache/fl_cache glusterfs defaults 0 0 ics-dl360-1:/gl-cache-md /cache/metadata glusterfs defaults 0 0

The above lines are needed at a later step in the upgrade.


26

5. Be sure to comment them out (for now) when you paste them into the current filesystem table (/etc/fstab):

# ics-dl360-1:/gl-cache-dl /cache/download glusterfs defaults 0 0 # ics-dl360-1:/gl-cache-fl /cache/fl_cache glusterfs defaults 0 0 # ics-dl360-1:/gl-cache-md /cache/metadata glusterfs defaults 0 0

You will uncomment them after you set up gluster.

6. Save and exit the file (<Esc>:wq>).

7. Mount the /cache volume (all the of fstab):

mount -a The above command causes Linux to read the contents of the fstab file and mount its contents.

8. Verify the cache has been mounted correctly:

df -h

Reconfiguring Gluster in a 1.4.x/1.5.x to 1.8 Upgrade When you upgrade from ICS 1.4.x/ 1.5.x to ICS 1.8 the previous Gluster configuration is removed and you must reconfigure Gluster. However, the Gluster replication bricks are not removed, so you must do some additional steps not documented in the ICS 1.8 Installation & Configuration Guide. These steps must be done manually, as described here.

First, insert the USB key and mount it:

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

Next, if you have not already done so, mount the cache located on the RAID 5 volume:

· In this document, see “Mounting the Cache in a 1.4.x/1.5.x to 1.8 Upgrade” on page 25.

Next, refer to the section “Replicating the Cluster File Caches” in the ICS 1.8 Installation & Configuration Guide, and do the following:

1. “Installing Gluster”

2. “Creating the Trusted Storage Pool”

3. “Configuring the GlusterFS Volumes”

In this section, before performing steps #1-3, you need to remove the old Gluster replication bricks. (On each node in the cluster) enter the following commands:

setfattr -x trusted.glusterfs.volume-id /cache/gluster/gluster_data_download setfattr -x trusted.gfid


27

/cache/gluster/gluster_data_download rm -rf /cache/gluster/gluster_data_download/.glusterfs setfattr -x trusted.glusterfs.volume-id /cache/gluster/gluster_data_fl_cache setfattr -x trusted.gfid /cache/gluster/gluster_data_fl_cache rm -rf /cache/gluster/gluster_data_fl_cache/.glusterfs setfattr -x trusted.glusterfs.volume-id /cache/gluster/gluster_data_metadata setfattr -x trusted.gfid /cache/gluster/gluster_data_metadata rm -rf /cache/gluster/gluster_data_metadata/.glusterfs

Note: If some of these commands return a “No such attribute” message, you can ignore it and proceed with the next command.

Note: If you receive a “no such file or directory” error, it means the RAID 5 cache was not mounted correctly.

Continue with the remaining procedures in the ICS 1.8 Installation & Configuration Guide as follows:

4. If you copied the backed up fstab entries, you need not follow the procedure “Mounting the GlusterFS Volumes in Linux”—as the volumes are already in /etc/fstab. Simply uncomment the lines you copied instead.

5. “Testing the Cache”

6. “Ensuring the Gluster is On at Boot”

7. Proceed with the next step in your upgrade process.

Backing Up and Restoring SSL Private Keys Upgrading can be a “true” (non-destructive) upgrade, or can involve a fresh install of RHEL. For fresh installs, the system-backup script has been provided to back up and restore system settings related to ICS, including SSL data (the Jetty keystore and certificates it contains). However, if you stored the private key (jettyPrivateKey.key) file in in the root user home directory (/root) be sure to back it up manually before the upgrade. Backing up private key files is good practice, whatever the type of upgrade being performed.

Note: If the private key was not backed up elsewhere, it is doubly important to back up the keystore before performing the upgrade. The private key is used to generate Certificate Signing Requests (CSRs).


28

For more information, in the ICS 1.8 Installation & Configuration Guide, see “Appendix B: Handling SSL Certificates”.

To back up and restore the Jetty keystore:

1. Locate the separate private key file used to generate the Certificate Signing Request (if any).

The default name is jettyPrivateKey.key. During its creation, it was suggested you store it in the following directory:

/root

2. Copy the private key to a safe location (off the ICS server), restoring it at an appropriate step in the upgrade.


29

Appendix A: Frequently Asked Questions

What is the difference between the system-backup script and the avid-db utility? The system-backup script is used to back up and restore important ICS system settings and is found on the USB installation key. The avid-db utility is used to back up and restore the ICS database (including user information), and is found in the /opt/avid/bin directory.

What About Interplay Central Distribution Service (ICDS)? If you are upgrading from Interplay Central 1.4 or later, ICDS is already separately installed and configured, and the settings configured for it are backed up and restored as part of the upgrade process.

Note: Interplay Central 1.8 requires ICDS 3.0.8. In the ICS 1.8 Installation & Configuration Guide, see “Installing the Interplay Central Distribution Service”.

What Do I Do With the Unused Hardware After an Upgrade from 1.2.x? (Interplay Central only) If you are upgrading from Interplay Central 1.2.x to Interplay Central 1.8, some hardware used in 1.2.x is no longer required in 1.8. You can decommission this hardware entirely, though you may want to repurpose it for other uses. Here are some suggestions:

· Repurpose the former Interplay Central middleware servers to run ICDS (required by Interplay Central). In this case, uninstall Interplay Central. If necessary, update Avid Service Framework (ASF), the Windows ISIS client, and then the ICDS package that came with your ICS installation package.

· If the former Interplay Central middleware servers are AS3000s, you may want to repurpose them as Interplay Transcode engines, or some other Interplay service engine. Consult an Avid representative for options.


30

Appendix B: Migrating the UMS Database to a Test Node ICS maintains a database containing information for the following subsystems:

· ACS - Avid Common Services · ICPS - Interplay Central Playback Services · UMS - User Management Services

In some situations you might need to extract just the UMS data. For example, you may want to update the ICS database of a test system with user names and passwords, roles, and so on, from a ICS system in a production setting. This appendix provides the procedures for doing so.

Migrating the 1.6.x (or later) UMS Database To extract the UMS database from an ICS 1.6.x (or later) system, use the avid-ums-backup and avid-ums-restore utilities:

avid-ums-backup <backup-filename> [-pp <postgres password>] [ -pu <postgres user>]

avid-ums-restore <backup-filename> [-pp <postgres password>] [-pu <postgres user>]

The tools for working with the UMS database are located in the following directory:

/opt/avid/bin

To extract the UMS database from an ICS 1.6.x (or later) system:

1. Log in to the master node as root and dump the UMS database:

avid-ums-backup <backup-filename> [-pp <postgres password>] [-pu <postgres user>] For example:

avid-ums-backup backup.sql -pu postgres

The system responds with an indication of success:

UMS database was backed up successfully.

2. Move the file to the server of interest in preparation for restoring it to the ICS 1.8 system.

To restore the UMS database to a ICS 1.8.x system:

1. Log in to the master node as root

2. Stop the UMS service:

service avid-ums stop


31

In the case of a cluster, issue the following command instead:

crm resource stop AvidUMS

3. Restore the UMS database:

avid-ums-restore <backup-filename> [-pp <postgres password>] [-pu <postgres user>] For example:

avid-ums-restore backup.sql -pu postgres Once you confirm the restore operation, the operation begins. It can take a minute or two.

The system responds with an indication of success:

UMS database was restore successfully.

4. Confirm the UMS service was restarted by the avid-ums-restore utility:

service avid-ums status In the case of a cluster, issue the following command instead:

crm resource status AvidUMS

Migrating the 1.4.x/1.5.x UMS Database To extract the UMS database from an ICS 1.4.x/1.5.x system and load it into an ICS 1.8 system, you must use PostgreSQL tools directly, at both ends.

To extract the UMS database from an ICS 1.4.x/1.5.x System:

1. Log in to the master node as root and dump the UMS database:

pg_dump –U postgres uls > uls_backup.sql

2. Move the file to a safe location (off the server) in preparation for restoring it to the ICS 1.8 system.

To restore the ICS 1.4.x/1.5.x UMS database to the ICS 1.8 system:

5. Log in to the master node as root

6. Stop the UMS service:

service avid-ums stop In the case of a cluster, issue the following command instead:

crm resource stop AvidUMS


32

7. Drop the current UMS database from the ICS database:

psql –U postgres –c "drop database uls;"

8. Create a new UMS database:

psql –U ulsuser postgres –c "create database uls;"

9. Import the ICS 1.5 UMS database:

psql –U ulsuser uls < uls_backup.sql

10. Start the UMS service:

service avid-ums start In the case of a cluster, issue the following command instead:

crm resource start AvidUMS


33

Appendix C: Glossary This section defines some terms used in this document.

Interplay Central Interplay Central is the set of web-based and mobile applications that are powered by Interplay Common Services. Interplay Central can be configured to work with Interplay, ISIS, and iNews to provide video editing, story editing, and logging solutions for broadcasters and newsrooms.

Prior to Interplay Central 1.3, the middleware and user management services ran separately on Windows servers.

Interplay Sphere Interplay Sphere is a Media Composer and NewsCutter plug-in that enables remote editing workflows. From any remote connection, you can log into a remote Interplay/ISIS and upload media from the field, as well as playback media residing on the remote ISIS. ICPS/ICS are used to provide the remote playback capability.

Interplay MAM Interplay MAM is a media archive solution, extensible to serve several media lifecycle workflows from ingest to distribution. ICPS/ICS are used to provide web-based playback of media proxies registered in the MAM database.

Interplay Central Services (ICS) Interplay Central Services (ICS) is the set of software services that work together to power Interplay Central. Additionally, ICS provides video playback for Interplay Sphere and Interplay MAM.

With the release of ICS 1.3 in December 2012, all Interplay Central services (including Interplay Central middleware, Interplay Central user management, and the Interplay Central Playback Service run on the same Linux server.

Interplay Central Playback Service (ICPS) Interplay Central Playback Service is one of the ICS services. It provides video playback of video assets for Interplay Central, Interplay Sphere, and Interplay MAM clients. ICPS can decode Avid MXF data on ISIS and many other standard file formats on standard and proprietary storage systems.

Prior to ICS 1.3 (and with it Interplay Central 1.3) the ICPS service ran on its own Linux server.


34

ICS System Settings In this document, the upgrade procedures refer to backing up and restoring ICS system settings. These settings include server network configuration, OS user settings (e.g., the root user password), SSL certificate configuration, load balancing configuration, and the video player configuration.

ICS Platform Settings ICS platform settings are the settings you configure in the Interplay Central Admin UI (e.g., the connections to Interplay, ISIS, and iNEWS).

ICS Database In this document, the upgrade procedures refer to backing up and restoring the ICS database. This database stores ICS platform.

Interplay Central User Management Database Since ICS 1.3, the Interplay Central User Management database has been part of the ICS database. Prior to ICS 1.3, the Interplay Central user management database was a separate database on the Interplay Central middleware servers

This explains why when upgrading from Interplay Central 1.2.x to 1.8, migrating the Interplay Central user management database is required. The migration of the database merges the user management data into the ICS database.

Corosync Corosync is a software service used by ICS to manage ICS software services across a multi-node server cluster. Corosync orchestrates the stopping and starting of software services on nodes in the cluster to obtain a highly available system.

Distributed Replicated Block Device (DRBD) DRBD refers to block devices designed as a building block to form high availability (HA) clusters. DRBD can be understood as network based raid-1. In ICS, DRBD is used to replicate the ICS database, allowing for a more reliable failover in more severe software and service failures.

DRBD was introduced in ICS 1.4—configuring DRBD is a required step for cluster setups only.


35

Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc.

The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license agreement.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Avid Technology, Inc.

Copyright © 2013 Avid Technology, Inc. and its licensors. All rights reserved.

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.

Trademarks

Adrenaline, AirSpeed, ALEX, Alienbrain, Archive, Archive II, Assistant Avid, Avid Unity, Avid Unity ISIS, Avid VideoRAID, CaptureManager, CountDown, Deko, DekoCast, FastBreak, Flexevent, FXDeko, iNEWS, iNEWS Assign, iNEWS ControlAir, Instinct, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, Interplay, ISIS, IsoSync, LaunchPad, LeaderPlus, ListSync, MachineControl, make manage move | media, Media Composer, NewsCutter, NewsView, OMF, OMF Interchange, Open Media Framework, Open Media Management, SIDON, SimulPlay, SimulRecord, SPACE, SPACEShift, Sundance Digital, Sundance, Symphony, Thunder, Titansync, Titan, UnityRAID, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, and Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

All other trademarks contained herein are the property of their respective owners.

Interplay Central Services v1.8 Upgrading Guide• 26 March 2014

• This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

http://www.avid.com/US/about-avid/legal-notices/patent-marking

avid interplay central services 1.8 upgrading...

Documents