VOD Packager and PRIMARY_MEDIA_SERVER_HOST

lsonzogni · January 24, 2018, 12:20pm

Hello All,
I have several server roles (Cluster Installation), DB, DWH, FrontEnd, VOD Packager, etc.
I have some trouble for playing VOD and Live entries. The “Edit Entry” function works OK, the URL is something like that: http://front01.cdn.xxxxx.com/p/101/sp/10100/serveFlavor/entryId/0_wpkc6kyh/v/2/ev/3/flavorId/0_0hep5n0i/forceproxy/true/name/a.mp4
The url points to FRONTEND server.

BUT…when I try “Preview & Embed” the URL is NOT WORKING. May be because points to VOD Packager Server (that’s logical): http://vodpackager1.cnd.xxxxx.com:88/hls/p/101/sp/10100/serveFlavor/entryId/0_wpkc6kyh/v/2/ev/3/flavorId/0_82kbtp9d/name/a.mp4/manifest.m3u8

May be I misstaked configuring /opt/kaltura/app/configurations/system.ini , /opt/kaltura/app/configurations/media_servers.ini, and /opt/kaltura/app/configurations/broadcast.ini

I dont know what means “PRIMARY_MEDIA_SERVER_HOST” related to VOD Packagers and FrontEnd Servers…and, there is NO “SECONDARY_MEDIA_SERVER_HOST”???.

Is conceptual problem…and…I dont get it!!!

Thanks.

jess · January 25, 2018, 3:09pm

Hi @lsonzogni,

Let’s talk about VOD first:)
The Nginx host [where the kaltura-nginx package which includes the nginx-vod-module is deployed] needs to be accessible from all devices requesting playback. You can certainly put a load balancer in front of the Nginx nodes so that only it is accessible from the outside, SSL offloading to the nodes.

A rather detailed explanation of the different configurations related to delivery via the VOD module can be found here:

You can read about how the Nginx SSL config here:

github.com

kaltura/platform-install-packages/blob/Mercury-13.12.0/doc/nginx-ssl-config.md

### Nginx SSL configuration

The kaltura-nginx package is used for two functions:
- On-the-fly repackaging of MP4 files to DASH, HDS, HLS, MSS using [VOD module](https://github.com/kaltura/nginx-vod-module)
- RTMP Live Streaming using the [RTMP module](https://github.com/arut/nginx-rtmp-module)

**A general note about SSL: if you have a CE cluster, as opposed to an all in one instance, it is wise to use a load balancer configured to perform SSL offloading to the various Kaltura API and Nginx nodes.**

You can read more about load balancing here:

[RPM cluster howto](rpm-cluster-deployment-instructions.md#apache-load-balancer)

[deb cluster howto](deb-cluster-deployment-instructions.md#apache-load-balancer)

During the post install configuration phase, you will be prompted about whether or not you'd like to configure Nginx over SSL.
In the event you choose to do so, you will be prompted for the SSL certificate and key files as well as the port you'd like to use [default SSL port is 8443 since 443 is used by Apache].
Once the configuration is done, you should also adjust the delivery_profile.url column like so:
```
# mysql -h$DB1_HOST -u $DB1_USER -p$DB1_PASS -P$DB1_PORT $DB1_NAME
mysql> UPDATE delivery_profile SET url = REPLACE(url, '$NGINX_HOST:$NGINX_NON_SLL_PORT', '$NGINX_HOST:$NGINX_SLL_PORT') WHERE url LIKE '$NGINX_HOST:$NGINX_NON_SLL_PORT%';

This file has been truncated. show original

We also have templates for configuring SSL offloading with HAProxy and Apache’s mod_proxy, see links in the howto.

In regards to live streaming, kaltura-nginx is also shipped with the RTMP module, which you can use for live streaming. See:

/opt/kaltura/app/configurations/media_servers.ini is not needed for that. It is only being used by the “Kaltura Live Streaming” option is meant to work with Wowza, which is not FOSS.

This solution [consisting of https://github.com/kaltura/media-server and https://github.com/kaltura/livedvr and Wowza] is not officially supported when using CE though as you can see, the repos are FOSS and licensed under AGPLv3 so if you’d like to deploy them manually from the source, you are welcome to do so.

Like I said, you’ll also need to pay for a Wowza license. If you do decide to try, use Wowza of version 4.7.3. It’s important to state that I cannot commit to providing support for this but you are always welcome to post additional questions.

lsonzogni · February 5, 2018, 2:12pm

Thanks for the info Jess. Now, after reading and checking your answer, is working OK!!!

jess · February 6, 2018, 9:24am

Hi @lsonzogni,

Glad to hear we’re good:)

Happy videoing,