About the Pexip Infinity software files

The Pexip Infinity platform is entirely software-based, and is deployed by installing the files provided by Pexip onto your hypervisor or cloud platform to create Virtual Machines (VMs), which you then configure appropriately for your environment.

The Pexip Infinity version 34 release includes the files described below. Which set of files you require depends on:

  • the hypervisor or cloud platform you are deploying on
  • whether you are deploying a new instance of Pexip Infinity, upgrading an existing deployment, or deploying a new Conferencing Node
  • if you are deploying new generic Conferencing Nodes in unsupported or non-standard environments.

No changes should be made to any Pexip VM via the terminal interface (other than as described when running the initial Pexip installation wizard) unless directed to do so by Pexip support. This includes (but is not limited to) changes to the time zone, changes to IP tables, configuration of Ethernet interfaces, or the installation of any third-party code/applications.

Upgrading an existing deployment (all environments)

The Pexip Infinity upgrade package is required when upgrading an existing deployment. It is used to upgrade all deployment environments.

Description File name Location Hypervisor Notes
Pexip Infinity upgrade package

Pexip_Infinity_v34_UPGRADE_<build>.tar

Pexip download page Any hypervisor or cloud platform Used when upgrading the Pexip Infinity platform to version 34. For more information, see Upgrading the Pexip Infinity platform.

Deploying the Management Node on an on-prem hypervisor

Use one of these files when deploying the Management Node on an on-prem hypervisor.

Description File name Location Hypervisor Notes
Pexip Infinity OVA

Pexip_Infinity_v34_generic_pxMgr_<build>.ova

Pexip download page Any hypervisor except Microsoft Hyper‑V

Used to deploy a new generic Management Node VM using VMware, KVM or other hypervisors except Microsoft Hyper‑V. For more information, see:

Pexip Infinity ZIP

Pexip_Infinity_v34_HyperV_pxMgr_<build>.zip

Pexip download page Microsoft Hyper‑V Used to deploy a generic Management Node VM using Hyper‑V. For more information, see Installing the Management Node — Hyper-V hypervisors.

Deploying new Conferencing Nodes on supported hypervisors

There is no requirement to download any files from the Pexip website when deploying new Conferencing Nodes on VMware, Hyper‑V, or KVM hypervisors, as the relevant file is generated on request by the Management Node.

Deploying the Management Node or Conferencing Nodes on cloud environments (Azure, AWS, GCP or Oracle)

There is no requirement to download any files from the Pexip website when you are deploying the Pexip Infinity Management Node or Conferencing Nodes on an AWS or Azure cloud platform — the relevant Pexip image files are hosted on the AWS/Azure platform instead. However, GCP and Oracle image files are downloadable from the Pexip website.

For specific deployment information about each platform, see:

Deploying new generic Conferencing Nodes on non-supported hypervisors or orchestration layers

Use one of these files when deploying a Conferencing Node on other non-supported hypervisors or orchestration layers.

Description File name Location Hypervisor Notes
Generic Pexip Infinity Conferencing Node OVA

Pexip_Infinity_v34_generic_ConfNode_<build>.ova

https://dl.pexip.com/infinity/index.html

and then select the appropriate directory for your software version

Other environments that take .ova or .ovf files as input Used to deploy a generic Conferencing Node VM in environments that take .ova or .ovf files as input. For more information, see Deploying a Conferencing Node using a generic VM template and configuration file.
Generic Pexip Infinity Conferencing Node ZIP

Pexip_Infinity_v34_HyperV_ConfNode_<build>.zip

https://dl.pexip.com/infinity/index.html

and then select the appropriate directory for your software version

Hyper-V in a cloud-based environment Used to deploy a generic Conferencing Node VM using Hyper‑V in cloud-based environments or other orchestration layers where standard deployment is problematic. For more information, see Deploying a Conferencing Node using a generic VM template and configuration file.