ambiser
/
openvidu
mirror of https://github.com/OpenVidu/openvidu.git
8
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
openvidu/openvidu-server/docker/openvidu-docker-compose/readme.md

299 lines
12 KiB
Markdown
Raw Blame History

# Openvidu Platform deployment
> **IMPORTANT NOTE:** This procedure is in development an can change in any moment. Please use it with care and visit the page with frecuency.
This document describes how to deploy OpenVidu Platform. It allows also to deploy OpenVidu Call videoconference application.
OpenVidu Platform is deployed as a set of docker containers managed with a docker-compose (Kubernetes Helm chart is in the works). Docker basic knowledge is not required, but recommended.
This procedure installs the following services:
- **OpenVidu Server (openvidu-server)**: This is the brain of OpenVidu platform. The signaling plane.
- **Kurento Media Server (kms)**: This is the hearth of the OpenVidu platform. In charge of media plane.
- **Coturn (coturn)**: Service used to allow media communications with browsers in certain special networks.
- **Redis (redis)**: Database to manage users in Coturn server.
- **Nginx (nginx)**: A reverse proxy used to configure SSL certificate and to allow both Openvidu Server and the Application in the standard https port (443).
- **Videoconference Application (app)**: OpenVidu Call application or any other application. Can be disabled.
## 1. Prerequisites
OpenVidu Platform can only be installed in Linux. Mac and Windows is not supported for production use. If you want to develop in Mac or Windows, please follow the [tutorials](https://docs.openvidu.io/en/2.12.0/tutorials/) to see how to execute OpenVidu in a single docker container.
You can use any modern Linux distribution supported by docker. We have tested with Ubuntu 18.04.
You will need docker and docker-compose installed in your linux distribution.
- [Install Docker](https://docs.docker.com/install/linux/docker-ce/ubuntu/)
- [Install Docker Compose](https://docs.docker.com/compose/install/)
Open ports:
- 22 TCP: To connect using SSH to admin OpenVidu.
- 80 TCP: If you select Let's Encrypt to generate an SSL certificate this port is used by the generation process.
- 443 TCP: OpenVidu server and application are published in standard https port.
- 3478 TCP: Used by TURN Server to stablish media connections.
- 3478 UDP: Used by TURN Server to stablish media connections.
- 40000 - 57000 UDP: Ports used by Kurento Media Server to stablish media connections.
- 57001 - 65535 UDP: Used by TURN Server to stablish media connections.
It is important to have a **domain name** pointing to the machine where you are are going to deploy OpenVidu. The platform is deployed using https because is mandatory to use WebRTC. Then, if you do not have a domain name, an ugly warning will appear to your users when enter to your site. And, of course, you can suffer a man in the middle attack. You don't need a valid SSL certificate as one can be created by Let's Encrypt in the installation process.
## 2. Deployment
Execute the following command to download and execute the installation script:
`curl https://raw.githubusercontent.com/OpenVidu/openvidu/master/openvidu-server/docker/openvidu-docker-compose/install_openvidu.sh | bash`
It will donwload all required files into `openvidu` folder and will show this message with basic instructions:
```
Openvidu Platform successfully installed.
1. Go to openvidu folder:
$ cd openvidu
2. Configure DOMAIN_OR_PUBLIC_IP and OPENVIDU_SECRET in .env file:
$ nano .env
3. Start OpenVidu
$ ./openvidu start
For more information, check readme.md
```
## 3. Configuration
OpenVidu Platform configuration is specified in the `.env` file with environment variables.
**YOU MUST** specify the **DOMAIN_OR_PUBLIC_IP** of the machine and the **OPENVIDU_SECRET**. They are empty and execution will fail if you do not specify them.
If you have a domain name, generate a certificate with Let's Encrypt or put your own certificate.
All other configuration properties comes with sane defaults.
The `.env` file looks like this:
```
# OpenVidu configuration
# ----------------------
# Documentation: https://docs.openvidu.io/en/stable/reference-docs/openvidu-config/
# NOTE: This file doesn't need to quote assignment values, like most shells do.
# All values are stored as-is, even if they contain spaces, so don't quote them.
# Domain name. If you do not have one, the public IP of the machine.
# For example: 198.51.100.1, or openvidu.example.com
DOMAIN_OR_PUBLIC_IP=
# OpenVidu SECRET used for apps to connect to OpenVidu server and users to access to OpenVidu Dashboard
OPENVIDU_SECRET=
# Certificate type:
# - selfsigned: Self signed certificate. Not recommended for production use.
# Users will see an ERROR when connected to web page.
# - owncert: Valid certificate purchased in a Internet services company.
# Please put the certificates files inside folder ./owncert
# with names certificate.key and certificate.cert
# - letsencrypt: Generate a new certificate using letsencrypt. Please set the
# required contact email for Let's Encrypt in LETSENCRYPT_EMAIL
# variable.
CERTIFICATE_TYPE=selfsigned
# If CERTIFICATE_TYPE=letsencrypt, you need to configure a valid email for notifications
LETSENCRYPT_EMAIL=user@example.com
...
```
> **NOTE:** If you want to try OpenVidu in your linux development machine:
> * If you set `DOMAIN_OR_PUBLIC_IP=localhost` then in your browser you have to use `https://localhost/`. If you use `https://127.0.0.1/` instead, you will have some issues.
> * OpenVidu services will use some host ports that have to be available: 80, 3478, 5442, 5443, 8888 and 6379.
### Videoconference application
By default, the [OpenVidu Call application](https://docs.openvidu.io/en/stable/demos/openvidu-call/) is deployed alongside OpenVide Platform. It is accesible in the URL:
```
https://openvidu_domain_or_public_ip/
```
This application is defined in the file `docker-compose.override.yml`.
To disable OpenVidu Call application, you can delete the file `docker-compose.override.yml` (or renaming it in case you want to enable again in the future).
You can configure any other application updating the content of `docker-compose.override.yml` with the following requirements:
* Application server port must to be binded to 5442 in the host, as this port is used by NGINX to publish your app in port default https port (443).
* The application must be served in plain http as NGINX is the responsible of managing SSL certificate.
* Application has to know OpenVidu Server URL. You can use the variables ${DOMAIN_OR_PUBLIC_IP} and ${OPENVIDU_SECRET} in `docker-compose.override.yml` file.
* The application and OpenVidu platform are deployed in the same domain. For that reason, the following URLs are reserved for OpenVidu and you cannot use them in the application:
* `/api/`
* `/openvidu/`
* `/dashboard/`
## 4. Execution
To start OpenVidu Platform (and the application if enabled) you can execute this command:
```
$ ./openvidu start
```
Then, all docker images for services will be downloaded (only the first time) and executed.
The first part of the log shows how to docker-compose command execute all services:
```
Creating openvidu-docker-compose_coturn_1 ... done
Creating openvidu-docker-compose_app_1 ... done
Creating openvidu-docker-compose_kms_1 ... done
Creating openvidu-docker-compose_nginx_1 ... done
Creating openvidu-docker-compose_redis_1 ... done
Creating openvidu-docker-compose_openvidu-server_1 ... done
```
Then, `openvidu-server` service logs are shown.
When OpenVidu Platform is ready you will see this message:
```
----------------------------------------------------
OpenVidu Platform is ready!
---------------------------
* OpenVidu Server: https://server/
* OpenVidu Dashboard: https://server/dashboard/
----------------------------------------------------
```
You can press `Ctrl+C` to come back to the shell and OpenVidu will be executed in the background.
If the application is enabled, it is available in `https://server/`.
You can open OpenVidu Dashboard to verify if the platform is working as expected go to `https://server/dashboard/` with credentials:
* user: OPENVIDUAPP
* password: the value of OPENVIDU_SECRET in `.env` file.
## 6. Stop execution
To stop the platform execute:
```
$ ./openvidu stop
```
## 6. Changing configuration
To change the configuration:
* Change configuration in `.env` file
* Restart the service with command:
```
$ ./openvidu restart
```
## 5. Problems
### Configuration errors
If you have any problem with the configuration, when you start OpenVidu the following report will be shown:
```
Configuration errors
--------------------
* Property OPENVIDU_SECRET is not set. Cannot be empty.
* Property DOMAIN_OR_PUBLIC_IP is not set. Cannot be empty
Fix config errors
---------------
1) Return to shell pressing Ctrl+C
2) Set correct values in '.env' configuration file
3) Restart OpenVidu with:
$ ./openvidu restart
```
### Docker compose
To solve any other issue, it is important to understand how openvidu is executed.
OpenVidu is executed as a docker-compose file. The commands executed by the script are the standard docker-compose commands:
* start
* `$ docker-compose up -d`
* `$ docker-compose logs -f openvidu-server`
* stop
* `$ docker-compose down`
* restart
* `$ docker-compose down`
* `$ docker-compose up -d`
* `$ docker-compose logs -f openvidu-server`
* logs
* `$ docker-compose logs -f openvidu-server`
As you can see, logs of `openvidu-server` service are shown when platform is started or restarted. This log contains the most important information for the OpenVidu execution.
### Show service logs
Take a look to service logs to see what happen. First, see openvidu-server logs:
```
$ ./openvidu logs
```
Then, you can see all service logs togheter:
`$ docker-compose logs -f`
Or you can inspect one by one the other services:
```
$ docker-compose logs -f kms
$ docker-compose logs -f nginx
$ docker-compose logs -f coturn
$ docker-compose logs -f redis
$ docker-compose logs -f app
```
### Review the configuration
Sometimes, we can have a typo when writing a property name. For this reason, openvidu-server print in the log all the configuration properties you are configured in `.env` file and the default values for all other config properties. In that way, you can double check what openvidu-server *see*.
If `openvidu-server` detects some error, it will show it in the log.
```
Configuration properties
---------------------
* CERTIFICATE_TYPE=selfsigned
* OPENVIDU_CDR=false
* OPENVIDU_CDR_PATH=/opt/openvidu/cdr
* DOMAIN_OR_PUBLIC_IP=my.domain.com
* OPENVIDU_RECORDING=false
* OPENVIDU_RECORDING_AUTOSTOP-TIMEOUT=120
* OPENVIDU_RECORDING_COMPOSED-URL=
...
```
### Java options
To use java options in openvidu-server change the property `JAVA_OPTIONS` in configuration file `.env`
For more information about posible values for java option visit [Configuring Java Options](https://docs.oracle.com/cd/E37116_01/install.111210/e23737/configuring_jvm.htm#OUDIG00007)
### Change log level of the services
To change the level of `openvidu-server` logs change the property `OV_CE_DEBUG_LEVEL`.
To change the level of Kurento Media Server `kms` logs change the property `KMS_DEBUG_LEVEL`. For more information about possible values visit https://doc-kurento.readthedocs.io/en/stable/features/logging.html
### Change Kurento Media Server docker image
OpenVidu and Kurento Media Server evolves at different rithm. Sometimes, it is possible that a new KMS is released but OpenVidu is not still updated. In that case, in case you hit a bug and that bug is solved in last KMS version, you can test if updating only KMS is working for you. `KMS_IMAGE` property allows you to specify the new KMS image.
Reference in New Issue View Git Blame Copy Permalink