Avid MediaCentral 2.2 User guide

Brand: Avid

Model: MediaCentral 2.2

Category: Software

Type: User guide

Avid MediaCentral

Platform Services

Version 2.2 Upgrading Guide

Document Version: 1.0.1

This document is a guide to upgrading to MediaCentral Platform Services (MCS) 2.2 from a

previous version of MCS or Interplay Central Services (ICS). It also includes instructions on

migrating the UMS database from a production system to a test system.

Note: For a list products qualified for use with MCS 2.2, and the supported RHEL operating

system, see the Avid MediaCentral Platform V2.2 ReadMe.

Note: The Gluster version changed and additional Gluster packages are required as of MCS 2.0.

See “Obtaining Gluster” in the MediaCentral Platform V2.2 ReadMe.

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 MCS 2.2 documentation can be found

here:

http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-2-x-

Documentation

Revision History

Date Revised

Version

Changes Made

March 26, 2015

1.0

First publication

April 17, 2015

1.0.1

Fixed incorrect references to MCS 2.1.

About MCS 2.2

Please see the MediaCentral Platform 2.2 ReadMe and any ReadMe documents pertaining

to the solution(s) by which MCS is used.

MediaCentral Services 2.2 Upgrading Guide

Contents

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

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

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

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

How to Use this Guide ............................................................................................................................... 4

Operating System ....................................................................................................................................... 4

Update Installation versus Full Installation ................................................................................................ 5

Obtaining the MCS Installation Package .................................................................................................... 5

Obtaining Gluster ....................................................................................................................................... 5

Security Updates ........................................................................................................................................ 5

An Important Note on SSL Certificate Passwords ...................................................................................... 5

Upgrading Media | Index and Multi-Zone Deployments ........................................................................... 6

Resetting Layouts After Upgrading from V2.0 to V2.2 .............................................................................. 7

Resetting Layouts After Upgrading from ICS V1.6 or Earlier ..................................................................... 7

Setting Gluster Volume Ownership Permanently ...................................................................................... 7

Upgrading Paths ......................................................................................................................................... 9

Upgrading from 1.2.x or 1.3.x to MCS 2.2 .............................................................................................. 9

Upgrading to MCS 2.2 for Interplay Central ........................................................................................... 9

Upgrading to MCS 2.2 for Media Composer | Cloud ........................................................................... 10

Upgrading to MCS 2.2 for Interplay | MAM ......................................................................................... 10

Special Note: Upgrading from MCS 2.0 ................................................................................................ 10

Upgrading a Single Server RHEL 6.5 System to MCS 2.2 .......................................................................... 11

Installing MCS 2.2 Using the Update Installation ................................................................................. 11

Upgrading a Cluster RHEL 6.5 System to MCS 2.2 ................................................................................... 12

Identifying the Master, Slave and Load-Balancing Nodes .................................................................... 13

Bringing the Cluster Off-line ................................................................................................................. 13

Updating the Cluster ............................................................................................................................ 14

Upgrading a Single Server RHEL 6.3 System to MCS 2.2 .......................................................................... 16

Backing Up System Settings and Installing RHEL 6.5 & MCS 2.2 .......................................................... 17

Restoring System Settings and Migrating User Settings ...................................................................... 18

Verifying and Configuring Date and Time Synchronization Settings .................................................... 19

Logging in and Backing Up the New System Settings........................................................................... 20

Upgrading a Cluster RHEL 6.3 System to MCS 2.2 ................................................................................... 21

MediaCentral Services 2.2 Upgrading Guide

Identifying the Master, Slave and Load-Balancing Nodes .................................................................... 21

Backing Up Master Node System Settings and Bringing Down the Cluster ......................................... 22

Upgrading the Master Node ................................................................................................................. 23

Restoring System Settings and Migrating User Settings on the Master Node ..................................... 24

Verifying and Configuring Date and Time Synchronization Settings .................................................... 25

Upgrading the Slave Node and Load-Balancing Nodes ........................................................................ 26

