OnPrem Standard Package – Discovery
Customer Facing
Revision
1.0
Date
30-Jul-12
Author
Yair Leshem
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 1 of 10
Change
Initial
1.
Document Objective ............................................................................................................................. 3
2.
Standard Package Deployments ........................................................................................................... 3
3.
Standard Package Core Components.................................................................................................... 3
4.
Multi-Server (VMs) Diagram Example .................................................................................................. 6
5.
HW Recommendations ......................................................................................................................... 7
6.
CDN Integration .................................................................................................................................... 8
7.
Virtual Machine’s Building Blocks ......................................................................................................... 8
8.
Installation Requirements ..................................................................................................................... 9
9.
Additional Features ............................................................................................................................... 9
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 2 of 10
1. Document Objective
This document objective is to present to the customer with the basic essintial information about
Kaltura’s OnPrem standard solution as a basis for scoping, sizing and deployment phase.
2. Standard Package Deployments
Kaltura’s OnPrem Standard Package is a solution enables the customer to operate a fullyfeatured Kaltura OVP on his premises and in his close environment.
The standard package is a Virtual Appliance, running on ESX server. It is a prepackaged appliance
with all software requirements and has been verified to work by an extensive QA cycles.
Any configuration (features, building blocks, special deployments or integrations) that doesn’t
match the below will be considered as ‘custom package’ and will have to be scoped by Kaltura.
The standard package can be deployed in customer’s environment in 2 variations:
1. Single Server
One VM that combines all modules in one server and all share its resources (RAM, CPU, HDD).
2. Multiple Server
Deployed as numerous VMs connected together and each VM operates and a different module
in the cluster.
The multiple server deployment enables to replicate a certain kind of module (for example the
transcoding module or the web services module) for better handling multiple users and optimize
the VM’s resources.
3. Standard Package Core Components
The following components must operate within Kaltura’s online video platform:
1. Kaltura Web Services Module
Apache server and Kaltura web services layer in the form of a set of Application Programming
Interfaces (API) as a single access point for client-server applicative communication. This module
should be deployed on front-end server/s (traffic distributed by load balancing equipment).
2. Kaltura Batch Jobs Module
Scalable middleware entities deployed on back-end server/s. Central orchestration of atomic
batch services such as media import, media info extraction, transcoding, server notification and
others. This module should be deployed on a backend server.
3. Kaltura Transcoding Module
This module manages all media transcoding tasks, by utilizing open source and/or commercial
transcoders. This is a CPU intensive module and could either be deployed on a backend server at
a local deployment or can be distributed using independent transcoding servers deployed in a
cloud solution.
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 3 of 10
4. Shared Storage
A dedicated disk space that is shared and accessible by all of Kaltura’s servers within a specific
deployment. The Shared storage holds all content and application files, including: media assets,
Kaltura flash widgets/applications, skins, thumbnails, players/playlist configuration files (UI conf)
etc. The shard storage can be deployed as part of a local deployment or using independent
storage within a cloud solution.
5. Operational Database
This is the applicative database, used for storing and managing content related data (metadata,
identifiers, URLs etc.) as well as application and business logic supporting data. The operational
database should be deployed as part of a local deployment, preferably on dedicated server/s
utilizing a master/slave topology.
6. Search server
Full text search server based on the Sphinx open source solution for fast indexing and search.
7. Site Admin Module
This module is responsible for operating Kaltura’s Admin Console, enabling site administrators
to monitor and operate their own deployment of Kaltura’s online video platform. For full
monitoring, it is important to deploy this module on a local separate server.
8. Video Analytics Module
This module is responsible for processing and aggregating Kaltura’s video analytics data into a
dedicated Data Warehouse (DWH), and the production of video usage and behavior reports. The
module includes the data Exporting, Transforming and Loading processes (ETL), a DWH
database, and the reporting utilities in use. This module can be deployed as part of a local
deployment or can be distributed using independent analytics servers deployed in a cloud
solution.
9. MediaSpace (optional)
Kaltura MediaSpace is a fully customizable media destination site for the organization.
MediaSpace is an out-of-the-box video-centric site that can serve as a repository for media
collections across the organization or a full-featured "internal YouTube. It can be integrated into
the local authentication environment for role-based authentication, or use it as a public
destination site. It can be easily configured and branded, and requires minimal resources to get
up and running while allowing extensive customization.
10. Document Conversion Module (optional)
The Document conversion module converts various document formats into a flash based swf
document, later to be used within the Kaltura dynamic player as a synchronized slideshow
alongside a video. The supported document formats include the following: MS Office
documents (e.g. Word, PowerPoint), Open Office documents, and Adobe PDF. The document
conversion process can be distributed using independent document conversion servers
deployed in a cloud solution. Each server must run Open Office and MS Office in order to
perform the document conversion.
11. Video Recording Module (optional)
This module is responsible for recording web camera streams; it is an optional component to be
deployed only when there is a need to support video recording functionalities. Kaltura operates
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 4 of 10
this module using the Red5 solution. Using a local FMS of another provider is possible as well
but may require validation.
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 5 of 10
4. Multi-Server (VMs) Diagram Example
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 6 of 10
5. HW Recommendations
1. Single Server
A single server can usually handle 1000 active user sessions and approximately 220 minutes of
daily video uploads.
Minimum HW requirements is 1GB RAM, 2 quad core CPU and Storage per need, according to
expected usage estimations
2. Multi-Servers
Kaltura’s recommendation and best practice is to have full redundancy of the VMs for failover.
2 servers running a VMWare ESXi Hypervisor. Each server will host several modules as VMs.
1 Platform Shared Storage - To be accessible by the Kaltura platform servers via NFS (RAID 5 or
10 is recommended).
It is recommended to select hardware based on VMWare’s Hardware Compatibility List:
http://www.vmware.com/resources/compatibility/search.php?deviceCategory=server
The below is minimum quantity and specifications, suitable for 75K users.
Server
Front-End API
Servers
Min Qty
2
Comments
In high load cases, we may recommend a
SQUID proxy in front of the Apaches. In this
case Back-End Batch servers might also be
needed.
2 for redundancy
Back-End
Batch Server
2
Back-End
Transcoding
Servers
2
DB Server
2
Admin
Console and
DHW Server
search
servers
1
not exposed to the world directly - for
security reasons
2
2 for redundancy
MediaSpace
2
Media Server
2
Optional - if MediaSpace is required
Estimation - a typical server with 3GB RAM
can support 100 concurrent requests ~1,000
concurrent users
Optional - if Webcam recording feature is
Creating a video entry with multiple flavors
can take up to 20 times the length of the
source file.
2 for redundancy
Add more CPUs to be able to handle peak
uploads
One master and one slave
One pair will suffice for ~75k users
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 7 of 10
Minimal HW requirements
8GB RAM
1 quad core CPU
100GB of local HDD
8GB RAM
1 quad core CPU
100GB of local HDD
8GB RAM
2 quad core CPU
100GB of local HDD
8GB RAM
1 quad core CPU
100GB of local HDD
No minimal specifications
on hardware
8GB RAM
1 quad core CPU
100GB of local HDD
3GB RAM
The app is not CPU
intensive
No special storage req
Windows
server
2
required
Optional - if Video-PPT feature is required
Windows server 2008
Hyper-V licensing
2GB RAM
1 quad core CPU
100GB of local HDD
With growth in service utilization this initial setup can be scaled up as needed, to add the
required server type (e.g. additional transcoding servers, additional database servers for
replications, additional front end server etc.).
6. CDN Integration
The standard package includes integration with one of the following CDNs:
1. Akamai - www.akamai.com
2. Limelight - www.limelight.com
3. Level3 - www.level3.com
4. Edgecast – www.edgecast.com
5. Mirror Image - www.mirror-image.com
7. Virtual Machine’s Building Blocks
1
2
Building Block
Operating system
Web server
Details
CentOS 6.3
Apache 2.2.x
3
PHP
PHP 5.3.3
4
5
6
7
8
9
Data Base
Java
BI Suite
Transcoding engine
Search server
Storage
10
Mail server
11
12
Media server
Video-Presentation
widget
MySQL 5.1.52
JRE 1.6.x
Pentaho 4.2.1
ffmpeg 0.10
Sphinx 2.0.4
NFS - should be
provided by
customer
Sendmail /
postfix
Red5
Kaltura’s
pdf2swf and
presentation
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 8 of 10
comments
with the following modules enabled - rewrite, headers,
expires, filter, deflate, file_cache, env, proxy
Both php and php-cli must be present.
The following extensions are also required: Gd, Curl,
Memcache, Mysql, Mysqli, Exif, ftp, iconv, json, Session,
apc (recommended), spl, DOM, SimpleXML, xml, xsl,
imap, ctype, ssh2 - optional (required for enabling the
remote storage functionality)
Also include the Pentaho data integration package.
Required for managing outgoing emails as part of the
Kaltura platform workflow
Optional, if Webcam recording feature is required
Optional, if Video-PPT feature is required
Windows & Office server should be provided by
customer:
- Microsoft 2008 server
- PDFCreator
- Office 2007
- OpenOffice
Installed SW:
 .NET 3.5.1
 Desktop Experience
 XAMPP 1.7.1 on port 8080
 OpenOffice 3.2.1
 MS Office Professional 2007
 PDF Creator 1.0.2 ( standard installation)
 make PDFCreator the default printer
 Place RunAffinityCmd.exe in C:\
 Mediainfo 0.7.29 - optional
