Page tree
Skip to end of metadata
Go to start of metadata


We recommend these key decisions are made before installing Flexiant Cloud Orchestrator. Making these decisions first will ease the deployment and ensure all requirements have been considered. 

Some of these key points are business decisions and others are technical requirements. 


You will need to decide whether your installation will be branded with your company details, logo and support links. You will need to make a similar decision on behalf of your resellers and partners. For instructions on how you can brand the control panels, see Branding and White Labelling.

Please speak to our sales department if you require additional assistance. 


The hypervisor that your platform uses will affect your costs, and affect the choice of which images that your customers can use. Ensure you are aware of the benefits of each hypervisor before installing and creating images on the platform. 

Customer Networking Modes

Flexiant Cloud Orchestrator supports a variety of networking modes. Two of these give access to the public internet (Public VLAN mode and PVIP). Both of these modes are available with all hypervisors. Deciding which of these (if any) you wish to offer before deployment will affect the network configuration of your routers and switches. Deciding this before installation means this configuration can be applied before installation of the software, thus saving engineer time.


Flexiant Cloud Orchestrator is a software stack deployed on top of a stock Ubuntu 14.04 LTS installation. It can thus be backed up by any Ubuntu compatible backup solution. It is worth considering what software you are going to use for backups as well as reading over our Backup guide before deployment as this may affect how your rack and switching configuration is designed.

Failover / High Availability

Flexiant Cloud Orchestrator can be deployed in a fail over or high availability configuration. Deciding if you require HA before deploying a live platform is essential. Our Professional Services department can help you deploy various HA configurations. Please contact Sales for further information. 


As the number of VMs on your platform increases, so will the number of physical hypervisor nodes required. You must consider the consequent increased demand for rack space, power, cooling, switch ports and switching capacity. Ensuring your deployment can scale at the outset is imperative, if you wish to add capacity without downtime in the future.

Routing Protocol

Flexiant Cloud Orchestrator compute nodes need a way to announce allocated subnets to the upstream router. This is done by either static routing, OSPF or BGP. Deciding on a routing protocol is essential as it affects the configuration of the upstream router. We recommend static routing for smaller configurations, and BGP (if your router supports it) for larger ones. See Managing Routing Protocols for more details.

  • No labels