Feeds

Virtual management - a lesson from history

Wetware still required

  • alert
  • submit to reddit

Security for virtualized datacentres

Blog I have worked with many different virtualisation platforms, from Microsoft’s early attempts with Virtual Server 2005 to the latest VMWare, Hyper-V, KVM and Xen offerings. I have taken the time to play with the management software offered by these vendors, and even a few of the third-party stuff. Depending on your specific needs, the higher-level management tools can either make your life easier or far more complicated. They will most assuredly make it more expensive.

The most obvious problem is that of keeping all our eggs in one basket. This is tough to beat. In some instances (such as VDI) it may well be a perfectly acceptable risk to run a collection of virtual machines on a single physical server. The downtime that occurs in the rare event that the server suffers a hardware failure can be considered acceptable, and those VMs can then be spun up elsewhere. As soon as you step away from systems that can afford brief outages and start looking at the virtualisation of critical systems, everything gets a lot more complicated.

As a systems administrator, it’s part of my job to look at the state of IT today and the history of IT in general, and from this extrapolate a prediction of where it is going. Buying most hardware is a fairly short-term bit of foresight; on average, you’ll be replacing your servers and desktops every four years. Software requires a lot more research, both into the capabilities of the product, but the viability of the supplier. Once locked into a given operating system or application, exiting that ecosystem is not easy. Whether you are trying to hop software vendors to a superior competitor or because the vendor has failed or exited the market, software changes tend to present far greater difficulty than hardware changes.

The lessons I have learned trying to solve power management issues on my network have brought this required bit of professional prognostication to the fore. I have long maintained that the IT landscape is in the midst of collapsing into a relatively small number of megacoporations. While I can’t possibly say how that will shake out, it will make for an interesting decade wherein everything from storage arrays to operating systems and even cloud services are commoditised to the point of being indistinguishable. This process is generally good for consumers; we get more choice for a lower cost. What it always brings with it in IT are some desperate endgame plays and strategic alliances. Everyone starts pairing off, and the game becomes one of locking your customers into your particular vertical stack of hardware, hypervisor, operating system, management applications and services. Through this integration it becomes nearly impossible to ever leave.

The death of the PC has been predicted many times before, and I certainly am not going to predict it here. There will likely always be a need for general purpose desktops and servers, but I feel that the days where they are the norm rather than the exception will soon be behind us. The reason for this is not politics or money, or even the rise of the iPad. The reason is that Intel has spent the greater part of the aughties stymied by the laws of physics.

Somewhere in the past decade, the ability to keep increasing the speed of a single core hit a wall. Intel loves to tell anyone that will listen that multi-core is the future, and programmers just need to catch up with the hardware. Programmers respond by politely informing the semiconductor behemoth that they are very sorry, however some workloads can’t be parallelised. This dance has gone on for years now, and very little progress has been made. In an attempt to continually increase the price/performance/watt values of our networks, virtualisation has bought us time. It needs to be borne in mind though that it isn’t an endgame solution, but rather a stop-gap measure. Without that single-thread performance, we are limited to only being able to grow workloads that can be parallelised. Virtual Desktop Infrastructure (VDI) is one of them. So low are the requirements of most users today that many small, simple, non-critical workloads can be shoved into one of these multi-core monstrosities without any noticeable compromises.

Providing a secure and efficient Helpdesk

More from The Register

next story
Docker's app containers are coming to Windows Server, says Microsoft
MS chases app deployment speeds already enjoyed by Linux devs
IBM storage revenues sink: 'We are disappointed,' says CEO
Time to put the storage biz up for sale?
'Hmm, why CAN'T I run a water pipe through that rack of media servers?'
Leaving Las Vegas for Armenia kludging and Dubai dune bashing
Facebook slurps 'paste sites' for STOLEN passwords, sprinkles on hash and salt
Zuck's ad empire DOESN'T see details in plain text. Phew!
Windows 10: Forget Cloudobile, put Security and Privacy First
But - dammit - It would be insane to say 'don't collect, because NSA'
Symantec backs out of Backup Exec: Plans to can appliance in Jan
Will still provide support to existing customers
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Why and how to choose the right cloud vendor
The benefits of cloud-based storage in your processes. Eliminate onsite, disk-based backup and archiving in favor of cloud-based data protection.
Three 1TB solid state scorchers up for grabs
Big SSDs can be expensive but think big and think free because you could be the lucky winner of one of three 1TB Samsung SSD 840 EVO drives that we’re giving away worth over £300 apiece.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.