We're all familiar with the concept of a virtual server. However, when planning and implementing a virtualisation project, it's not just the servers that can be and should be virtualised – it's the network too. Among the first differences that you'll notice when setting up a virtual machine (VM) is the network setup. Naturally, …
I for one...
... am holding out for the virtual ASICs obviously necessary to make this thing fly with any speed.
Hm? The virtual one, thanks. It's a Kaiser's Original[tm] too, not some cheap knockoff, you know.
Long Live the Binary Raj and AIMonarchs of the Zen.
"In an ideal world, the datacentre's network hardware infrastructure should be required to change as little as possible on the introduction of virtualisation, apart perhaps from an increased emphasis on the reliability aspects, given the number of servers dependent on each host although clearly some change will be needed. But at the higher layers, the key is to automate as much as possible, aiming for the holy grail of the datacentre as a unified computing fabric." ..... Manek Dubash
Quite so, Manek Dubash, in an ideal world would it be so, provided the datacentre's network hardware infrastructure is programmed correctly and/or run by top class virtual machine hierarchy specialists.
I really wish there was a simple cookbook for those of us not steeped in this.
- Breaking news: Google exec veep in terrifying SKY PLUNGE DRAMA
- Geek's Guide to Britain Kingston's aviation empire: From industry firsts to Airfix heroes
- Analysis Happy 2nd birthday, Windows 8 and Surface: Anatomy of a disaster
- Google CEO Larry Page gives Sundar Pichai keys to the kingdom
- Something for the Weekend, Sir? SKYPE has the HOTS for my NAKED WIFE