Educational Episodes: Hyperconverged Infrastructure (HCI)

Hyper-Converged Hyper-V solution using Starwind across two buildings When I first started working for my current employer back in 2013 one of the first projects was to address business continuity concerns. The Brief was very… brief… no details other than “we have another building on the site which is linked by fibre optic, if our current physical servers had a problem we want to be back up and running in under 4 hours”. No guidance on what we should use or how to accomplish this, so off I went in search for solutions.

This is a follow up post on a post we have done previously – How To Convert EXE To MSI Package In 5 Easy Steps – where we created a MSI package for an application that did not exists as MSI, so we had no choice. We used third party software to repackage our application.

When a large Hyper-V infrastructure is deployed, often Virtual Machine Manager (VMM) is installed. It enables to deploy logical switches which are mainly VM Switches and virtual network adapters for Live-Migration, Backup, heartbeat, storage or management purposes. However small or medium business doesn’t necessarily implement VMM because it is expensive or not well-known. Even if you don’t use VMM, you can deploy consistency VM Switches on several Hyper-V by using PowerShell. This topic aims to show you how to deploy VM Switches and virtual network adapters by using PowerShell. In this way you will be able to make a standard script to configure your Hyper-V hosts.

The hyperconverged infrastructure appliance market (HCIA) is growing fast and hardware competitors are using Dell, HP, SuperMicro and other servers and not Cisco’s UCS hardware. EMC only covers a portion of the market so Cisco should address the rest in order to both preserve its current UCS market share and grow it further.

During 2015 Backblaze data centre has expanded from 39’690 hard drives in 882 Backblaze Storage Pods to 56’224 drives in 1’249 Pods, which makes about 65 Petabytes of additional space.

Hyper-converged infrastructure, when we started to hear about it last year, was simply an “appliantization” of the architecture and technology of software-defined storage (SDS) technology running in concert with server virtualization technology. Appliantization means that the gear peddler was doing the heavy lift of pre-integrating server and storage hardware with hypervisor and SDS hardware so that the resulting kit would be pretty much plug-and-play.

For large Hyper-V infrastructure, IT people use often Virtual Machine Manager (VMM) to automate tasks as VM deployment. VMM provides profiles (hardware, operating system and application) and then we use these profiles to build a VM Template. Most of the time, a VM Template contains a VM hardware configuration and the OS configuration (join the domain, product key and so on). Then VMs are deployed from templates which decrease the time to deploy a working VM.

New Integrity MC990 X is the first server in a line conforming to the new naming convention, with ‘MC’ standing for ‘mission critical’ and ‘X’ standing for ‘Xeon’.It replaces the Proliant DL980 (‘DL’ – ‘density line’). The name changes are implemented in order to meet specific customer needs, e.g., high performance and cloud computing. HP will keep the Proliant name for low-end and mid-range servers, and also keep the BL (blade) designation.

On VMware Labs site you can read about new utilities which can simplify the management of VMware vSphere virtualization infrastructure. They help administrators to solve their everyday problems. The following list includes the tools with functions description.