Skip to content

Virtualisointi EQU virtualization

Random ramblings from the world of virtualization and then maybe some other things as well

Okay, here’s a pet peeve of mine and I cannot resist of writing about it.

Occasionally I see a phenomena of trying to do all and everything with a single product, as if expecting one technology to be a silver bullet that magically resolves all the problems that are for some purpose tied together to produce a whole. This is a problem that plagues especially [managed] service providers or organizations offering paid-for service to multiple customers. 

The usual flow of reasoning in these situations goes somewhat like this:

- Does it do foo and bar, which – incidentally - are the main things we want it to do?

- It does? Okay, that’s good but then we would expect it to do quux and xyzzy, which – in no way, btw - relate to the core things that your product does but needs to be done within the same system anyhow.

- It doesn’t do those? Oh, that’s too bad, then it cannot be any good at all.

And herein lies the problem; these people are not willing to embrace the idea of choosing the best products – multiple products if needed to - for the job, each one focusing on their forte. Yes, this could and will mean integration to some extent, but the end-result surely is better overall solution than doing with just one product that tries to do everything but does all those parts little bit badly. Which is, btw, somewhat similiar to UNIX ideology of small little utilities building up larger wholes instead of single monolithic systems.. And from the competitive point of view, let’s not forget that if you add your own special “spice” by actually developing some of that glue that holds everything together, as opposed to doing integration purely with the interoperability capabilities of the products used, you are doing something that no competitor too can readily buy off the shelf.

In keeping with the spirit of this site, let’s take a simplified example from the one of latest trends in virtualization: providing desktops (VDI) to customers as a service (DaaS as some call it) from the datacenter.

In the typical (or should I say more realistic) desktops as a service scenario, there’s multiple components involved: brokers, hypervisors, storage optimization, management layers, automation, self-automation, protocols, billing, integration, web portals, maybe integration APIs exposed etc. Expecting one product, or even only couple of products, to actually do all of these is simply a pipe dream. Many of the different aspects mentioned above are completely and utterly separate and distinct concepts that no one company can really (realistically) be best at, so excepting one company to build and provide a such technological whole is like expecting a miracle to happen.

Yes, maybe I’m stating the obvious here, but I have actually seen these sort of illusions where one solution is expected to solve every demand there is to a complete system, not really stepping back and looking what parts can be lifted from the different vendors and technologies.

And yes, more often than not these companies also might have “hidden” ties to certain vendors or technologies that they have decided to keep or favor and so, little bit artificially, other technologies are unfairly looked at and maybe discarded for not a very valid reason. Existing investment is a valid argument for some cases, but it should not be show-stopper if you really aim to provide something completely new in any case. Competetive advantage demands agility to switch and move, if necessary!

There’s no silver bullet, you know?

-Kalle

As the upcoming App-V 4.6 now supports x64 systems (along with 64-bit apps) so new OSVALUEs were in order. These are the new values for x64 OSes (existing – old - ones are for 32-bit versions):

  • WinXP64
  • WinVista64
  • Win764
  • Win2003TS64
  • Win2008TS64
  • Win2008R2TS64

Speaking of OSVALUEs, it should be noted that no longer separate values exists for both “regular” server and terminal services. From now on, only one value maps for server OSes and that’s for terminal server (understandably so as not many people ran App-V client on regular servers and also when considering licensing nowadays, that’s not really even doable). For 2008 R2, only 64-bit value is defined.

-Kalle

Quest just recently released new 6.2 version upgrade to their vWorkspace product suite.

New version adds some more rapid deployment of VDI instances, but only when using VMware as virtualization platform and NetApp FlexClone as a storage. Hopefully similiar features will start appearing in Hyper-V’s side of the fence, which is still little bit lacking behind VMware in features being offered/supported through vWorkspace UI. Of course, this is most likely due to differences of underlying technologies, but hey! it would be nice to have e.g. sysprep options offered directly from the vWorkspace for Hyper-V/SCVMM as well..

Maybe more universally appliable enhancements in 6.2 releases are ones in EOP however. There is a new/rewritten graphics acceleration functionality that moved things from user- to kernel-mode and should also provide more higher-quality compression, which is of course very user subjective as things compressed with JPEG usually are. But should be better anyhow.

Also in the EOPs enhancements, there’s support for more oddball multi-monitor resolution/orientation configurations and some improvements on universal USB redirection. Which, IMHO, can never be “good enough” ;-)

The updated version is downloadable, as always, from the http://www.vworkspace.com/ website, after you have registered an account for yourself. Full features, but time-limited.

-Kalle

Sorry, this entry is only available in Suomi.

This is new becoming for the virtualisointi.fi, in more than one way.

In the first ever version, the site was available in more than one language. Then, after a while, when switching to dasBlog -engine, this capability was lost (for good reason) and now with Wordpress I decided to resurrect it again. So here we go, hopefully there’s going to be posts in both or one of the languages depending on the topic..

Oh, and speaking of virtualization which is kind of topic for this whole site: my new Wordpress engine is happily running on top of Linux VM running inside the Microsoft Hyper-V. Yes, it’s a second-class citizen in Hyper-V, but it’s working great thanks to kindly folks at microsoft.beta.windowsserver.hyper-v.linux -newsgroup providing pre-built CentOS VHDs.. If you’re interested in it, I belive that the Linux Integration Components -connection is available for all to join at Microsoft’s Connect -website.

-Kalle