This Quick Start guide will help you deploy Flexiant Cloud Orchestrator with VMware vSphere. For KVM/Xen 4/Hyper-V please see the Quick Start guides specific to these hypervisors. We recommend you have read and understood the following pre-requisite documents before continuing:

Providing these requirements have been met you are ready to begin your installation. 


At this stage all hardware should be racked and ready to be configured. The first step is configuring the networking between the internal Flexiant Cloud Orchestrator management server, vSphere, Router Nodes and your existing upstream router. For a detailed description please see the following guide:

Flexiant Cloud Orchestrator by default supports static routing through the use of Automatic Router Configuration (or ARC). This is suitable for small environments.

The major advantage of static routing is that the configuration on your upstream router is very simple indeed.  

For each IP address pool you have, you must create an 'interface route' or 'device route' on your upstream router pointing at the interface to which the nodes are attached. This will be the interface carrying the PVIP network and if using defaults will have the IP address

Instructions for doing this are simple but vary depending on your choice of router, various examples are listed here, but please contact your network admin if you are not sure.


When integrating Flexiant Cloud Orchestrator with VMware's vSphere, Flexiant Cloud Orchestrator will use vSphere's storage integration.

vSphere supports a wide range of storage devices. All that is necessary to achieve correct physical configuration is to configure the storage such that it presents a storage pool under VMware which is accessible to all nodes within the cluster.

Please refer to vSphere's documentation for its supported storage criteria.

vSphere Configuration

An example vSphere configuration is as follows:

A typical (default) networking configuration should look like this:

Ensure that the local store is removed if this exists.

The management IP address of each ESXi Host, by default, should start at and increment by 1 for each host. This should be on the same LAN as the node interface of the Flexiant Cloud Orchestrator management server (by default its 2nd NIC). The vSphere server itself should have the IP address on its management interface and also be part of this node LAN.

You may name the Datacenter and Cluster whatever you wish but the names are important and will be used when configuring Flexiant Cloud Orchestrator. You may have as few or many clusters and hosts as you wish, but at least one cluster with one host. There can be as many datastores per cluster as you require, however nodes within the cluster must have access to all datastores they might use to store VM disks on. Flexiant Cloud Orchestrator will move disks around datastores as required.

By default, Flexiant Cloud Orchestrator expects a vSphere Standard Switch named 'vSwitch1' for the VM 'public' network (the network to connect to the Internet on). This can be changed by adding any of the following options to /etc/extility/cluster.cfg.

Once added or modified you will need to run build-config to apply the changes.

PVIP Network

If you wish to use PVIP networking then you will need to add a vSwitch2 network with no network adapters. This should contain a Host Switch of Virtual Machine type. It should have access to all VLAN IDs.

Console Service

For the integrated console service we also need to allow VNC through the firewall for each ESXi host, to do this you need to enable 'gdbserver' in the Security Profile, Firewall Properties section of each ESXi host within vSphere.