

Well, I guess the word is out on twitter (not that I was given forewarning of the announcement!) but in case you haven’t heard yet – VMware have in partnership with Pearson established their own VMware Press. I’m really pleased they have taken this step – it was something I suggested to VMware back in 2005/6 but at the time there seemed little enthusiasm. I guess that’s kind of understandable – after all VMware is an ISV, not publisher. But time and tide have moved on, and I think VMware realise that there is a major benefit to be had in engaging with the small band of merry authors – of which I am part.
So the next VMware Site Recovery Manager book will be the first to be release for the first time through a formal publisher. Previous editions were self-published by myself, and distributed by LULU and Amazon – and later still in a PDF format. It’s great privilege to be selected this way, and I believe is recognition of my long-term commitment to writing books/content/guides on VMware technologies for which I’ve become international renowned (time to blow my own trumpet, and know that isn’t euphemism) .
So along side including even more storage vendors – by adding Dell Equallogic to the book – there will be detailed coverage of all the new major features which I’m sure will rock your world. Make no bones about it the next release of VMware SRM is going to be significant uplift compared to the 1.0/4.0/4.1 releases. With many of the major roadblocks to adoption being elevated, or even removed altogether.
The other big change is that I will be working with VMware much more closely than ever before – and believe me I close before hand. But this time around VMware themselves have direct stake in validating and checking the content. So I’m hoping that my contacts with VMware will allow this time around a more “under the covers” approach to be taken than was previously possible…
So where do I go after this book. Well, I have big plans for some kind of “cloud stack” book that encompasses understanding how the layers of stack – OEM, ESX, vSphere, vCloud Director and other VMware virtualization management products (vCHBS, AppSpeed, ConfigControl and so on) interact and work with each other. The way I’m looking at it is a bit like this. In the mid-90′s I forage a career based on knowing Windows NT4, and essentially teaching all the “core” operating systems functionality. As time wore on that wasn’t enough – and my students and peer group demand more – until the OS almost disappeared – so focused were we on Exchange 5.5/IIS/Citrix or what ever platform was running. That’s the direction I need to go in, and think the vCommunity needs to go in. Never fear I remain equally committed to understanding that core platform of ESX/vCenter – vSphere if you like. But its time to move up the stack and into new and virgin territory.