Does RES Software portfolio update deliver DaaS?

If DaaS provider is only focused on hosting a virtual desktop they are failing you. If you only provide a desktop to your customers – you will annoy them. You don’t deliver “a desktop” you deliver “a workspace”. RES Software have recently released a number of updates, new releases and patents that help put the Service into desktop-as-a-service. When considering your own enterprise desktop environment, or enhancing your DaaS offering – what tools are you using to automate delivery? Does the updated RES Software portfolio assist?

OpenShift — Pricing and Comparison to AWS

On June 26th,Red Hat announced a new version of OpenShift, and pricing for a future production offering (some time this year). You still can’t buy it but if you were able to buy it you’d know exactly how much it could cost – at least if you could work out what a “gear” is. Pricing allows us to start to compare it more meaningfully with other offerings. However rather than comparing with another PaaS offering, we think most people will be actually considering IaaS as an alternative, so we are going to do that comparison instead.

Enter the FrankenCloud: Or Do we really care about the Hypervisor?

There has been quite a lot of twitter traffic about the FrankenCloud recently: A cloud with more than one type of hypervisor underneath it. One example, is to build a cloud using Hyper-V three and vSphere, both managed through Microsoft System Center. Another example, is to build a cloud using Hyper-V, KVM, and vSphere all managed through HotLink. But is this a desired cloud topology?

News: Piston Cloud and Gridcentric Partner to Deliver First Commercial OpenStack VDI Platform

Piston Cloud Computing raised a few eyebrows on Tuesday with the announcement that it was extending its Piston Enterprise OS (PentOS) to provide a platform for hosting virtual desktops (VDI) through an exclusive licensing deal with Toronto-based Gridcentric for its innovative Virtual Memory Streaming (VMS) technology.

Unified Computing: Collective Group or Single Responsibility

I have spent a great deal of time lately working with the Cisco Unified Computing System (UCS). This computing platform is really quite impressive with its power and flexibility, but my expectations about the platform have really changed since I completed the UCS training. During the training classes that I attended, both the design and install courses emphasized that the Cisco UCS platform would be a collaborative platform that would bring the different groups like Storage, Network, and Server each working their own functional area of responsibility within UCS based on role permissions. That sounded great. The network team can create and trunk the VLANS and the storage team could add the boot targets as well as assign the LUNS. This platform is a true collective effort by all teams right?

Defense in Depth: Firewalls within the Virtual Environment

The 6/14 Virtualization Security Podcast we spoke about firewall placement within the virtual environment as well as storage based defense in depth. While we covered Encryption on the 5/31 podcast, in the 6/14 podcast we covered other measures when dealing with storage (which will be part of a followup post). This conversation was slightly different than all other firewall discussions, as it was about migrating from a physical environment to a virtual environment, and keeping the same firewall placements. Spurred by a customer, we sought to come to a set of guidelines to follow for defense in depth within the virtual as well as physical and hybrid cloud environments.