Hi, on server-side in 2.12, a service was automatically created for OpenVidu during deployment. The servernode also auto-detected any up-and-running medianodes that were defined in the config. I don’t see those features in the 2.13 release? Are they hidden somewhere or should we write the code for that ourselves?
In the case of writing it ourselves:
What .sh script should be launched on startup of the server- and medianodes?
Are there any templates for the openvidu_launch_kms.sh and openvidu_drop.sh scripts? (I don’t remember the exact names)
The same set of features provided in 2.12 version is provided in 2.13. You don’t have to do any additional task on your side. That is… the services you are referring to are included in OpenVidu services…
If you have any specific issue with 2.13, please describe it.
Rebooting the nodes do not start the appropriate openvidu services, not as I can see at least. I have to manually cd into the respective folder and run the command specified in the docs.
The .env file does not have any settings for URIs to Media Nodes, so since I haven’t set up any of those, the server node does not find any of the media nodes, and would have to manually be added in the inspector. Where do I insert the startup KMS URIs?
Nevermind, found the KMS URI setting at the bottom of the .env file? Probably shouldn’t be below the “If you’re working outside AWS ignore this section” header?
A bug(?) is that if the media-node is not running at the time the server-node searches for it, the server just stops, it doesn’t retry in x second intervals.
What you want is to manually configure a set of Media Nodes URIs in OpenVidu Server Pro Node, so when restarting this node all of them are always automatically connected, right?
Two things about this:
This is not the official supported behavior of On Premises deployment of OpenVidu Pro. That’s why KMS_URIS config property is not documented in OpenVidu configuration page. A restart of OpenVidu Server Pro Node in On Premises deployments will require to manually add all the desired Media Nodes to the cluster, as documentation states:
AWS deployments (and in the future other cloud providers) do not require this because of the control OpenVidu has over the infrastructure. It is able to automatically discover any running Media Node, and to launch or drop Media Nodes on startup until the desired number is reached. But in On Premises deployments OpenVidu does not have any control over the infrastructure, so admins must add the Media Node to the cluster once OpenVidu Server Pro Node is up an running.
That being said, OpenVidu will try to honor property KMS_URIS if it finds it in .env file. But the behavior you want (that it remains trying to connect to all of the URIs defined in the property without stopping even when some URI is not reachable) is not contemplated. If OpenVidu finds any value inside KMS_URIS array, then those URIs must be accessible on startup or OpenVidu will shut down.
Yes I understand that a lot of these features are only available on AWS, but in 2.12 PRO, the OpenVidu services would automatically launch with VM boot, and would iterate over given KMS URIs and connect to those available automatically.
This was in the on premise solution.
So what I understand is that this feature has been removed from the on premise solution going from 2.12 to 2.13?
Well, it has been “hidden” in the documentation as we understood was for the better, as it introduced a complex and variable factor on OpenVidu startup process.
But as I said, if you want you can still use it. It works exactly the same way as in 2.12.0. The URIs you define in KMS_URIS array must be valid on OpenVidu startup. This hasn’t changed from 2.12.0.
Kinda liked the option to just click “Start” in Azure VM on Server- and MediaNodes and let them do their thing.
Now I have to start VMs, SSH into them, start services, then connect them in Inspector.
In 2.12, the Systemd service was automatically created, but that’s not the case anymore. Do you have a template for openvidu.service file that works with the new launch scripts?
We are working on providing a better configuration experience in OpenVidu PRO deployed on premises and restarting the service without losing connection between master and media nodes.
