Security in the cloud and the virtual environment is ‘all about the data’ and not specifically about any other subsystem. It is about the data. As such the data has something it knows (the contents of the data), something it is (its signature), and something it has (its digital rights) and since it has these three elements, the data has all it has identity. However, protecting the data requires us to put things between the data and the real world such as firewalls, and complex role based access controls, as well as methods to replicate the data to other locations in a non-intrusive mechanism. The goal to such replication could be to ensure multiple sites have the same data (such as a hot-site) or to have the data available in another locations in case of disaster. In addition, such data must maintain its identity.
Articles Tagged with Hyper-V
As a delegate for Tech Field Day 6 in Boston, I was introduced to SRM Replication as well as ZeRTO a third party replication tool. They seem to be as different as night and day but are they? Both work within the vSphere environment to replicate virtual disks regardless of storage type, and apparently hook into the same location within VMware’s API stack. This shows a maturity of VMware’s API stack that until now has been unknown and secret. In this one area, Microsoft Hyper-V is beating VMware vSphere: The availability of well known APIs that are easy for Third Parties to use. I now see a change in VMware’s behavior, can they continue this growth?
As a delegate for Tech Field Day 6 in Boston, I was introduced to many third party management tools. In the past I have been given briefings as well on various VMware, Hyper-V, and Citrix Xen Management Tools as well. Many of these tools are marketed directly for use by the administrator, but they have the tools can be used by more than the administrator. These tools should be marketed to management, administrators, as well as the network operations center (NOC). The NOC you say, why should they see the details of my environment? The NOC should not, but they should be able to tell when systems are in failure states outside of the hardware. Only a few tools can be used this way today. The sooner administrators get the word of a problem the sooner it can be fixed. The NOC is the one place that centralizes all monitoring whether it is for security or health of your virtual and cloud environments.
Virsto has announced they have secured $12 million in Series B venture capital funding. In addition, Virsto has revealed it has acquired EvoStor, a company specializing in storage virtualization technology for VMware environments.
Virsto developed the first hypervisor-based storage solution built for virtual machines which we’ve spoken about in the past. At present, Virsto’s solution is for Microsoft Hyper-V implementations only. Yet Khaled Nasr, partner at InterWest who joins Virsto’s board of directors, is obviously excited about the prospect of not only expanding Virtso’s potential for Microsoft Hyper-V, but developing new markets:
VMware and Microsoft approach the Small to Medium companies quite differently, but which product to buy often depends on your business needs vs cost of the products. However, there needs to be at least one major distinction: SMB vs SME.
The Small to Medium Business (SMB) is quite a bit different than the growing number of Small to Medium Enterprises (SME), and VMware knows this does Microsoft or Citrix?
On October 22nd, Microsoft announced that it has partnered with Cloud.com to provide integration and support of Windows Server 2008 R2 Hyper-V to the OpenStack project. The announcement caused a great deal of interest here at the Virtualization Practice, as it signals an unexpected willingness on Microsoft’s part to pursue interoperability at the IaaS layer, allowing users to break out of the Hyper-v stack, whilst still retaining Hyper-v at the bottom. The fact this announcement came from Microsoft (not Cloud.com, Rackspace or OpenStack) seems to signal the seriousness of the intent.
In practical terms this means that Cloud.com puts a Hypervisor Abstraction Layer into the bottom of the OpenStack compute platform (Nova), and binds Hyper-V into that, to allow images to be deployed to and controlled on Hyper-V from OpenStack, using tooling that speaks one or other of the two OpenStack APIs (Native or Amazon EC2). Technically it is not a major step because although the initial version of Nova targeted libvirt and thereby Xen, KVM and Qemu, Citrix had already succceeded in providing a hypervisor abstraction layer in OpenStack for XenServer.