It's been such a strange week. On Tuesday I headed to VMware HQ, Palo Alto, to conduct multiple VCDX interviews. Actually this was the first time we had people from outside of VMware presenting and defending. Of course I can't comment on the outcome, but I must say that overall I was pleased… very pleased about the level of expertise that was shown. During the week I also met several people I wanted to for a long time, including Mr Planet V12n himself John Troyer. It was a great week and there's another great week ahead of us: VMworld. That is not what this post is about. This post is about this weeks top 5, euuuh make it 3 cause 99% of the article were news articles this week, here we go:
- Eric Gray – The VMware ESXi 4 64MB Hypervisor Challenge
In a previous article, I answered the question: If VMware ESXi 4 is so small, why is it so big? It’s quite clear now that the disk footprint of VMware ESXi 4 is less than 60MB. But to really drive the point home, I wanted to demonstrate that VMware ESXi 4 could boot and run from a tiny 64MB flash device, so I asked Olivier Cremel, the inventor of ESXi, if that was feasible. He said it was — and gave me advice on how to set it up. This article shows you how. - Scott Lowe – Thinking Out Loud: HP Flex-10 Design Considerations
The number of uplinks doesn’t matter anymore, because bandwidth is
controlled in the Flex-10 configuration. You want 1.5Gbps for VMotion?
Fine, no problem. You want 500Mbps for the Service Console? Fine, no
problem. You want 8Gbps for IP-based storage traffic? Fine, no problem.
As long as it all adds up to 10Gbps, architects can subdivide the
bandwidth however they desire. So the number of uplinks, from a
bandwidth perspective, is no longer applicable. - Chad Sakac – Important note for all EMC CLARiiON Customers using iSCSI and vSphere
You can ABSOLUTELY drive simultaneous interfaces against a single
target when using NMP Round Robin or PowerPath/VE and an EMC CLARiiON
and the vSphere 4 software initiator. BUT there is one CLARiiON issue
(this is really a bug, IMHO – and one that we’re fixing, so the the
below is a workaround – but a workaround that you could leave for as
long as you want – there’s not really a general downside).
