Deploying Kaltura using Opscode Chef
This guide is intended for users of Chef that would like to deploy Kaltura clusters using Chef recipes.
Before You Get Strated Notes
- Please review the frequently answered questions document for general help before posting to the forums or issue queue.
- If you don't know what Chef is, start by reading An Overview of Chef.
- If you're looking to install Kaltura on a signle machine, see: Installing Kaltura on a Single All-In-One Server (RPM)
- If you're looking to deploy a cluster manually or using other automation tools, see Deploying Kaltura Clusters.
- Kaltura Inc. also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a Free Trial of the Kaltura.com Hosted Platform or learn more about Kaltura' Commercial OnPrem Edition™. For existing RPM based users, Kaltura offers commercial upgrade options.
Installing the Chef server
- Request this page: http://www.getchef.com/chef/install/
- Select the 'Chef Server' tab
- Select your distribution, version and arch and download
- Download the RPM or deb package depending on your distribution.
- The post install will provide instructions as to what else needs to be done to set the instance up.
- Obtain chef-repo from https://github.com/kaltura/platform-install-packages.git
- Upload the Kaltura recipes to your Chef server using:
# knife cookbook upload kaltura
- We also recommend you use the ready made recipes for MySQL, NFS and NTP which can be taken from here:
Note: you may also want to use this recipe for a simple Apache load balancer: http://community.opscode.com/cookbooks/apache_load_balancer
Run the following:
# curl -L https://www.opscode.com/chef/install.sh|sh # mkdir -p /etc/chef # knife configure client /etc/chef
/etc/chef/validation.pem from your Chef server onto
/etc/chef/client.rb and paste the following lines into it.
Make sure to modify your Chef server url
log_level :info log_location STDOUT chef_server_url 'http://yourchefserver.com:4000' validation_client_name 'chef-validator'
# chef-client -i 3600
Repeat this action for each node in your Kaltura cluster.
To test it, on the Chef server, run:
# knife node list
You should see your new nodes when running:
[root@chef-server ~]# knife node list kalturadev front.kaltura.dev batch.kaltura.dev dwh.kaltura.dev nfs
Alternatively, log in to Chef's web with https://chef-server/
You should see your added nodes under the "Nodes" tab as well as the "Clients" tab.
Loading the NFS and MySQL recipes to your Chef server
Download NFS and MySQL recipes:
These recipes have dependencies you will need as well. Please follow documentation on the above URLs.
Note that the MySQL recipe configures MySQL to listen on localhost only. You need to change this here: mysql/templates/default/my.cnf.erb:bind-address as the various nodes in your cluster will need access to it.
Loading the Kaltura recipes to your Chef server
# git clone https://github.com/kaltura/platform-install-packages.git # cp -r sources/platform-install-packages/chef-repo/cookbooks/kaltura /var/chef/cookbooks/kaltura/ # knife cookbook upload --all
Then to verify use
# knife cookbook list.
You should see output along the lines of:
[root@chef ~]# knife cookbook list build-essential 1.4.2 kaltura 0.1.0 line 0.5.1 mysql 4.0.20 nfs 0.5.0 ntp 1.5.5 openssl 1.1.0
The properties of your cluster should be set here:
When done editing, run:
# knife cookbook upload kaltura
Defining recipe run lists
Now that we have our cluster nodes registered, and our recipe uploaded to the Chef server, we need to assign a recipe[s] for each node type. The syntax for it is:
# knife node run_list add $NODE_NAME $RECIPE
An example cluster deployment will be:
# knife node run_list add mynfs kaltura::nfs-server # knife node run_list add mynfs nfs::server # knife node run_list add my-mysql-machine mysql::server # knife node run_list add my-batch-machine nfs # knife node run_list add my-batch-machine kaltura::batch # knife node run_list add my-sphinx-machine kaltura::sphinx # knife node run_list add my-sphinx-machine kaltura::db_config # knife node run_list add my-front-machine nfs # knife node run_list add my-front-machine kaltura::front # knife node run_list add my-dwh-machine kaltura::nfs # knife node run_list add my-dwh-machine kaltura::dwh
If at any point you would like to remove a role assignment, use:
# knife node run_list remove node 'recipe[COOKBOOK::RECIPE_NAME]'
Alternatively, log in to Chef's web I/F with https://chef-server
And deploy the cluster from the "Nodes"->"Edit" menu.
- The db_config runs from sphinx because it requires Kaltura's code which there is no reason to deploy on the DB machine.
- The above run lists are a recommedation, you can of course run more than one role per node.
- The order of the run_list is crucial. NFS needs to happen first. Note that your recipe should include creation of /opt/kaltura/web BEFORE the NFS recipe runs.
Running the Chef client
Installing on a node is done using the chef-client utility.
Note that the order in which you install the nodes matters!
It should be as following:
$ ssh my-mysql-machine root@my-mysql-machine:~# chef-client $ ssh my-front-machine root@my-front-machine:~# chef-client $ ssh my-sphinx-machine root@my-sphinx-machine:~# chef-client $ ssh my-batch-machine root@my-batch-machine:~# chef-client $ ssh my-dwh-machine root@my-dwh-machine:~# chef-client
Please this howto about auto provisioning EC2 images: https://learnchef.opscode.com/starter-use-cases/multi-node-ec2/