Today, we announced we will be delivering VM networking support for Hyper-V in Microsoft’s forthcoming Windows 8. Specifically, we are working with Microsoft to deliver integrated support for the Nexus 1000V and VM-FEX technology in their next generation server platform, thus extending the benefits customers have seen from both these technologies to another server/hypervisor environment. For more info, check out the announcement and this brief and this Q&A.
With this latest announcement, we offer (or will offer) Nexus 1000V functionality for VMware vSphere and Microsoft Hyper-V as well as VM-FEX support for those two hypervisors and RedHat Enterprise Virtualization. For folks building out virtualization architectures and cloud environments, we think this is a key benefit, since it maintains their choice and flexibility and allows them to build out hyper-visor agnostic infrastructure that delivers consistent features and functionality.
So, that’s about it for now. Stay tuned to this space and we’ll keep you apprised as things progress.
With the opening of the new Cisco Datacenter in RTP, I thought it would be cool to reach out to a few of the guys responsible for the design and ask them a few questions. So, I got together with Jag Kahlon (Cisco IT Architect) and John Banner (Cisco IT Network Engineer) for a quick chat.
Me: What were the primary objectives for the new datacenter?
Last week in part 1 of this blog, I used the analogy of the Winchester House to start the discussion on why an architecture-led approach should be a strategic imperative for your IT architectural evolution and transformation. In this part 2, I’ll give some industry data points, and use some examples of the complex network-based solutions you are implementing, to illustrate why you should adopt the architectural-led approach over the point product minefield.
The Winchester House - A Case for Architectural-Led Evolution and Transformation