Setting up the Cluster and Cache Replication ...................................................................................... 27

Validating the Cluster and Backing Up the New System Settings ........................................................ 27

Reconfiguring ICS for Interplay | MAM or Media Composer | Cloud in an Upgrade from ICS 1.7 or Earlier

................................................................................................................................................................. 28

Reconfiguring MCS for Use with Interplay | MAM .............................................................................. 28

Reconfiguring MCS for Use with Media Composer | Cloud ................................................................. 29

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

Appendix A: Frequently Asked Questions................................................................................................ 31

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

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

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

Appendix C: Mounting and Unmounting the USB Key ............................................................................ 34

Appendix D: Deleting the RAID 5 ............................................................................................................. 35

Appendix E: Backing Up and Restoring System Settings and the ICS/MCS Database ............................. 38

Appendix F: Glossary ................................................................................................................................ 43

MediaCentral ........................................................................................................................................ 43

Media Composer | Cloud ..................................................................................................................... 43

Interplay | MAM................................................................................................................................... 43

MediaCentral Platform Services (MCS) ................................................................................................ 43

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

MCS System Settings ............................................................................................................................ 44

MCS Platform Settings .......................................................................................................................... 44

MCS Database ...................................................................................................................................... 44

MediaCentral User Management Database ......................................................................................... 44

Corosync ............................................................................................................................................... 44

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

Copyright and Disclaimer ......................................................................................................................... 45

MediaCentral Services 2.2 Upgrading Guide

Overview

Upgrading to MediaCentral Platform Services (MCS) 2.2 for MediaCentral, Media

Composer | Cloud, and Interplay | MAM, 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. When upgrading from the earliest

versions of Interplay Common Services (ICS) the upgrade involves significant changes to the

hardware topology of the system.

Note: Beginning with version 2.0, the term “MediaCentral Platform Services” replaces

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

“Interplay Central Playback Service.”

There are two main upgrade paths to MCS 2.2, depending on the currently installed

operating system:

• RHEL 6.5 – If this is the currently installed OS, the upgrade is non-destructive and

largely automated. Manually backing up system settings and MCS Database is not

required, but recommended.

• RHEL 6.3 and earlier – The upgrade involves a clean installation of RHEL 6.5 and

MCS. Manually backing up system settings and MCS database before the upgrade

and restoring them after is mandatory.

When the upgrade path involves a RHEL version change, you must also manually

back up any private keys associated with SSL certificates received from a Certificate

Authority, if CA-signed certificates are in use. In the case of a cluster, you must

manually re-create the cluster and reconfigure cache replication (if used).

How to Use this Guide

This guide documents the overall upgrade process for the supported upgrade scenarios. It

must be used in conjunction with the MCS 2.2 Installation and Configuration Guide. For

clustering, you might find it helpful to refer to the most recent edition of the MCS Clustering

Guide too – for validation of the cluster post-installation, for example.

For each step in the overall upgrade process, this document offers the following guidance:

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

- or -

• Cross-references a section in the MCS 2.2 Installation and Configuration Guide

In the second case, the heading of the relevant section in the MCS 2.2 Installation and

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.

Operating System

MCS 2.2 requires RHEL 6.5. In addition, whether performing an upgrade or a full installation,

the MCS installer requires the RHEL 6.5 ISO to be mounted, so you must obtain the RHEL 6.5

MediaCentral Services 2.2 Upgrading Guide

ISO. This is true, even when performing an upgrade where the operating system does not

change.

Note: Red Hat has issued a security advisory for RHEL 6.5. See “Security Updates” on page 5.

For convenience, the following table lists the ICS/MCS releases and corresponding RHEL

versions.

ICS/MCS Version

RHEL Version

ICS 1.2.3 – 1.5

RHEL 6.2

ICS 1.6 – 1.8

RHEL 6.3

ICS 1.8.1 – MCS 2.2

RHEL 6.5

Update Installation versus Full Installation

