flexVDI is a desktop virtualization platform. Using well-known, open-source technologies, it provides a stable, performant infrastructure for both Windows and Linux desktops. Its main features are:

flexVDI must be installed on a set of physical servers with either RHEL 7 or CentOS 7, that form a VDI cluster. This document will guide you through the process of installing flexVDI 3.0 on your physical servers.

Terminology

This document makes use of various flexVDI 3.0 specific concepts. Below you will find those terms with a brief description:

Components

Relationships between components:

The most simple configuration of a flexVDI platform, looks like this:

When a flexVDI Client is started, it connects to the flexVDI Manager, to ask for instructions; usually, flexVDI Manager first requests the flexVDI Client for credentials to authenticate the user. But unauthenticated access can be configured too.

Then  flexVDI Manager will start a virtual machine if needed, and send connection data to the flexVDIClient that started the session.

Finally, flexVDI Client will connect to a virtual desktop, which is served by a virtual machine running on one of the flexVDI Hosts.

Basic components run on a flexVDI Host

flexVDI Hosts are the hypervisor machines; they run most of the software which communicates with the flexVDI Clients. In a basic installation, they run:


flexVDI Gateway usually runs on flexVDI Hosts too, although it is not needed in every deployment.

flexVDI Gateway

The flexVDI Gateway is a part of the flexVDI Suite, that gives flexibility to to the way that users connect to their Guests.

Its basic functions are:

When using a flexVDI Gateway, the schema looks like this:

Usually, the flexVDI Gateway runs on one a flexVDI Host, but it can run on a separate machine too. Also, several flexVDI Gateways can be installed if needed, which gives a schema like this: