VirtualBacon

Deploying the PernixData Management Server Virtual Appliance

If you have previously deployed PernixData FVP then you know how easy it already was to deploy the management server on a Windows server: deploy a 64 bit Windows server, have access to a SQL server to use to store the performance data, and that's it. Very simple and a no brainer for anyone who has installed pretty much any client-server application. The installation of the management server software itself takes only 5-10 minutes but it is common for people to spend an hour or so deploying the Windows VM, bringing it up to date with patches, installing SQL or creating database credentials, etc.

Well as of FVP 3.5 / Architect 1.1 the process is even easier with the introduction of a virtual appliance version of the management server. As a reminder no storage IO flows through this server as acceleration with FVP is completely transparent at the hypervisor level.

Note: The Windows version of the management server is still available for those who want to continue using that version but deployment with the new version is much faster as it includes the OS and database server within the appliance.

The steps for installing the new management server virtual appliance are:

  1. Deploy the OVA.
  2. Push the host extension (VIB) to the hosts within a vSphere cluster using VUM or command line if you prefer.

The deployment of the OVA takes about 3 minutes while the host extension installs are about 3-5 minutes per host. As the host install is a maintenance mode operation actual install time will depend on how long it takes to temporarily migrate VMs to other hosts.

Screenshots of the OVA deployment

Select the vSphere cluster where you want to deploy the virtual appliance and click on the File menu and select Deploy OVF Template...

FVP3.5_Deploy_OVF_Template

 

Select the OVA file that you downloaded from the PernixData Support Portal using your account:

FVP3.5_Select_OVA

Give the virtual appliance a name:

FVP3.5_Name_Appliance

Select the datastore to deploy the virtual appliance to:

FVP3.5_Deploy_OVF_Select_Datastore

Select the configuration size of the VM based on your environment size:

FVP3.5_Size_Config

Select the desired disk format (thin or thick):

FVP3.5_Deploy_OVF_Disk_Format

Configure the networking information for the appliance:

FVP3.5_Configure_Networking

Select the virtual network to use:

FVP3.5_Select_Network

Review the deployment summary:

FVP3.5_Deploy_OVF_Summary

Deploy VM:

FVP3.5_Deploying_Appliance

Once the virtual appliance is deployed power it on (unless you checked the box to power it on automatically) and confirm that it is up:

FVP3.5_Console_Initial

Log into the web interface at https://[ip address or DNS name]/config to complete the installation though the config UI:

FVP3.5_PernixMS_Config_Login

Enter the vCenter server information:

FVP3.5_PernixMS_Config_vCenter

Review network settings:

FVP3.5_PernixMS_Config_NetworkSettings

Enter Time Zone and NTP server information:

FVP3.5_PernixMS_Config_Time

Installation is complete and you can go to the PernixData Management Console to apply your license(s) and begin using FVP and/or Architect.

FVP3.5_PernixMS_Config_Complete

Service starts for the first time:

FVP3.5_PernixMS_Config_Starting_ServiceFront-End Login:

FVP3.5_PernixMS_Front_End_Login

 

It looks like a lot of steps but the entire process takes all of 3-4 minutes depending on the speed of your host and network to transfer the ova file!

For those of you who are deploying the FVP MS at customer sites you will be pleased that the time spent ensuring that the management server Windows and SQL pre-requisites is now gone. Deploy OVA. Patch hosts. About 4-5 minutes each (minus waiting for VM migrations). Done. 🙂

Video of the deployment:

Website Security Test