Note: Kaltura cannot run when the Security-Enhanced Linux (SELinux) feature is deployed and
enabled. If the SELinux feature is deployed on the servers, it must be disabled or set it to
permissive for being able to use Kaltura.
widget
8. Installation Requirements
Remote access through one of the following:
 SSH
 Cisco VPN
 PPTP (point to point tunneling protocol)
Remote access to different geographical locations for install and testing (USA and Israel)
Root Access to the entire environment during the installation phase
VPN login (if needed)
Every tool or process that will run over the environment, and it's not part of Kaltura product, will
be under the customer responsibility, and Kaltura shall not be responsible, for investigating or
fixing issues, that will cause by the operation of this tool.
9. Additional Features
Not as part of the OnPrem Standard Package but as Professional Services offering, Kaltura’s
extensions and features are available to be added after OnPrem was set-up. For example:
1. Single Sign On (SSO) - Integration with an external authentication server to enable external
user management and access to already logged in users.
2. Active Directory integration as LDAP, Shibboleth.
3. Secured Login - Creation of an HTTPS certificate by the customer and integration effort
a. KDP supports HTTPS, but requires to be set on the on the partner’s CDN
configuration. The same is true for other widgets (e.g. KCW)
b. Blackboard Building Block supports HTTPS from version 2 and on.
c. KMC – Only login page supports SSL
d. Admin Console – supports.
4. LMS integration as Blackboard, Moodle, Sakai.
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 9 of 10
5. Antivirus – Entries scanning by Symantec (licensed SW) or with Clam AV (Open source).
6. Others
Confidential
Copyright © 2012 Kaltura. All Rights Reserved.
Page 10 of 10