The MCS 2.2 release can be installed as a full installation that performs a clean installation of

RHEL, overwriting the system disk. In this case, you prepare a USB key, insert and reboot

from it. For an existing MCS installation with a supported RHEL version, it can be installed as

an upgrade. In this case, you prepare the USB key and trigger the installation script

manually. You do not reboot from it. The installation package and USB key preparation is the

same in both cases.

Obtaining the MCS Installation Package

The MCS 2.2 release is available directly on the Avid Download Center.

Obtaining Gluster

If are installing Gluster, note that since MCS 2.0 a new version of Gluster is required, and

additional Gluster packages.

For package names and download instructions, please consult the MediaCentral Platform

2.2 ReadMe.

Security Updates

Important: Red Hat has issued security advisories for RHEL 6.5. Once you have installed the

operating system, please take a moment to resolve the security vulnerabilities. For

instructions, see the “Security Updates” section in the MediaCentral Platform 2.2 ReadMe.

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

MediaCentral Services 2.2 Upgrading Guide

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 MCS 2.2 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.

Upgrading Media | Index and Multi-Zone Deployments

If your deployment is configured for Media | Index and multi-zone, note the following:

MediaCentral Services 2.2 Upgrading Guide

• Upgrade Slave Zones First: If you cannot bring all zones off-line at once, upgrade

the slave zone(s) before the master zone.

Note that an upgraded slave zone system no longer has access to the centralized

user management service (UMS), which is owned by the master zone. Users in the

upgraded slave zone can continue to log in —the local, read-only copy of the UMS

database is used — but you cannot create new users.

• Delete the Media| Index System Data Index: The system data index contains

information on registered systems and localization strings for display fields. In

initialized systems it also contains production data. If Media Index is configured, you

must delete the system data index in the master zone before the upgrade. Note that

deleting the system data index restores a clean index state. For instructions, see the

Avid Media | Index Configuration Guide.

Resetting Layouts After Upgrading from V2.0 to V2.2

Three panes used in MediaCentral UX v2.0 were dropped as of MediaCentral UX v2.1:

• Markers pane: redesigned as Logging pane.

• Layouts pane in Users Layout: replaced by drag-and-drop functionality.

• Search pane in Users Layout: replaced by Filter field.

After Media Central UX is upgraded to v2.2, users who had signed out of V2.0 with these

panes open will see them when they sign in again, with the message: “No View

implementation found for type undefined” in the pane. Users need to reset the panes.

To reset the outdated panes, do one of the following:

• Close the outdated panes.

• Reset the layout by selecting Reset Layout from the Layout selector.

Resetting Layouts After Upgrading from ICS V1.6 or Earlier

After upgrading from Interplay Central Services V1.6 or earlier, users who had previously

signed in will see the Assets pane and Search panes from their most recent session.

However, the Assets tabs and Search panes are not usable.

This problem does not occur when upgrading from ICS V1.7 to MediaCentral Platform V2.2.

To reset the Assets pane and Search panes, do one of the following:

• Close all open Assets tabs and Search panes and reopen them.

• Reset the layout by selecting Reset Layout from the Layout selector.

Setting Gluster Volume Ownership Permanently

Recall that the following two directories must be owned by user maxmin and have group id

set to maxmin:

cache/gluster/gluster_data_download

MediaCentral Services 2.2 Upgrading Guide

cache/gluster/gluster_data_fl_cache

The directories above are associated with RHEL directories (/cache/fl_cache and

/cache/download) used to store files for http-based streaming, such as media converted to

FLV for file-based playback. They are also used to store media converted to Mpeg2TS for

playback on iOS devices. The download directory contains links to simplify iOS playback.

With Gluster 3.4.0.8, restarting the Gluster daemon (glusterd) results in user ID and group

ownership of the Gluster volumes being changed from maxmim to root, which breaks

playback on iOS devices. Thus if a cluster node is rebooted, playback issues can arise.

To prevent issues for an existing cluster, you must configure the two Gluster cache volumes

