Like all good remakes this is best served cold. After an hiatus of several months The Virutalization Practice are pleased to bring back to life the Virtual Thoughts podcast. The subject for the first program is as follows:-
Is the Hypervisor being pushed into hardware, why/why not?
So add the time and date into your calendar and join the Analysts of the The Virtualization Practice for an hour of thoughts and maybe even a little bit of insight into the dark arts that is the virtualisation world
That is Tuesday the 29th June 2010 @ 7:00pm (BST)that is 2:00pm EST and 11:00am PST
Hope to see you there!
With the advent of existing VMsafe products from Altor Networks, Reflex Systems, and ones on the horizon from Trend Micro and others in the security space, all administrators should have a clear understanding of how they work under the covers. Where does VMsafe appear within the stack? Is VMsafe on the incoming physical NICs, within the vSwitch, portgroups, or before or after the vNIC? Can we expect the other aspects of VMsafe to be the same? While I was discussing VMsafe with the vendors, VMware was also going around and talking to all the VMsafe vendors for VMware TV shots.
Overall VMworld 2009 displayed a coming of age; an ecosystem maturity for all vendors, this was evident to all within the category of business continuity and disaster recovery, specifically the many forms of backup creation. Veeam, Vizioncore, and PhD Virtual all showed their latest released products as well as demoing future products that will integrate with VMware vSphere at a much deeper levels than previously available, a’la the VMware vStorage API. All vendors talked about expanding their product support into both Microsoft Hyper-V and Citrix XenServer. This space has become so important that even the traditional backup vendors such as Symantec (BackupExec)and HP (DataProtector) are getting into the act. This demostrates a market matruity in the ecosystem not seen at last years VMworld.
Reflex Systems announced today that they have the first VMware VMsafe Certification for their Reflex VMC product. This announcement brings two things to light. The first is that VMware has made a very smart move to certify VMsafe drivers for their hypervisor, which is a much needed step I have written about previously. The second is that Reflex Systems has been working through the process with VMware and working out the bugs in the process as well. This will help other vendors and VMware. Kudos to Reflex Systems!
But what does being VMsafe Certfied imply?
There have been several interesting posts in the blogosphere about virtualization security and how to measure it. Specifically, the discussions are really about the size of the hypervisor footprint or about the size of patches. But hypervisor footprints from a security perspective are neither of these. The concern when dealing with hypervisor security is about Risk, not about the size of the hypervisor or the size of a patch it is purely about the Risks associated with the hypervisor in terms if confidentiality, availability, and integrity. Vendors who claim that security is proportional to the size (in GBs) of the hypervisor footprint are spreading FUD.
I have been preparing my virtual environment for a VMware vSphere upgrade. Specifically I have been going over my existing hardware with an eye towards running all aspects of vSphere including VMware Fault Tolerance (FT), NPIV, Cisco Nexus 1000V, and well everything.
But first a little about my environment. It is not all that big. Currently it has 2 DL380 G5s with dual quad port E5345 CPUs, 16GBs of memory, 2 146GB SAS drives, dual port Intel GigE dual port adapters, Emulex Dual Port FC-HBAs. In addition, there are 2 DL380 G3s both with 6GBs of memory and 6 146GB drives. One of the DL380 G3s is my VMware vCenter Server and Backup Server attached to a USB DISC BluSafe of which I blogged about previously. The other DL380 G3 is a test box for the virtual environment.
So what will going to vSphere entail?