This guide is applicable for Kaltura CE version 3.0.x based Amazon Machine Images (AMIs)
The Kaltura Community Edition is a free, open-source, self-hosted video platform. It is developed through the combined efforts of Kaltura and the community and is available under the GNU Affero General Public License v3
This installation guide helps you understand how to work with Kaltura's Amazon EC2 images so you can get up and running using Kaltura's Community Edition.
Getting Your Amazon Credentials
Kaltura offers pre-configured Amazon Machine Images (AMIs) of our Community Edition that can get you up and running in short order. If you don't already have an Amazon Web Services account, you will need to signup for a free developer account at Amazon.
After configuring your EC2 credentials, you can use the AWS Management Console, or your favorite tool, to create instances using our AMIs.
If you'd like to learn more about Amazon EC2 and how to use it, refer to the Amazon EC2 Getting Started Guide.
Our Amazon Machine Images
Kaltura currently offers two Amazon AMIs in the US East availability
zone. They have 15 gigabyte EBS (Elastic Block Storage) backed root partitions.
-
ami-a80ef9c1ami-d8ad53b1 - This is Kaltura CE 3.0 running on 32-bit Ubuntu 10.4 LTS -
ami-ae0ef9c7ami-9cad53f5 - This is Kaltura CE 3.0 running on 64-bit Ubuntu 10.4 LTS
[Note: May 12th, 2011 update to AMIs to fix ssh key security issue
If you are running one of the old instances, you can fix them easily:
Edit these two text files with your favorite text editor:
/home/ubuntu/.ssh/authorized_keys
/root/.ssh/authorized_keys
Those files list public keys that have access to your running instance.
Remove any public keys that don't belong to you. Save the files.
Note that if you corrupt this file you will no longer have access to your image and you will have to terminate it.]
These images are pre-configured versions of the official Ubuntu 10.4 LTS images with Kaltura CE. The CE source code is on the server, but it is not installed. However, the installation process has been streamlined to make it very simple.
Support
The Kaltura Community Edition is free software that is supported by the community. Please go to our forums for questions and feel free to post bug reports to our bug tracker.
Preinstallation Considerations
Configuring mail service for your instance
Amazon does not provide a mail server for your instance. The Kaltura CE depends on mail service to create new Publisher accounts. So, you need to configure a mail service for your instance before you install the CE. The images are configured to use Postfix as the mail agent, but you can install anything you like.
If you choose to use Postfix, you have two basic choices:
- Sign up at Sendgrid.com. This is 100% free for up to 200 emails per day. New signups will usually get activated in less than four hours and then you simply add your username/password to the Postfix installation by editing the main.cf file (the main.cf is already configured for Sendgrid):
sudo vi /etc/postfix/main.cf
sudo service postfix restart - Use another service such as AuthSMTP or Postini. Also, if you have your own SMTP server and know how to configure Postfix, you can go that route as well. You can also install Sendmail or any other mail server you like.
Optional: Assign an Elastic IP address
Note: You only need to do this step if you intend on stopping and restarting your machine instance.
When you bring up an instance, Amazon automatically assigns a domain name and IP address to it. When you install the CE, we'll use that domain name and IP address. To ensure that your image has the same IP address even after you've stopped and restarted your instance, we recommend that you assign an Amazon Elastic IP address to the image. The IP address (and domain name) needs to stay the same or else the Kaltura software will get confused. Use the Amazon Management Console to assign the Elastic IP BEFORE installing the Kaltura software.
Note: when you stop a running instance, the Elastic IP address will be released by Amazon. You will need to re-attach it after you've re-started the instance.
Installation Steps
Once you've brought up an instance and logged in via SSH, you're ready to install the CE.
- You should first configure the mail system as outlined above.
- Change directory to /opt/kaltura_install
- Run the install script: sudo php install.php
Your Kaltura installation is now installed at /opt/kaltura
Adding an EBS Volume to Extend Storage Capacity
The Amazon AMIs have the operating system and Mysql database on a single 15 gigabyte partition. This is typically not enough storage for most users. To extend the storage capacity, we recommend that you mount an EBS volume and modify the CE to store media files on it.
First, create an EBS volume of up to one terabyte in the same zone as your EC2 image using your favorite EC2 tool, such as the Amazon Management Console. Still using your favorite EC2 tool, attach the EBS to a device on your Amazon EC2 image. In this example case, we'll use /dev/sdk.
Now follow these steps to have the CE use the mounted EBS volume:
- Create a filesystem (we'll use the ext3 type here) and mount it:
sudo mkfs -t ext3 /dev/sdk
sudo mount -t ext3 /dev/sdk /kaltura_storage - Copy the media assets directory over and soft link it
sudo cp -r --preserve=all /opt/kaltura/web/content/entry/ /kaltura_storage
sudo rm -r /opt/kaltura/web/content/entry
sudo ln -s /kaltura_storage/entry /opt/kaltura/web/content/entry - Copy the uploads directory over and soft link it
sudo cp -r --preserve=all /opt/kaltura/web/content/uploads/ /kaltura_storage
sudo rm -r /opt/kaltura/web/content/uploads
sudo ln -s /kaltura_storage/uploads /opt/kaltura/web/content/uploads - Create a tmp directory and edit the php.ini files to point to it
sudo mkdir /kaltura_storage/tmp
sudo chmod 777 /kaltura_storage/tmpEdit these two files:
/etc/php5/cli/php.ini
/etc/php5/apache2/php.iniand set
upload_tmp_dir = /kaltura_storage/tmp
- restart Apache
sudo apache2ctl restart
NOTE: Using this setup will cause warning messages to appear in the Kaltura
API log. The reason is explained here: http://bugs.php.net/bug.php?id=50676




Comments
15 gig volume out of space
I have followed the instructions and created a 1T volume with the links
but now after a few weekns my /dev/sda1, 15 gig volume has run out of space
what can I do now? my kaltura is showing up with a white screen after login
Try this at the command
Try this at the command prompt:
sudo du -kah / | sort -n -r | head -n 20
This should list the top 20 largest objects in your filesystem. Post the output.
J
I deleted a bunch of log
I deleted a bunch of log files and am now at 90% it was 100% >.<
here's what I have after.
du: cannot access `/proc/14293/task/14293/fd/4': No such file or directory
du: cannot access `/proc/14293/task/14293/fdinfo/4': No such file or directory
du: cannot access `/proc/14293/fd/4': No such file or directory
du: cannot access `/proc/14293/fdinfo/4': No such file or directory
1020K /usr/local/pentaho/pdi/docs/api/org/pentaho/di/resource
1020K /usr/lib/python2.6/lib-tk
1020K /usr/lib/python2.6/dist-packages/twisted/python
1020K /opt/kaltura/web/flash/kpaint/v1.0.1
1020K /opt/kaltura/log/sphinx/binlog.001
1020K /opt/kaltura_install/package/app/web/flash/kpaint/v1.0.1
1016K /usr/share/xml/iso-codes
1016K /usr/local/pentaho/pdi/docs/api/org/pentaho/di/trans/step/class-use/Step Meta.html
1012K /usr/share/automake-1.11
1012K /usr/lib32/gtk-2.0/2.10.0/engines
1008K /usr/lib32/libvorbisenc.so.2.0.6
1004K /var/lib/hobbit/histlogs
1004K /opt/kaltura_install/package/app/app/vendor/symfony
1004K /opt/kaltura/app/vendor/symfony
996K /usr/local/pentaho/pdi/libext/JDBC/h2.jar
992K /usr/share/info
992K /usr/share/autoconf/autoconf
988K /opt/kaltura/web/flash/kdp3/v3.3.9.2
988K /opt/kaltura_install/package/bin/linux/64bit/mencoder-dir/ffmpeg32bit/li b/libschroedinger-1.0.so.0
988K /opt/kaltura_install/package/bin/linux/32bit/ffmpeg-aux-dir/lib/libschro edinger-1.0.so.0
oh the log files were in
oh the log files were in /opt/kaltura/log/batch
I removed all the old ones before today
and that list doesn't seem to show the huge log files :(
There should be 10gig or so
There should be 10gig or so of free space after you first install the image. The files in your list are pretty small. Try this
command:
sudo find / -size \+10M -exec du -h "{}" \;
This will list all files greater than 10megabytes in size. If there are too many files listed, change the
"10" to "20" or larger.
Post your output.
Also, post your "df -h" output.
J
I did sudo find / -size
I did sudo find / -size \+10M -exec du -h "{}" \; | lessand got the following,
there were more inf "/kaltura_storage/entry/data/4/" and "/opt/kaltura/tmp/convert"
shouldn't the files in "/opt/kaltura/tmp/convert" be "/kaltura_storage/tmp" and shouldn't they get deleted after fles are converted
and is it safe to delete them
I have done the step:
Create a tmp directory and edit the php.ini files to point to it
sudo mkdir /kaltura_storage/tmp
sudo chmod 777 /kaltura_storage/tmp
Edit these two files:
/etc/php5/cli/php.ini
/etc/php5/apache2/php.ini
and set
upload_tmp_dir = /kaltura_storage/tmp
and checked those lines are in the .ini files.
15M /var/cache/apt/srcpkgcache.bin
15M /var/cache/apt/pkgcache.bin
98M /kaltura_storage/tmp/phpHZVUQi
13M /kaltura_storage/entry/data/4/267/0_xy9tvkmk_0_2xce60ls_1.mp4
22M /kaltura_storage/entry/data/4/267/0_7opsnzbr_0_4r4kx9gx_1.mp4
15M /kaltura_storage/entry/data/4/267/0_xx5fymm7_0_arqy1q2v_1.mov
21M /kaltura_storage/entry/data/4/267/0_bj1romnp_0_xr7ykh9d_1.mp4
31M /kaltura_storage/entry/data/4/267/0_hlul05aj_0_8pzubdhh_1.mp4
47M /kaltura_storage/entry/data/4/267/0_ch7fakc7_0_qvhabnvz_1.mp4
23M /kaltura_storage/entry/data/4/267/0_4qy7gu35_0_y0z7sk61_1.mp4
63M /kaltura_storage/entry/data/4/267/0_p8ilcnlz_0_ol6m8xao_1.flv
51M /kaltura_storage/entry/data/4/267/0_ivhgty1b_0_z1qm8is7_1.flv
83M /kaltura_storage/entry/data/4/267/0_nj6p6git_0_snsx1sr8_2.flv
15M /kaltura_storage/entry/data/4/267/0_2swu13vm_0_foe1d0ex_1.mp4
16M /kaltura_storage/entry/data/4/267/0_l6fenmss_0_qfww344t_1.mp4
13M /kaltura_storage/entry/data/4/267/0_7wltf76l_0_lcu1tdxz_1.mp4
26M /kaltura_storage/entry/data/4/267/0_0wumotpx_0_pkeba484_1.mp4
31M /kaltura_storage/entry/data/4/267/0_jfan3iua_0_5r1145xh_1.mp4
20M /kaltura_storage/entry/data/4/267/0_ch7fakc7_0_2pqc2awc_1.mp4
25M /kaltura_storage/entry/data/4/267/0_ujp0xkdb_0_p6xl05vj_1.mp4
21M /kaltura_storage/entry/data/4/267/0_olbxb4qc_0_xdn8knz0_1.mp4
52M /kaltura_storage/entry/data/4/267/0_6hqri8nj_0_lwrbpt5a_1.flv
38M /kaltura_storage/entry/data/4/267/0_g3uevkmi_0_sfp5632c_1.mp4
27M /kaltura_storage/entry/data/4/267/0_rj9ruhvx_0_3jvsocmk_1.mp4
11M /kaltura_storage/entry/data/4/267/0_atqnolhx_0_dgfosim8_1.mp4
13M /kaltura_storage/entry/data/4/267/0_iy4704az_0_ww344bhi_1.mp4
60M /kaltura_storage/entry/data/4/267/0_g3uevkmi_0_qoewmaow_1.mp4
25M /kaltura_storage/entry/data/4/267/0_ujp0xkdb_0_8cmsm9t2_1.mp4
:find: `/proc/13276/task/13276/fd/5': No such file or directory
find: `/proc/13276/task/13276/fdinfo/5': No such file or directory
find: `/proc/13276/fd/5': No such file or directory
find: `/proc/13276/fdinfo/5': No such file or directory
93M /tmp/phpcfE2pT
19M /tmp/oflaDemo-r3989-java6.war
37M /opt/kaltura/log/dwh.log
12M /opt/kaltura/web/content/templates/entry/data/SampleBigBuckBunnyTrailer.flv
11M /opt/kaltura/web/flash/mixplugins/v1.0/transitions/BrushAway/PaintBrush.fla
34M /opt/kaltura/tmp/convert/tmp_convert_4d124ec3dace0
15M /opt/kaltura/tmp/convert/tmp_convert_4d1236fb2128f
29M /opt/kaltura/tmp/convert/tmp_convert_4d1237e99ecc3
12M /opt/kaltura/tmp/convert/tmp_convert_4d123340ee410
12M /opt/kaltura/tmp/convert/tmp_convert_4d1129e5d262c
29M /opt/kaltura/tmp/convert/tmp_convert_4d111e24ee5c4
48M /opt/kaltura/tmp/convert/tmp_convert_4d111e408e04c
16M /opt/kaltura/tmp/convert/tmp_convert_4d135b68cd13d
23M /opt/kaltura/tmp/convert/tmp_convert_4d18cf237a713
32M /opt/kaltura/tmp/convert/tmp_convert_4d0cb73c3a10e
31M /opt/kaltura/tmp/convert/tmp_convert_4d12762877810
18M /opt/kaltura/tmp/convert/tmp_convert_4d1239bcd361e
15M /opt/kaltura/tmp/convert/tmp_convert_4d10a8e612705
18M /opt/kaltura/tmp/convert/tmp_convert_4d1237e8c4bb7
13M /opt/kaltura/tmp/convert/tmp_convert_4d112ab568947
49M /opt/kaltura/tmp/convert/tmp_convert_4d127576a0fdd
25M /opt/kaltura/tmp/convert/tmp_convert_4d13c880d3e29
25M /opt/kaltura/tmp/convert/tmp_convert_4d18d0a243cbb
14M /opt/kaltura/tmp/convert/tmp_convert_4d10ebb6c955c
21M /opt/kaltura/tmp/convert/tmp_convert_4d0fc619899b3
17M /opt/kaltura/tmp/convert/tmp_convert_4d1399ed88840
12M /opt/kaltura/tmp/convert/tmp_convert_4d126fc072136
12M /opt/kaltura/tmp/convert/tmp_convert_4d139a340dc28
16M /opt/kaltura/tmp/convert/tmp_convert_4d1102cb0744d
61M /opt/kaltura/tmp/convert/tmp_convert_4d0fc6e489933
46M /opt/kaltura/tmp/convert/tmp_convert_4d18d7dc918c9
37M /opt/kaltura/tmp/convert/tmp_convert_4d123af47081a
14M /opt/kaltura/tmp/convert/tmp_convert_4d10ed0193b63
22M /opt/kaltura/tmp/convert/tmp_convert_4d12349b6cd9d
27M /opt/kaltura/tmp/convert/tmp_convert_4d125163737c1
11M /opt/kaltura/bin/sphinx/searchd
12M /opt/kaltura_install/package/app/web/content/templates/entry/data/SampleBigBuckBunnyTrailer.flv
11M /opt/kaltura_install/package/app/web/flash/mixplugins/v1.0/transitions/BrushAway/PaintBrush.fla
11M /opt/kaltura_install/package/bin/linux/64bit/sphinx/searchd
47M /usr/lib/libgcj.so.10.0.0
15M /usr/lib/jvm/java-6-sun-1.6.0.22/lib/ct.sym
13M /usr/lib/jvm/java-6-sun-1.6.0.22/lib/tools.jar
12M /usr/lib/jvm/java-6-sun-1.6.0.22/jre/lib/amd64/server/libjvm.so
50M /usr/lib/jvm/java-6-sun-1.6.0.22/jre/lib/rt.jar
11M /usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server/libjvm.so
59M /usr/lib/jvm/java-6-openjdk/jre/lib/rt.jar
34M /usr/share/red5/red5-1.0-beta-r4150.zip
11M /usr/lib32/libQtGui.so.4.6.2
17M /usr/lib32/libQtWebKit.so.4.6.2
here is my "df -h" output:
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 15G 13G 1.5G 90% /
devtmpfs 3.7G 116K 3.7G 1% /dev
none 3.8G 0 3.8G 0% /dev/shm
none 3.8G 76K 3.8G 1% /var/run
none 3.8G 0 3.8G 0% /var/lock
none 3.8G 0 3.8G 0% /lib/init/rw
/dev/sdb 414G 199M 393G 1% /mnt
/dev/sdk 1008G 18G 940G 2% /kaltura_storage
BTW thanks for your help! :)
is there a fix so kaltura
is there a fix so kaltura will delete all the /opt/kaltura/tmp/convert/tmp_convert stuff?
start page does not appear
I have followed the instructions and tried to open the start page using the links provided at the end of the installation process but I can't open it. The browser reported a timeout.
2011-05-12 SSH Security Update
I see the AMI images have been updated with a security fix, although I can't find an advisory on the fix itself.
Can you please post instructions to apply the same fix to images built from the earlier AMI, if possible? I'm sure there are plenty of Kaltura CE sites who will not want to have to reinstall or migrate to a new image if they can avoid it.
@grobot ✿ www.giantrobot.co.nz
start page does not work
I am also getting timeout when I try to open the start page or admin console.
start page does not work
I just figured out that it was getting blocked because of security group rules. I added a rule to allow port 80 and it worked
can not connect to instance
I am trying to set up the Kaltura CE 3.0 running on 64-bit Ubuntu 10.4 LTS , I have it running. When I try to connect, both with the java and terminal, it just times out. Is there a specific username that you need to use to connect to the instance? I have tried ubuntu and root. Neither work.