Pinnacle Systems MediaCentral Platform Services - 2.9 User Manual
MediaCentral Platform Services v2.9
Hardware Guide
Important Information
For the latest information on MediaCentral Platform Services, see the documentation available from
the MediaCentral Documentation page of the Avid Knowledge Base. Updates are occasionally issued
after initial release.
This document is intended for people who either need to advise on or directly make purchase
decisions for hardware on which MediaCentral Platform Services (MCS) will be installed and
configured. A basic understanding of server components (CPU, RAM, etc.) is required.
This document provides HP and Dell part numbers as a reference. Prices are not provided, and may
n
differ, depending on your geography and the customer’s relationship with HP or Dell. Part numbers
may change without notification. Consult the manufacturer directly for updated information.
Revision History
Date Revised Changes Made
May 25, 2017 Adding details related to Media Composer | Cloud Remote. For more information,
see “Determining Scale: MediaCentral for Media Composer | Cloud Remote” on
page 20.
March 14, 2017 Details related to Media Composer | Cloud users and stream-counts found in earlier
versions of this guide have been temporarily removed for clarity. The data was
determined to be inaccurate for current versions of MediaCentral Platform
Services. This document will be re-released when updated data is available.
January 11, 2017 Added details regarding the processor type used for the AVC-ULTRA and XAVC
testing.
December 22, 2016 First Publication
• Added AVC-ULTRA and XAVC resolutions to Stream Count tables.
For details, see “Media Format and Stream Count Assessment” on page 17.
Contents
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Operating System Requirements and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Caching and HDD Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Supported Network Adapters for Avid Shared Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Over-Specifying and Under-Specifying the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Deploying Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Determining Scale: MediaCentral UX for iNEWS Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Determining Scale: MediaCentral UX - Mixed Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Determining Scale: Interplay | MAM Deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Qualified Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Legal Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2
Overview
Before getting into the details of buying hardware, take a moment to understand what MCS is, and
why it is important to make the right hardware purchasing decisions.
After reading this document you should be able to:
• Clearly identify the solution for which you are buying MCS hardware
• Determine the general hardware platform you need to buy
• Choose the Red Hat Enterprise Linux (RHEL) support subscription option that best meets your
needs
• Determine the type of network interface card (NIC) required for your environment
• Determine whether or not you require additional hard drives for media caching
• Collect data that will allow you to determine how many MCS servers are required
What is MediaCentral Platform Services?
MediaCentral Platform Services (MCS) is a set of software services that provide a foundation for
applications such as MediaCentral | UX, Interplay | MAM, Media Composer | Cloud, and more.
Some of the primary services hosted on the platform are:
Overview
• Layouts for various applications and workflows
• Local or global MCS user management and authentication
• A graphical user interface (GUI) for system configuration and management
• Network-based video playback services for web and mobile clients
For more information, see the MediaCentral Platform Services Concepts and Clustering Guide at:
http://avid.force.com/pkb/articles/en_US/user_guide/Avid-MediaCentral-Documentation
Buying Hardware for MCS
For the most part, provisioning hardware is straightforward in that it is easy to configure a basic
supported server. However, varying workflows and optional video playback methods can add
complexity to the hardware provisioning process. Take the time to determine the number of servers
required, and the hardware options with which the servers may need to be equipped. Review the
following deployment options and associated supported server types:
• MCS supports MediaCentral UX and Media Composer | Cloud on HP and Dell hardware only.
• MCS supports Interplay | MAM on HP, Dell and other hardware.
• MCS supports deployments that do not require video playback on HP, Dell and other hardware.
An iNEWS-only deployment with connections to iNEWS, but no connection to Interplay |
Production, is a non-video deployment.
In all cases, it is recommended that you review your hardware assessment with a qualified Avid
representative before making a final purchase. Reviewing this document is an essential first step prior
to consultation that will accelerate the process.
3
Server Requirements at a Glance
Determining the number of required servers depends on a number of factors:
1. Deployment Type: The type of deployment is the primary influence on server requirements. An
iNEWS only deployment without video playback has the lowest processing needs. MediaCentral
UX and Interplay MAM deployments require more CPU resources, due to the media transcoding
requirements.
2. Media Formats: The next biggest consideration is the source media format. For example,
DNxHD is a resource-intensive media format while Avid JFIF is lightweight in comparison.
Thus for the same number of users, fewer servers are needed for a site where the source media is
Avid JFIF.
3. Frame-based vs File-based Playback:
- The default playback method for MediaCentral UX is frame-based. In this mode, media is
encoded as a series of JPEG files that are streamed directly from the server for playback.
This technique provides frame-accuracy and a smooth transition between cuts. Frame-based
playback is high quality, but requires a higher network bandwidth than file-based playback.
- The default playback method for Interplay | MAM is file-based. In this mode, media is
encoded as a series of FLV files that are downloaded to the client workstation for playback.
File-based playback provides good quality in low-bandwidth situations.
Overview
- Both MediaCentral UX and Interplay MAM allow the end-user to configure the session for
either playback method. Frame-based playback is more CPU-intensive in MAM
configurations that use an MP4 format with an H.264/AAC essence. In file-based playback
in Interplay Production configurations, assets are converted to FLV/MP3 files on the MCS
server. The first playback transcodes the file and initially consumes more resources than
frame-based playback.
4. Number of Users: The number of servers deployed must match peak usage requirements. For
example, if a single server can simultaneously transcode 15 streams of the proxy storage format
and if 25 concurrent user connections are expected, two servers will be needed to serve media to
all users.
The following table summarizes the basic cases for one, two and three or more servers. For more
information, see “Deploying Multiple Servers” on page 15.
Number of
Servers
1 Single Server The minimum deployment model, suitable for MediaCentral for iNEWS-
Deployment
Model Description
only (browse and edit iNEWS content with no media playback
requirement) or environments with few users and / or undemanding
transcoding requirements.
This solution offers some hardware redundancy (dual power supplies, dual
internal drives), but little redundancy for system services.
2 Master and Slave This is the minimum recommended deployment for most scenarios.
Adds automatic failover safety to the basic single-server deployment, plus
increased peak-usage and transcoding capacity.
This solution offers redundancy for both hardware and system services.
4
Overview
Number of
Servers
3 + Master, Slave and
Deployment
Model Description
Adds increased peak-usage and media transcoding capacity.
Load Balancing
Deploying multiple servers in a cluster is particularly important for sites
with many users and/or resource-hungry media formats.
For example, a single server can support the simultaneous playback of over
100 Avid JFIF media streams, but only 15 streams of AVC Intra 50 to
MediaCentral UX.
This solution offers redundancy for both hardware and system services.
Adding Servers to an Existing Installation
Over time, a site may wish to expand a single server to a cluster configuration or potentially add
nodes to an existing cluster. When purchasing, sites might not be able to obtain server hardware that
matches the specifications of the original hardware. Avid supports mixing server hardware for a
cluster configuration as long as the following criteria are met:
• Mixed processor speeds and RAM are supported between the servers. However, all servers
should meet the minimum RAM requirements outlined in this document.
• RAID1 (OS) and RAID5 (cache) drive sizes do not need to be identical between the old and new
servers. However, the DRBD volume size and the Gluster bricks need to be the same sizes. If the
new servers include larger drives, some space will be left unused. In other words, if the RAID5
cache volume is 2TB on the original hardware and is 3TB on the new hardware, 1TB will be left
unused.
• The network interface card does not need to be of the same type, but the name of the interface
must be the same. For example, the naming convention for the network adapters in an HP is
“ethx”, while Dell servers use “emx” and “pxp1”. When creating or expanding a cluster, special
care and additional steps are required to ensure that all NICs have the same interface name.
• While mixing 1 GB and 10 GB network adapters between the servers is possible, it is not
recommended. Avid has not specifically tested clusters containing a mix of 1 GB and 10 GB
adapters
• Mixed server generations are supported. For example, an HP Gen 8 server and an HP Gen 9
server are supported together in the same cluster.
Additional Resources
The following sections provide useful links for vendors discussed in this guide.
Red Hat Enterprise Linux (RHEL)
Red Hat Enterprise Linux main page:
https://www.redhat.com/en/technologies/linux-platforms/enterprise-linux
5
Operating System Requirements and Support
Hewlett-Packard (HP) and Dell
Consult the manufacturer’s web site for the most up-to-date for resources for researching and
configuring the servers supported for MediaCentral Platform Services.
• HP (Enterprise) website (US):
https://www.hpe.com/us/en/home.html
• Dell (Enterprise) website (US):
http://www.dell.com/us/business/p/enterprise-products
Operating System Requirements and Support
MediaCentral Platform Services requires Red Hat Enterprise Linux (RHEL), a commercially
supported open source operating system. Although it is open source, RHEL is not free. Avid does not
include or redistribute it as part of the MCS software set.
For information on the supported RHEL version, see the Interplay Production and MediaCentral
n
Compatibility Matrix on the Avid Knowledge Base.
In order to be legally compliant with the RHEL EULA, customers are required to procure a RHEL
support subscription, a commercial offering that recurs annually. RHEL support offers two key
components:
• Technical support for OS-related issues. The level of support depends on the support
subscription purchased by the customer.
• Indemnification. Because RHEL is an open source project, there is a risk that it will be
discovered to infringe on patents and the patent holders will take legal action. Red Hat protects
its customers by taking legal responsibility for the distribution.
It should be noted that OS-related issues for MCS are extremely rare.
There are two different ways to provision RHEL support:
• HP offers RHEL one and five year renewable support subscriptions.
• Red Hat offers different tiers of annual support subscriptions directly.
HP RHEL Support
HP RHEL support covers indemnification and provides technical support staffed by people who
specialize in Red Hat running on HP servers. This option is fairly expensive (compared to Red Hat
direct offerings) but gives the customer single point of contact for both OS and hardware related
issues. It also is an easier purchase process—the customer simply adds it to the HP server order.
Part Number Component Description
G3J28AAE Red Hat Enterprise
2 Sockets or 2 Guests 1 Year Subscription 24x7 Support E-LTU
Linux Server
G3J32AAE Red Hat Enterprise
Linux Server
2 Sockets or 2 Guests 5 Year Subscription 24x7 Support E-LTU
6
HP provides other RHEL support options (subscription periods, support for more server sockets and/
or virtual guests), but the two options listed above are the most appropriate selections for MCS
deployments. For more information, visit:
https://h41380.www4.hpe.com/red-hat-product-selector/
Direct RHEL Support
Price-sensitive customers may prefer to provision RHEL support subscriptions directly from Red
Hat. In this case, they order the server with no OS. In parallel they buy RHEL support from Red Hatin which case they have different support tiers to choose from.
The least expensive option is RHEL “Self-Support” which covers indemnification only. For technical
support issues, users have access to Red Hat online resources and community support. For more
information on Red Hat’s support offerings and pricing, visit:
https://www.redhat.com/wapps/store/catalog.html
Dell RHEL Support
For information on Dell RHEL support, visit:
Operating System Requirements and Support
http://www.dell.com/redhat
http://en.community.dell.com/techcenter/os-applications/w/wiki/red-hat
Optional Support
HP and Dell offer several other support options varying in coverage and duration. Customers should
purchase the support option they feel is appropriate for their operation.
7
Memory Requirements
The following table summarizes the MCS memory requirements:
RAM Description
64 GB Minimum RAM required for MCS v2.1 and earlier deployments
96 GB Minimum RAM required for all current deployments (MCS 2.2 and later)
128 GB Minimum RAM required for deployments with high-quality streaming and/or Media | Index
To optimize RAM configuration and slot usage, it is helpful to understand how the Intel Xeon
processor addresses memory. As shown in the following example, the 2650L V3 CPU features 4
memory channels with 3 DIMM slots per channel. When populating the motherboard with RAM,
ideally each channel receives at least one DIMM (not shown in illustration).
Memory Requirements
For optimal memory performance, select RAM in “kits” of matched DIMMS that correspond to the
available memory channels (e.g. x4, x8). For example, you could deploy two x4 kits, or one x8 kit. A
x4 kit would consist of 4 matched DIMMs. An x8 kit would consist of 8 matched DIMMs. Matched
DIMMs are tested and guaranteed to perform well when installed, one per channel, in each of a CPUs
memory channels. DIMM slots are usually color coded to indicate each memory channel.
Mixing DIMMs of different size and/or different kits is not recommended, and can result in
performance degradation that can be difficult to diagnose and remedy. Consult your hardware vendor
for assistance with RAM configurations.
8
96 GB Memory Configuration
When configuring the server with 96 GB RAM, the following illustration shows acceptable DIMM
placement:
Memory Requirements
In the above illustration, note that the first configuration (12 x 8 GB DIMMs) indicates best use of the
CPU’s capabilities, since it populates each memory channel. Although the second configuration
achieves the desired amount of RAM (96 GB), it is a suboptimal configuration as two memory
channels remain unused.
128 GB Memory Configuration
When configuring the server with 128 GB RAM, the following illustration shows acceptable DIMM
placement:
In the above illustration, both deployment styles are acceptable, since each channel receives at least
one DIMM.
9
Adding Memory to Accommodate Higher-Quality Playback
In MediaCentral 2.0 a feature was introduced where you can add users to a group with the ability to
set a maximum JPEG stream image size of up to 960px wide (as opposed to the default maximum
width of 480px). If this option is used, MediaCentral servers must be provided with additional RAM,
as indicated in the following table:
RAM Description
96 GB Minimum RAM required for all deployments
128 GB Minimum RAM required for deployments with high-quality streaming and/or Media | Index
Intel Xeon 2650L V3 CPU
If the system has already been provisioned with 12x8GB DIMMs, purchase an additional 4x8GB of
identical RAM, as illustrated in the following table:
Qty Part Number Component Description
4 (HP) 726718-B21 Memory HP 8 GB (1x8GB) Single Rank x4 DDR4-2133 CAS-15-15-
15 Registered Memory Kit
Memory Requirements
4 (Dell) 8G2R Memory Dell 8 GB RDIMM, 2133MT/s, Dual Rank, x8 Data Width
Alternatively, if you already provisioned the system with the minimum RAM requirements (12x8 GB
= 96 GB DIMMs), all 8 GB DIMMs can be replaced with 16 GB DIMMs (8x16 GB = 128 GB
DIMMs):
Qty Part Number Component Description
8 (HP) 726719-B21 Memory HP 16 GB (1x16GB) Dual Rank x4 DDR4-2133 CAS-15-15-
15 Registered Memory Kit
8 (Dell) 16G2R Memory Dell 8x16 GB RDIMM, 2133MT/s, Dual Rank, x4 Data
Width
For DIMM placement information, see “128 GB Memory Configuration” on page 9.
n
10
Caching and HDD Requirements
In several workflows, MCS generates and locally caches transcoded media assets. These workflows
include:
• Multi-cam logging in MediaCentral | UX
• Media playback for iOS and Android mobile apps
• Interplay | MAM browse proxy file-based playback for formats that cannot be natively loaded in
the Flash player (MPEG-1, Sony XDCAM, WMV, Harmonic MXF).
These workflows all share the same requirement: asset playback from a web or mobile application is
requested of a source media asset that is not web or mobile compliant. In this case MCS must locally
generate a web or mobile compliant copy of the source media asset. This asset is then served to the
requesting web or mobile application. The asset is also cached in anticipation of a subsequent
playback request. In the case of multi-server deployments (cluster), the cached assets are replicated
across the servers to reduce future transcoding of the same asset on a different playback server.
As a result, additional drives are required on MCS servers for this cache. The following table
summarizes caching requirements:
Deployment Comments
Caching and HDD Requirements
MediaCentral UX for Interplay
Production
MediaCentral UX for
iNEWS-only
MCS for Interplay | MAM • The cache is populated with FLV files when a file-based playback
For hard drive specifications and the number of drives required, see Media Cache Drive Configuration below.
Required for:
• Multicam media - The cache is populated with JPEG images when
multi-cam logging is performed.
• Media Composer Cloud workflows using multicam media.
• Mobile Apps - The cache stores MPEG-2 Transport Stream media
files.
• File-based playback
Media is not created on the cache while in frame-based playback mode.
n
The cache volume is not used with iNEWS-only workflows.
request is made of any non-MP4 (H.264/aac) format proxy.
• The Remote Playback workflow introduced with MCS v2.5 caches
JPEGs and audio media for frame-based playback.
• The cache is not used when playing back MP4 (H.264/aac) browse
proxies.
11
Media Cache Drive Configuration
When a media cache is required, the following options are supported:
Drives Volume Configuration and Notes
1 A single hard drive configured as a separate volume.
This configuration provides no redundancy in case of hard drive failure.
2 2 drives configured as a RAID1 volume.
This configuration provides redundancy in case one of the hard drives fails.
6 or 8 Drives configured as a RAID5 volume.
This configuration provides redundancy in the event of hard drive failure. It also provides
increase I/O for a higher volume of proxy generation and serving.
Important: In all cases, the media cache is distinct from, and in addition to, the 2 HDD RAID1 volume
configured for the operating system.
The cache drives can be sourced directly from HP/Dell as part of your server requisition. The
following (or equivalent) drives are recommended:
Caching and HDD Requirements
Part Number /
Supplier
HP 652572-B21 HP 450 GB 6G SAS 10K SFF (2.5-inch) SC Enterprise 3 yr Warranty HDD
Dell 600S10 600 GB 10K RPM SAS 6 Gbps 2.5in Hot-plug Hard Drive
Product Code Description
12
Loading...