to use the same UID and GID as the maxmin user, as described in the following procedure.

Note: This procedure should be done after the upgrade. It is only necessary for cluster

deployments using Gluster.

To set Gluster volume ownership so it does not change:

On each node in the cluster perform the following steps (slave first, master second, load

balancing at any time):

1. Stop Pacemaker:

service pacemaker stop

2. Stop Corosync:

service corosync stop

3. Obtain the user ID of the user maxmin (this might be different on each machine):

id -u maxmin

4. Change the user ownership of the gluster volume to maxmin using the user ID:

gluster volume set gl-cache-dl storage.owner-uid <uid>

gluster volume set gl-cache-fl storage.owner-uid <uid>

In the above commands, do not type the angle brackets. Enter the number obtained in

the previous step.

Note: Do not alter the gl-cache-mcam (multicam) volume. It uses the default root ownership.

5. Obtain the group ID of the user maxmin (this might be different on each machine):

id -g maxmin

6. Change the group ownership of the gluster volume to maxmin using the group ID:

gluster volume set gl-cache-dl storage.owner-gid <gid>

gluster volume set gl-cache-fl storage.owner-gid <gid>

Note: Do not alter the gl-cache-mcam (multicam) volume. It uses the default root ownership.

MediaCentral Services 2.2 Upgrading Guide

7. Verify the success of the ownership changes:

ls –la /cache/gluster

Should return:

drwxrwsrwx 3 maxmin maxmin 4096 Jan 12 09:51 gluster_data_download

drwxrwsrwx 5 maxmin maxmin 4096 Jan 12 09:51 gluster_data_fl_cache

drwxr-xr-x 3 root root 4096 Feb 5 08:33 gluster_data_multicam

8. Restart the GlusterFS service:

service glusterd restart

9. Verify the ownership changes are sticky:

ls –la /cache/gluster

Should return same as before:

drwxrwsrwx 3 maxmin maxmin 4096 Jan 12 09:51 gluster_data_download

drwxrwsrwx 5 maxmin maxmin 4096 Jan 12 09:51 gluster_data_fl_cache

drwxr-xr-x 3 root root 4096 Feb 5 08:33 gluster_data_multicam

10. Change ownership of any files residing in gluster_data_download and

gluster_data_fl_cache:

chown –R maxmin:maxmin /cache/gluster/gluster_data_download

chown –R maxmin:maxmin /cache/gluster/gluster_data_fl_cache

This is only absolutely necessary on systems that have already been running, where the

Gluster daemon reset ownership to root.

11. Start Corosync:

service corosync start

12. Start Pacemaker:

service pacemaker start

Upgrading Paths

This section presents the upgrade paths for specific deployment options.

Upgrading from 1.2.x or 1.3.x to MCS 2.2

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

representative.

Upgrading to MCS 2.2 for Interplay Central

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

colocation on Linux servers — in many respects MediaCentral Platform Services and

MediaCentral Services 2.2 Upgrading Guide

MediaCentral are the same thing. MediaCentral uses all MediaCentral Platform Services,

and its version number increases in lock step with MediaCentral Platform Services.

For upgrading instructions:

• “Upgrading a Single Server RHEL 6.5 System to MCS 2.2” on page 10

• “Upgrading a Cluster RHEL 6.5 System to MCS 2.2” on page 12.

• “Upgrading a Single Server RHEL 6.3 System to MCS 2.2”on page 16.

• “Upgrading a Cluster RHEL 6.3 System to MCS 2.2” on page 21.

Upgrading to MCS 2.2 for Media Composer | Cloud

The latest version of the Media Composer | Cloud plugin requires at least ICS 1.3. Upgrading

to MCS 2.2 for Media Composer | Cloud does not add any new functionality, but you do get

the benefit of the latest bug fixes.

For upgrading instructions:

• “Upgrading a Single Server RHEL 6.5 System to MCS 2.2” on page 10

