openvidu/openvidu-deployment
Piwccle 58172d785d openvidu-deployment: the same defaults and parameter names on every cloud
The templates of the five clouds had drifted apart. On AWS, Azure and Google
Cloud:

- 200 GB disk for the single node and the Master Nodes, the default where
  the template sets its size: Azure and Google Cloud raise it from 100 GB,
  as do the AWS High Availability Master Nodes. On Google Cloud an existing
  single node or Elastic Master Node keeps its disk when the template is
  applied again.
- Google Cloud boots the latest Ubuntu 24.04 (the ubuntu-2404-lts image
  family) instead of an image pinned in December 2024; an existing single
  node or Master Node is not recreated when a newer image is published.
- Same parameter names on every Terraform and Bicep template, with the old
  names deprecated but still honored (they win when set): rtcEngine on the
  Google Cloud single node, whose documented name was not applied, and
  masterNodeInstanceType on Google Cloud High Availability.
- Azure no longer opens port 9000 (MinIO) on the single node and Elastic:
  MinIO does not run there, and the other clouds closed it in 3.9.0.
- The Media Nodes install with the same arguments on every cloud: Azure
  passes --master-node-private-ip and no longer --enabled-modules, and the
  user-data names the variable MASTER_NODE_PRIVATE_IP everywhere.

The CHANGELOG also lists the DigitalOcean and Oracle Cloud changes made in
their repositories (v2compatibility by default, masterNodeInstanceType,
the Oracle single node size and disk, rtcEngine).
2026-10-27 19:11:15 +01:00
..
community openvidu-deployment: the same defaults and parameter names on every cloud 2026-10-27 19:11:15 +01:00
pro openvidu-deployment: the same defaults and parameter names on every cloud 2026-10-27 19:11:15 +01:00
CHANGELOG.md openvidu-deployment: the same defaults and parameter names on every cloud 2026-10-27 19:11:15 +01:00
update.sh openvidu-deployment: download the install scripts over HTTPS 2026-10-23 14:57:54 +02:00