Additional materials

Operational appendices: scaling OTT delivery via caching proxies and CDN, connecting external monitoring systems, tuning the node for large installations, the Intel hardware requirements for hardware transcoding, and managing the node from outside — the HTTP API, how the settings file is built and how to edit and carry it.

• Caching and CDN for OTT delivery
  • 1. Caching model
  • 2. Client behaviour
  • 3. Special mechanisms
  • 4. Request parameters
  • 5. Load characteristics
  • 6. Nginx as a caching reverse proxy
  • 7. Client-side caching
  • 8. Delivery through a CDN
  • 9. Monitoring
  • 10. Diagnostics
  • 11. Security
  • 12. Middleware integration
• Connecting external monitoring systems
  • Files
  • Installation
  • Configuration
  • Quick start
  • Metric paths
  • Zabbix integration
  • Prometheus integration
  • Telegraf / InfluxDB integration
  • HTTPS and authentication
  • Exit codes
  • Troubleshooting
• Node performance tuning
  • CPU load
  • Memory
  • Statistics and EPG databases
• Intel VPL transcoder: supported hardware
  • Two Intel runtimes
  • Codecs
  • Cut-down Atom hardware: not supported
  • What must be installed
  • How to check
• Managing the node over the HTTP API
  • Access
  • What the API is made of
  • How errors arrive
  • Changes that need a restart
  • The API or the settings file
  • Reference documents
• The pss.json settings file
  • What this file is
  • The file holds only the differences from the defaults
  • The structure of the document
  • What the service does when it reads the file
  • Rules that are not visible in the file
  • Values that must not be passed on
  • Checking against the JSON Schema
  • Compatibility between versions
• Editing, checking and carrying the settings
  • What you will need
  • Changing a parameter
  • Carrying the settings to another version
  • Carrying the settings to another node
  • The checks the schema does not do
  • Recovering after a refused file
  • Hints in the editor
  • In short