Skip to main content

Server Requirements

(Картинка)

Component Interaction​

  • Admin Interface (Web Version) - Server: HTTP protocol port 443 (if a certificate is installed on the server) or 80 (if no certificate is installed)

  • Player - Server: HTTP protocol port 443 (if a certificate is installed on the server) or 80 (if no certificate is installed)

Server and resource requirements for deployment on customer premises (virtual machines can be used). Use of virtual machines is allowed.

Server requirements:

  • 1-500 devices: 8 GB RAM, 4x CPU Core i5+, 250GB SSD (preferably 500GB)
  • 500-2000 devices: 16 GB RAM, 8x CPU Core i5+
  • 2000-5000 devices: 64 GB RAM, 24+ CPU Core i5+
  • 5000-10000 devices: horizontal cluster consisting of two mirrored application servers (48 GB RAM, 32x CPU Core i5+) + load balancer

Server preparation:

  1. Prepare a physical or virtual machine in any virtualization environment. Operating system Ubuntu Server 16.04 LTS or higher.

  2. Configure SSH access to the server.

  3. Important! For a large number of players (500+), we recommend using a separate media storage based on Amazon S3 or Mail.ru S3 to reduce the load on the Oohdesk CMS server. Any services are allowed (including local ones).

  4. Create an internal domain/subdomain which will resolve to the server (virtual machine) so that players can connect to the server. It is allowed not to have a domain and use just an IP address, although it is not recommended. That is, create a domain like visiobox.domain.com and set an A-record pointing to the server IP.

  5. Publish SSH protocol to the Internet for the server (virtual machine) if installation and configuration are done by Oohdesk CMS technical support.

  6. Provide full (all ports) direct access or via HTTPS-proxy to the following domains and subdomains:

  • registry.visiobox.cloud

  • sentry.visiobox.cloud (monitoring service)

  • license.visiobox.ru

  • license.visiobox.cloud

  • sks-keyservers.net (keys and certificates)

  • github.com

  • archive.ubuntu.com

  • cloudfront.net

  • mcs.mail.ru or amazonaws.com (if using external storage)

  • maps.googleapis.com link (maps and reverse geocoding when creating devices – time zones are calculated)

  • google.com link (maps and reverse geocoding when creating devices – time zones are calculated)

  • Create an email account from which clients will receive emails. Something like robot@domain.ru link and provide SMTP server, login/password (if Oohdesk CMS is configuring the server).

Important!

Since all player-server communication is done via WebSocket protocol, no traffic signatures should be truncated.

If you decided to deploy your own S3:

Storage requirements (Amazon S3 equivalent)

Upload (for content uploading): Server compatible with AWS S3 protocol (for example) link

Download (for content downloading by players): Access to files via HTTPS protocol through a single URL (geographic DNS)