• “Upgrading a Cluster RHEL 6.5 System to MCS 2.2” on page 12.

• “Upgrading a Single Server RHEL 6.3 System to MCS 2.2”on page 16.

• “Upgrading a Cluster RHEL 6.3 System to MCS 2.2” on page 21.

Upgrading to MCS 2.2 for Interplay | MAM

For Interplay MAM compatibility with MCS please refer to the MediaCentral Platform 2.2

ReadMe.

For upgrading instructions:

• “Upgrading a Single Server RHEL 6.5 System to MCS 2.2” on page 10

• “Upgrading a Cluster RHEL 6.5 System to MCS 2.2” on page 12.

• “Upgrading a Single Server RHEL 6.3 System to MCS 2.2”on page 16.

• “Upgrading a Cluster RHEL 6.3 System to MCS 2.2” on page 21.

Special Note: Upgrading from MCS 2.0

If you are upgrading from MCS 2.0, note the following. As part of some cluster deployments,

the MediaCentral Platform Services 2.0 Installation and Configuration Guide provided

instructions for replicating the cluster file caches using Gluster, an open source software

solution. The instructions include creating a metadata cache directory for Interplay | MAM

deployments with MPEG-1 browse proxies.

The use of Gluster to replicate metadata has been deprecated due to its negative impact on

performance. Please delete the GlusterFS metadata volume from all your server nodes in all

affected deployments. Once complete, metadata information is loaded into RAM and is no

longer replicated across other nodes.

MediaCentral Services 2.2 Upgrading Guide

For instructions, consult the Avid KB article “Removing the GlusterFS Metadata Cache

Replication Volume” at the following link:

http://avid.force.com/pkb/articles/en_US/how_to/Removing-the-gluster-metadata-cache-

replication-volume

Upgrading a Single Server RHEL 6.5 System to MCS 2.2

For systems already running RHEL 6.5, the upgrade to MCS 2. 1 is an update installation

involving the following procedure:

¨ Installing MCS 2.2 Using the Update Installation

Expected downtime: 30 min.

Installing MCS 2.2 Using the Update Installation

To install MCS 2.2 using the update installation:

1. Prepare and insert the MCS 2.2 installation USB key.

In the MCS 2.2 Installation and Configuration Guide, see “Preparing the MCS Installation

USB Key”.

Note: If the RHEL image cannot be put not on the USB key — that is, if it is not local to the

installation package — mount the RHEL as a loop device image to/sysinstall before

proceeding:

mount -o loop <Path_to_Image>/<RHEL_Image>.iso /sysinstall/

2. Mount the USB key and change to the USB mount point.

In this document, see “Appendix C: Mounting and Unmounting the USB Key

” on page

34.

3. Log in as root and dump the current database:

avid-db dumpall

Although the upgrade is non-destructive, it is a good idea to backup the MCS database.

4. Unzip the installation package.

unzip MediaCentral_Services_2.2_Build_XX_Linux.zip

5. Start the installation script.

./install.sh

Note: Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the installation

script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

MediaCentral Services 2.2 Upgrading Guide

For security, Linux does not include the “current” directory (“.”) in its PATH variable. You

must specify the path, even when you are in the directory where the script or command is

located.

During the installation process, progress is displayed (details have been omitted, for

clarity):

Cleaning repos:

Cleaning up Everything

Those familiar with the Linux yum update process will recognize the pattern of the

update.

The update completes with an indication of success:

INSTALLATION FINISHED

6. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.2.x.x

ICPS Version: 2.2.x.x

ICPS manager Version: 2.2.x.x

ACS Version: 2.2.x.x

System ID: "xxxxxxxxxxx"

ICS installer: 2.2 (Build xx)

Created on <installer creation date>

Note: The System ID is an 11-digit number used in support calls. You enter it via the

MediaCentral UX user interface. See the MCS 2.2 Installation and Configuration Guide.

Note: For precise version numbers for this release, see the MediaCentral Platform 2.2

ReadMe.

