The Virtualization Practice

Storage Networking

Storage Networking focuses upon virtualizing the storage and the SAN while collapsing and simplifying the management and performance of storage. This includes the role of storage virtualization in the Software Defined Data Center, and the comparison of pooled local storage options with traditional network attached storage (NAS) and fiber channel attached storage. Covered vendors include VMware, EMC, IBM, Dell, HP, Cisco, Tintri, and Nutanix.

IO Virtualization Approaches: VMworld 2010 Review

There seem to be three styles of IO Virtualization (IOV) taking place within the virtual environment. At VMworld, the IO Virtualization companies were out and talking to people about their wares, products, and approaches to IO Virtualization. These three methods are:

* Converged Network Adapters used within Cisco UCS, HP Matrix, etc.
* Attached IOV top of rack devices such as the Xsigo Device
* PCIe Extenders

Each of these provide unique benefits to your virtual environment but which to use? First, we need to know what each of these approaches brings to the table.

The Consolidated server stack has been the big items over the last year using converged network adapters, blades, and integrated storage that is designed around providing an order-able element that is a single SKU that provides enough resources for a set number of VMs. Currently the VCE colition has the VBlock which combines VMware, Cisco, and EMC products into a single stack. HP has its Matrix stack. But where is IBM’s and Dell’s stacks. Could the acquisition of 3Par be the beginning of a integrated stack play from Dell?

Who’s Who in Virtualization Management

Virtualizing business critical systems requires that a layer of virtualization management solutions be added to the virtualization platform. Virtualization management solutions in the areas of virtualization security, virtualization configuration management, virtualization service and capacity management, virtualization service and capacity management, virtualization provisioning and lifecycle management and backup and recovery should be added to the platform.

vSphere 4.1 Released – More Dynamic Resource Load Balancing

With the release of vSphere 4.1, VMware has added to their Dynamic Resource Load Balancing (DRLB) suite of tools that I hinted at in my post on Dynamic Resource Load Balancing that I wrote last week as well as providing new memory over commit and other functionality. In essence, vSphere 4.1 is more than a point release, this update includes many features that aid in security, reliability, and is a direct response to customer requests.

I just finished writing all the content for my next book entitled VMware ESX and ESXi in the Enterprise: Planning Deployment of Virtualization Servers (2nd Edition) which continues the discussion on Dynamic Resource Load Balancing (DRLB). DRLB is the balancing of virtualized workloads across all hosts within a cluster of virtualization hosts without human intervention. This is the ultimate goal of automation with respect to virtualization and therefore the cloud. In effect, with DRLB the virtualization administrators job has been simplified to configuration and trouble shooting leaving the virtual environment to load balance work loads on its own.

Virtualizing Business Critical Apps – The Value of Real Time SAN Data

Supporting Tier 1 applications on VMware vSphere requires real time and granular response time and latency instrumentation of the virtual and physical infrastructure. Virtual Instruments Virtual Wisdom complements the instrumentation provided by VMware by providing individual transaction level visibility into the SAN layer of the virtual infrastructure.

There is nothing like fully understanding the protections inherent within your vNetwork and the Roles and Permissions you can set within the virtualization management tool suites to ensure your vNetwork is secured, audited, and monitored for issues. Just like you do now within the pNetwork. Unlike the pNetwork, the vNetwork provides a certain amount of introspection and capability that is missing from a pNetwork, and this will also help with security.

Due to what I stated during GestaltIT’s TechFieldDay, I was invited with Bas Raayman and others to discuss Secure Multi-Tenancy (SMT) in more detail with Chuck Hollis at EMC World. In addition, during one of the Keynotes SMT was renamed from Secure Multi-Tenancy to Simple Multi-Tenancy. The current Cisco VMware Netapp solution is plainly not secure. During the TechFieldDay at Cisco, Cisco even claimed “we did not think about security” when designing the initial solution. Cisco is worried about Quality of Service, I.E. Bandwidth through out the system to the disk. Furthermore, their definition of ‘Tenant’ was quite a bit different than my own. So we should first start off by defining Tenant.