Copyright © 2011 Kaltura Inc.
All Rights Reserved. Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Terms of Use and Privacy Policy.
EduVideo.org
Amazon ec2 AMI
Fri, 07/24/2009 - 14:43
Anyone have a Kaltura CE ec2 AMI available for testing?
Wed, 09/02/2009 - 19:20
#2
The AMI is: ami-2520c04c
kaltura-on-jaunty-x86/jaunty-kalturaCE-x86.manifest.xml
Once launched, go to the ec2 public DNS address in your web browser. If it errors on the check, just hit check again.
Use the following to setup the database and you are all set:
database: kalturaDB
username: kaltura
password: kaltura
As the title suggests, this is setup on the alestic Ubuntu 9.04 (32-bit). All components were installed from packages for easy management. The email server only works locally, so if make sure you write down the login you created, or reconfigure the email server before setup.
The mysql root password is t00r, which you can change once you have launched the instance.
We have not done a ton of testing, but so far it seems to be good.
Thu, 09/03/2009 - 23:08
#3
Thanks for putting that together :)
Mon, 12/21/2009 - 09:30
#4
I tried running this but the server keeps failing.
Has anyone set this up?
I used Firefox on MacOS 10.6.2 as a client.
Tue, 07/27/2010 - 14:14
#5
Hi all,
This AMI ami-2520c04c seems to be no more available... In which region did you found it ?
Thanks
Rgds.
Tue, 07/27/2010 - 21:14
#6
This Kaltura 1.5 ami has been deleted to prevent confusion with the upcoming 2.0 ami.
Wed, 07/28/2010 - 01:37
#7
The CE 2.0 Amazon AMI will be up soon!
Jason
Wed, 07/28/2010 - 07:30
#8
Great news !
Can post here the AMI id when available ?
Will it be available in all regions ?
Thanks
Rgds
Wed, 07/28/2010 - 15:11
#9
The AMI and all details will be posted on kaltura.org. It will start off in US-East region and maybe add EU. Any specific region you'd like?
Jason
Fri, 07/30/2010 - 19:23
#10
Hi,
same here.
EU region pls. Will it be pre-configured for the usage of Amazon's CloudFront?
BR
Sun, 08/08/2010 - 15:54
#11
It won't be pre-configured for Cloudfront which is a "push" type of CDN. It will, of course, work with most "origin pull" CDNs.
Jason
Wed, 07/28/2010 - 15:33
#12
EU would be nice to have. US East is ok.
Many thanks
Thu, 07/29/2010 - 02:15
#13
US WEST
Fri, 07/30/2010 - 05:59
#14
I havent work with Kaltura before but been active in using AWS.
Let me know if you need help in building the AMI. ;)
Fri, 08/13/2010 - 21:15
#15
I've generated a couple of AMIs in the US-East zone. This is a trial run to see how things go. We
have both 32-bit and 64-bit versions using EBS root.
AMI: ami-9a8c66f3 - Kaltura CE 2.0.2 running on 32-bit Ubuntu 10.4 with EBS root
AMI: ami-9e8c66f7 - Kaltura CE 2.0.2 running on 64-bit Ubuntu 10.4 with EBS root
The main prerequisite is an SMTP server since you need to be able to receive email msgs
in order to get login credentials for the KMC. We suggest using SendGrid.com (totally
free for under 200 emails per day) but you are free to use any service you want.
The attached README file (also included within the image) has details.
Jason
| Attachment | Size |
|---|---|
| README.txt | 2.63 KB |
Mon, 09/20/2010 - 16:29
#16
Any news on setting up an EU instance?
Mon, 09/20/2010 - 17:32
#17
Improved AMIs will be up soon. We may still launch in the East zone but can migrate to EBS in the EU zone soon after.
Wed, 10/13/2010 - 00:17
#18
I'm trying to use the Amazon ami-9a8c66f3 - Kaltura CE 2.0.2 running on 32-bit Ubuntu to evaluate Kaltura; the instance is running, but I'm not sure what username / password I should be using to connect to it. I tried root using Putty with my normal key, but Ubuntu doesn't seem to allow root access.
Any help is greatly appreciated.
Many thanks
Niall
Wed, 10/13/2010 - 14:17
#19
Ubuntu does not let you login as the root user by default. You need to use the user "ubuntu".
J
Mon, 11/15/2010 - 22:02
#20
I am also trying to ssh into the intstance, and am getting a "Connection refused" error. Is there another port that this instance is listening to ssh on? And, assuming I get into the instance, did I read correctly that this instance is not ready to just use...that I need to install Kaltura on it?
Thanks, in advance,
Tom Otvos
Mon, 11/22/2010 - 16:50
#21
Just as an FYI to my own post, the new 3.0-based AMIs work perfectly for me. Up and running in under 15 minutes. Many thanks to whoever put that together.
-- tomo
Wed, 10/13/2010 - 22:00
#22
Hi many thanks for your help; I now have access!
Fri, 11/19/2010 - 00:01
#23
Hey guys,
First off I'm a totally newbie (to Linux/coding but am pretty good figuring tech things out) so please bear with me.
I am currently trying to run the EC2 instance of KCE 3 (ami-ae0ef9c7 - This is Kaltura CE 3.0 running on 64-bit Ubuntu 10.4 LTS).
So far so good following all the steps outlined in the guide here http://www.kaltura.org/kaltura-ce-v30-amazon-ec2-guide
I've got the 64-bit instance created/running, set-up/configured my mail server (w/Sendgrid.com) as prescribed and allegedly successfully installed
Kaltura on my instance (see below KALTURA INSTALL APPEARS OKAY).
Whew. Crash course in linux thinking 4 sure! But know I'm stuck again and could use some help:
1) Despite everything appearing/running okay on both AWS/Kaltura: a) I didn't receive a confirmation e-mail after install (although sendgrid indicates it successfully went through)
b) When I go to the start page recommended by the install (http://ec2-50-16-61-9.compute-1.amazonaws.com/start) nothing happens and page fails to load.
2) After checking the log on the instance it reads "landscape-client is not configured, please run landscape-config." (see below EC2 LOG W/POSSIBLE LANDSCAPE ISSUE).
Is this something that I'm supposed to do (next/or have previously done) and if so how? It wasn't mentioned anywhere in the above mentioned guide/And I can't seem to
find any info on the web/Kalutura forums. Note: I rebooted the ec2 instance a short while after things weren't initially working and tried again but the page still didn't load.
Any thoughts would be greatly appreciated.
Thnx guys,
-JB
KALTURA INSTALL APPEARS OKAY
ubuntu@ip-xxxxxxx:/etc/postfix$ sudo service postfix restart
* Stopping Postfix Mail Transport Agent postfix
...done.
* Starting Postfix Mail Transport Agent postfix
...done.
ubuntu@xxxxxxxxx:/etc/postfix$ cd /opt/kaltura_install
ubuntu@ixxxxxxxxx:/opt/kaltura_install$ sudo php install.php
Thank you for installing Kaltura Video Platform - Community Edition
In order to improve Kaltura Community Edition, we would like your permission to send system data to Kaltura.
This information will be used exclusively for improving our software and our service quality. I agree (Y/n)
> X
If you wish, please provide your email address so that we can offer you future assistance (leave empty to pass)
> xxxxxxxx
Your primary system administrator email address
> xxxxxxxxxx
The password you want to set for your primary administrator
> xxxxxxxxxx
Copying application files to /opt/kaltura
Copying binaries for linux 64bit
Replacing configuration tokens in files
Changing permissions of directories and files
Creating and initializing 'kaltura' database
Creating and initializing 'kaltura_stats' database
Creating data warehouse
Creating system symbolic links
Deploying uiconfs in order to configure the application
Creating the uninstaller
Running the sphinx search deamon
Populating sphinx entries
Running the batch manager
Sent post installation settings email to xxxxxxxxxxxx
Installation Completed Successfully.
Your Kaltura Admin Console credentials:
System Admin user: xxxxxxxxxxx
System Admin password: xxxxxxxxxx
Please keep this information for future use.
Restarting Apache....
... waiting ...done.
The start page is at:
http://ec2-50-16-61-9.compute-1.amazonaws.com/start
The KMC is at:
http://ec2-50-16-61-9.compute-1.amazonaws.com/kmc
Login to the Admin Console at:
http://ec2-50-16-61-9.compute-1.amazonaws.com/admin_console
ubuntu@xxxxxxxxxx:/opt/kaltura_install$
EC2 LOG (W/POSSIBLE LANDSCAPE ISSUE)
Starting AppArmor profiles
[80G
[XXG[ OK ]
Starting memcached: memcached.
* Starting Postfix Mail Transport Agent postfix
[80G
[XXG[ OK ]
landscape-client is not configured, please run landscape-config.
* Starting web server apache2
[80G
[XXG[ OK ]
* Starting Hobbit Server hobbitd
[80G
[XXG[ OK ]
Fri, 11/19/2010 - 15:56
#24
Did you associate an Elastic IP address with your instance? It's not required, but one reason I can think of that your
start page wouldn't load is if you installed it with the default IP address and then associated an Elastic IP address.
Another reason is if you *didn't* associate an Elastic IP address, and then you rebooted (stop/start) the instance -- the IP address will probably change (dynamically
assigned by EC2) and then your start page probably won't come up either.
The landscape-client message doesn't affect the instance. You can ignore it.
Also, be sure and look in your spam folder for the email messages. Sometimes they go in there.
Jason
Mon, 11/22/2010 - 01:08
#25
Thanks MellowK for the info. "You're Da Man, You nailed it!" (but I still need a lil more advice-see below).
I think that's exactly what happened: "...you installed it with the default IP address and then associated an Elastic IP address".
I also, as you said, didn't manually (in the drop down window) "associate" the Elastic IP address to the instance 'cause I figured it was automatically associated when created. My bad as well. Regardless...
Once I figured that out (and attached as mentioned), I applied some brute force to teach myself ssh/unix (on Mac OSX---ouch!) and finally got it all working!!!
It was awesome! Setup the a publisher account, uploaded some videos, all the usual stuff then almost an hour in outta no where BAM! "Internal Server Error Occured" (see attache png file).
Sux. So since I'm a newbie I figured it was the server (the EC2 instance) not the software install so I (stupidly/unknowingly) went to EC2 and rebooted the instance in hopes of making things better-bad idea. I also thought an Elastic IP worked more like a static IP feature and would retain the original IP address-also bad assumption. So as you know as a pro (and I didn't as the newbie), the IP address dynamically changed-ouch. So now both the Kaltura install, as well as myself, are confused/stuck.
I think it's because I set-up/installed CE w/the initial IP address and now it's completely different. So what do I to fix this without re-installing/re-building from scratch (and losing my already uploaded videos)? Is there a simple file that can be altered to add the new IP address?
Any thought would be greatly appreciated bud.
Thanks,
JB
| Attachment | Size |
|---|---|
| Kaltura_Server Error.png | 74.2 KB |
Mon, 11/22/2010 - 07:33
#26
I'm not sure about the internal server error, but please look in the /opt/kaltura/log directory and look at the kaltura_apache_errors.log file for anything that looks like an internal server error.
As far as your IP address issues, first thing to note is that it takes several minutes for the Elastic IP to associate to your running instance. So, wait 5 minutes after associating before trying anything. Once associated, that's the Elastic IP address you need to use for that instance FOREVER (since we don't have any easy way to change the IP address in your installed Kaltura software).
To fix your problem (I hope), simply associate the old Elastic IP address to the running instance. The existing dynamically assigned IP address will magically disappear 5 minutes after you do that. (Elastic IPs are tied to your account, not to any instance, so you should still own that old Elastic IP until you "release" it).
Note: When you "reboot", the Elastic IP stays associated to the instance and you should have no issues. My guess is that you should rarely, if ever, need to reboot. However, if you "stop" the instance, the Elastic IP is DISassociated. When you "start" the instance, you need to associate THE SAME Elastic IP address again (and wait 5-10 minutes) before proceeding. Stopping the instance will save you a lot of money since you don't pay anything (except minimal storage charges) when an instance is in the "stopped" state.
Sat, 11/27/2010 - 01:06
#27
Seriously thanks again for all your input Mellow K. (Especially so close to the Holiday)!
Worked like a charm.
Everything is up a running again (ubercool!). It really was about waiting the 5-10 mins. for the Elastic IP (association) to kick-in.
Managed somehow to get through the "Internal Server Error" but not sure if it will reappear at some point. Hopefully not.
Also, sorry, but I haven't had a chance to check the Apache logs cause I'm now having difficulties logging back into the server via SSH on my mac (OSX/Terminal). Even though everything is working fine (on EC2) I can't seem to get in. No worries though... It must be 'cause I'm still a newbie to the whole SSH/OSX/Terminal thing and all their intricacies. But eventually I'll brute force through it and report back in regards to anything that appears "wonky".
It also seems that I am having trouble with Adaptive Bitrate playback (says that "clip is missing" - see attachment). Maybe it's just not supported with KCE. I do have multiple flavors of the videos so I must be missing a lil' something technically there as well.
Lastly, I just wish KCE allowed us to encode/playback directly to/from our own AWS S3 buckets w/Cloudfront (not Kaltura Free) storage. That would be awesome and completely "open" in all senses of the word but I read the previous post on the matter so I'll just have to wait til that gets worked out or someone writes a cool script.
FWIW-This is my first real journey into an "open source" project and have to say that KCE 3 is an amazing effort as is the support that you (and fellow Kalturians) have offered. Keep up the hard work because it is truly, truly appreciated. Rock on and...
Thanks Again,
Joe B.
PS- Was there a version bump to 3.0 over the last few days (v3.0.x- maybe)? If so, is anything required (by us) when there is an update? Or is it all just handled by the AMI instance? - thnx
| Attachment | Size |
|---|---|
| ClipError_Adaptive.png | 54.61 KB |
Sat, 11/27/2010 - 03:53
#28
Glad things are working. You'll need to ssh into the image using the Elastic IP address e.g.
ssh -i /Users/someuser/ec2keys/mykeys ubuntu@50.16.64.99
Here, 50.16.64.99 is your elastic IP address. I'm using the "-i" flag to point to my local key storage.
If you previously connected to the instance using the dynamically assigned IP address, you might
get a warning about a possible key-related attack. You can google around for the answer to that. :-)
You cannot use RTMP protocol unless you are connected to a streaming server such as Red5 or Adobe FMS.
J
Sat, 12/11/2010 - 20:53
#29
Hi, does anyone know if there is an AMI of KalturaCE 3.0 with red5 combined and working?
also has anyone tried connecting to an EC2 wowza instance to get rtmp working ? if so can you just config that through Kaltura CMS or do you need to hack some code?
Sat, 12/11/2010 - 23:58
#30
We'll have a Red5+CE3 AMI available shortly.
J
Sun, 12/12/2010 - 03:05
#31
great news j !!! will you post the ami number here when done or should i search EC2 AMI list?
Sun, 12/12/2010 - 19:40
#32
Watch the Kaltura developer blog: blog.kaltura.org
J
Mon, 12/13/2010 - 14:15
#33
Hi, I found these instructions detailing a CE3+Red5 ami-8005f3e9 but I cannot find the AMI on EC2 anywhere?
" Installing Red5 on the Pre-Integrated CE3+Red5 Amazon EC2 AMI
Kaltura offers an Amazon EC2 AMI with Red5 already pre-installed:
ami-8005f3e9 – This is Kaltura CE 3.0 with Red5 running on 32-bit Ubuntu 10.4 LTS
To get this instance up and running with both CE3 and Red5, follow these three steps:
* Install CE3 according to our Amazon EC2 Guide
* cd /home/ubuntu
* sudo bash kalred5.sh "
did that AMI have problems?
cheers, ben
Mon, 12/13/2010 - 15:10
#34
No issues. We just updated that document before the AMI went public. :-)
All the details are on the Kaltura developer blog:
http://blog.kaltura.org/one-step-red5-installation-with-kaltura-ce3
Sat, 12/25/2010 - 10:37
#39
Would it be possible to get an image for a local test server (vmware, KVM, or VirtualBox) of those nice AMIs? It would really help the willing-to-learn-to-get-it-to-work among us.
It would certainly be appreciated and helpfull in getting in with the rest of the band.
thanks.
Tue, 06/21/2011 - 09:56
#40
@MellowK: any news on setting up an EU instance?
Tue, 06/21/2011 - 18:20
#41
Hi,
Just U.S. East Coast at the moment. Do you need an EU image?
MK
Thu, 06/23/2011 - 14:44
#42
Hi,
yes please. The K4 64bit AMI would be great.
Cheers
Tue, 06/28/2011 - 16:07
#43
Hi - it would be really great to have the EC2 image use either CloudFormation parameters to set the hostname (or have it part of the installer script to prompt for domain name) - in K3 had to modify the installer script to not use the Amazon public DNS name.
An AMI in EU region would be pretty awesome as well, I wouldn't mind one in Asia as well (Singapore) would just be super awesome for an upcoming project.
[ Although, if the Amazon CloudFront integration works smooth should be less of a problem. ]
Thanks for the good work. Looking forward to K4 on EC2.
Mon, 08/22/2011 - 17:16
#44
Any ETA for an update to the K4 image? The test image is quite buggy and the K3 images have been removed and hence no other option but to use the buggy K4 image (with a project in progress at the moment)... any update appreciated.
Sat, 10/22/2011 - 12:35
#45
I did as said ...I associated elastic ip before installing kalturaCE4. I installed it successfully and everything was working fine. Then I rebooted my instance and then the problem occured.I reattatched my elastic ip and logged into my instance.
But now i can not do anything. I click any of the tabs and get "internal Server error". what to do?
Waiting for your answer "Mr. MellowK"
Any help will be appreciated
Thanks in advance
Cheers
There is the following AMI listed in the EC2 public images, it may be of use, although we have not tried it out yet:
ami-f78a6c9e