7. Unmount the USB key.

In this document, see “Appendix C: Mounting and Unmounting the USB Key

” on page

34.

Upgrading a Cluster RHEL 6.5 System to MCS 2.2

Installing MCS 2.2 on a cluster already running MCS compatible with RHEL 6.5 is a simple

automated update of the affected packages. All MCS system settings are preserved. There is

no need to manually backup and/or restore any MCS system settings. All nodes must be

brought off-line to perform the update.

The cluster update involves the following steps:

¨ Identifying the Master, Slave and Load-Balancing Nodes

¨ Bringing the Cluster Off-line

MediaCentral Services 2.2 Upgrading Guide

¨ Updating the Cluster

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

Identifying the Master, Slave and Load-Balancing Nodes

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]

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

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

Bringing the Cluster Off-line

To bring the cluster off-line:

Note:

The master node should not be in standby when you back up the database.

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

avid-db dumpall

MediaCentral Services 2.2 Upgrading Guide

Although the update is non-destructive, it is a good idea to backup the MCS database.

2. Begin bringing 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>

Updating the Cluster

You can upgrade the nodes in any order you like. However, be sure to bring them back

online in the correct order, as indicated in the instructions.

To update the cluster:

1. Prepare and insert the MCS 2.2 installation USB key.

In the MCS 2.2 Installation and Configuration Guide, see “Preparing the MCS Installation

USB Key”.

Note: If the RHEL image is not on the USB key — that is, if it is not local to the installation

package — mount the RHEL image as a loop device to/sysinstall before proceeding:

mount -o loop <Path_to_Image>/<RHEL_Image>.iso /sysinstall/

2. Mount the USB key and change to the mount point.

In this document, see “Appendix C: Mounting and Unmounting the USB Key

” on page

34.

3. Unzip the installation package.

unzip MediaCentral_Services_2.2_Build_XX_Linux.zip

4. Start the installation script.

./install.sh

Note: Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the installation

script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

For security, Linux does not include the “current” directory (“.”) in its PATH variable. You

must specify the path, even when you are in the directory where the script or command is

located.

During the installation process, progress is displayed (details have been omitted, for

clarity):

Cleaning repos:

MediaCentral Services 2.2 Upgrading Guide

Cleaning up Everything

Those familiar with the Linux yum update process will recognize the pattern of the

update.

The update completes with an indication of success:

INSTALLATION FINISHED

5. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.2.x.x

ICPS Version: 2.2.x.x

ICPS manager Version: 2.2.x.x

ACS Version: 2.2.x.x

System ID: "xxxxxxxxxxx"

ICS installer: 2.2 (Build xx)

Created on <installer creation date>

Note: The System ID is an 11-digit number used in support calls. You enter it via the

MediaCentral UX user interface. See the MCS 2.2 Installation and Configuration Guide.

Note: For precise version numbers for this release, see the MediaCentral Platform 2.2

ReadMe.

6. Unmount the USB key, proceed to the next node, and follow the same pattern:

a. Mount the USB key (and the RHEL image, if it is not on the USB key)

b. Run the update script

c. Unmount the USB key

7. When all the nodes have been updated, you must restart the RabbitMQ server on each

node.

service rabbitmq-server restart

The system should respond with the following output:

Stopping rabbitmq-server: [FAILED]

Starting rabbitmq-server: [ OK ]

8. Once you have restarted the RabbitMQ server on each updated node in the cluster,

reactivate the cluster by running the following command on the master node:

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

Note: If after running the reactivate-cluster script you observe that a node is the state of

“Offline - Unclean Node”, restart Pacemaker on that node.

9. If the reactivate-cluster command does not bring all nodes back online, you can do it

manually. For example, to bring the master node back online:

MediaCentral Services 2.2 Upgrading Guide

crm node online <node name>

Bringing the master node back online starts the Avid Interplay Central service (which

was stopped when you put the node into standby).

Similarly, you can bring the slave node back online:

crm node online <node name>

