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

Overview

This Quick Start guide will help you deploy Flexiant Cloud Orchestrator with Hyper-V. 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. 

Networking

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, hypervisor/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 10.157.192.1.

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.

Storage

When integrating Flexiant Cloud Orchestrator with Hyper-V, Flexiant Cloud Orchestrator will use Hyper-V's storage integration, Windows Server 2012. This requires an SMB3 share, which can be obtained either directly from an SMB3 compatible SAN or equivalent, or through an SMB3 Windows fileserver in your domain, which acts as an intermediary between a storage solution and the rest of the domain. If you are using an intermediary fileserver, you must be able to mount the storage device as an SMB3 share on the intermediary fileserver. The intermediary fileserver is configured after you install Flexiant Cloud Orchestrator.

Please refer to Hyper-V's documentation for more details on its supported storage criteria.

  • No labels