If applicable, bring the load-balancing nodes back online:

crm node online <node name>

10. Verify the cluster status and cluster failover status

crm_mon -f

• Verify the master, slave, and load-balancing nodes have rejoined the cluster, as

expected.

• Verify the fail counts for the following resources (at a minimum): AvidIPC, AvidUMS,

AvidACS, pgsqlDB.

• Verify the cluster status.

11. If there are fail counts listed, run the cluster resource manager cleanup command to

reset them:

crm resource cleanup <rsc> [<node>]

<rsc> is the resource name of interest: AvidIPC, AvidUMS, AvidACS, pgsqlDB (or another)

<node> (optional) is the node of interest.

Note: If you receive an “object/attribute does not exist” error message, it indicates the

resource is active on more than one node. Repeat the command using the group name for

the resource (the “everywhere” form). For example, for the AvidAll resource, use

AvidAllEverywhere. For AvidConnectivityMon, use AvidConnectivityMonEverywhere.

Note: You can address the services contained in the postgres resource group (postgres_fs,

AvidClusterIP and pgsqlDB) individually, or as a group.

For example, to reset the fail count for AvidALL resource, issue the following command:

crm resource cleanup AvidAllEverywhere

Upgrading a Single Server RHEL 6.3 System to MCS 2.2

The upgrade to MCS 2.2 is a fresh OS and MCS software installation involving the following

procedures:

¨ Backing Up System Settings and Installing RHEL 6.5 & MCS 2.2

¨ Restoring System Settings and Migrating User Settings

¨ Verifying and Configuring Date and Time Synchronization Settings

¨ Logging in and Backing Up the New System Settings

MediaCentral Services 2.2 Upgrading Guide

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 29

Expected downtime: 30 min.

Backing Up System Settings and Installing RHEL 6.5 & MCS

2.2

To back up system settings and install MCS 2.2:

1. Prepare and insert the MCS 2.2 installation USB key.

In the MCS 2.2 Installation and Configuration Guide, see “Preparing the MCS Installation

USB Key”.

2. Mount the USB key and change to the mount point.

In this document, see “Appendix C: Mounting and Unmounting the USB Key” on page

34.

3. Back up the current system settings and ICS/MCS database using the backup script.

In this document, see “

Appendix E: Backing Up and Restoring System Settings and the

ICS/MCS Database” on page 38.

4. Unmount and remove the USB key.

In this document, see “Appendix C: Mounting and Unmounting the USB Key” on page

34.

5. Boot into the HP BIOS, enter the “Option ROM Configuration for Arrays” utility and

destroy the RAID 5.

In this document, see “Appendix D: Deleting the RAID 5” on page 35

6. While still in the utility, re-create the RAID 5.

In the MCS 2.2 Installation and Configuration Guide, see “Setting Up the RAID Level 5

Cache Drives”.

Destroying and re-creating the RAID 5 eliminates (in advance) problems with cache

permissions that can arise as a result of the RHEL update.

7. Insert the USB key and boot from it to install RHEL and MCS.

8. Once installed, remove the USB key and reboot as prompted.

Rebooting after the OS upgrade causes the RHEL Text Mode Setup Utility (“Choose a

Tool”) screen to appear, providing access to set-up menus.

9. Quit the RHEL Text Mode Setup Utility and log in to RHEL.

10. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.2.x.x

ICPS Version: 2.2.x.x

ICPS manager Version: 2.2.x.x

MediaCentral Services 2.2 Upgrading Guide

ACS Version: 2.2.x.x

System ID: "xxxxxxxxxxx"

ICS installer: 2.2 (Build xx)

Created on <installer creation date>

Note: The System ID is an 11-digit number used in support calls. You enter it via the

MediaCentral UX user interface. See the MCS 2.2 Installation and Configuration Guide.

Note: For precise version numbers for this release, see the MediaCentral Platform 2.2

ReadMe.

11. Install the RHEL security update.

In this document, see “Security Updates” on page 5

Restoring System Settings and Migrating User Settings

To restore system settings and migrate user settings:

1. Re-insert and re-mount the USB key.

In this document, see “Appendix C: Mounting and Unmounting the USB Key

” on page

34.

2. Restore the system settings and MCS database using the restore script.

In this document, see “

Appendix E: Backing Up and Restoring System Settings and the

ICS/MCS Database” on page 38.

Note: It is possible that error messages similar to the following will be output to the shell:

/usr/maxt/maxedit/cluster/resources/_common.sh errors

Ignore the messages and type the following and press Enter to complete the command:

service avid-all stop

You do not need to stop the error messages to type the above command. You can type it

even as the error messages are output to the terminal.

3. Unmount and remove the USB key.

In this document, see “Appendix C: Mounting and Unmounting the USB Key” on page

34.

4. Open the restored filesystem table (/root/fstab) to examine it for reference purposes.

• The restored filesystem table (/root/fstab).

• The current filesystem table (/etc/fstab).

Note:

The filesystem table cannot be automatically restored to the original location, since

some entries are assigned UUIDs dynamically by Linux. These can change from one RHEL

MediaCentral Services 2.2 Upgrading Guide

installation to the next, even if they underlying hardware remains the same. Nevertheless, it

is convenient to examine the restored filesystem table, for reference.

For example, in an MCS system with a RAID 5 cache volume, the restored filesystem

table contains an entry similar to the following:

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

Note: For Interplay | MAM system the filesystem table contains an entry to

automatically mount the Interplay | MAM filesystem.

5. Reboot and note the restored host name at the login prompt (e.g. ics-dl360-1).

6. Log in as root and migrate the user settings from the UMS database to the USS database

(new in 2.0):

/opt/avid/bin/avid-uss-import –p Avid123

The above command needs to be invoked once only. In the case of a cluster, it is

invoked on the master node only.

The system returns the following:

Loading properties..

Fetching zone UUID..

Importing settings for zone UUID: 00000000-0000-0000-0000-

000000000000

Importing setting_domain_class..

Importing setting_class..

Importing setting_instance..

SUCCESS

Verifying and Configuring Date and Time Synchronization

Settings

To verify and configure the date and time synchronization settings:

1. Log in and check the date and time are correct, and adjust if needed:

date

In the MCS 2.2 Installation and Configuration Guide, see “Verifying the Date and Time”.

2. Though time zone information was restored, you must re-create the symbolic link RHEL

needs to make use of it:

ln –sf /usr/share/zoneinfo/<yourzone> /etc/localtime

If you need to verify the zone in use prior to re-creating the symbolic link:

cat /etc/sysconfig/clock

For more information, in the MCS 2.2 Installation and Configuration Guide, see “Setting

the Time Zone”.

3. Verify the availability of the in-house NTP server, synchronize the System Clock, and set

up a cron job to keep the clock synchronized.

MediaCentral Services 2.2 Upgrading Guide

In the MCS 2.2 Installation and Configuration Guide, see “Synching the System Clock”.

Logging in and Backing Up the New System Settings

To perform final configurations and back up the new system settings and MCS database:

1. Log in to Media Central UX, accept the license agreement, and verify user migration and

role assignments.

2. If you are deploying ICS for Interplay | MAM or Media Composer | Cloud, you must

update Interplay Central configuration settings.

In this document, see “

Reconfiguring ICS for Interplay | MAM or Media Composer |

Cloud in an Upgrade from ICS 1.7 or Earlier” on page 28.

3. Finally, back up the system settings and MCS database.

In this document, see “Appendix E: Backing Up and Restoring System Settings and the

ICS/MCS Database” on page 38.

Page is loading ...

Avid MediaCentral 2.2 User guide

Brand: Avid

Model: MediaCentral 2.2

Category: Software

Type: User guide

Download PDF

report

Avid MediaCentral 2.2 User guide

Avid MediaCentral 2.2 User guide

Related papers

Other documents