Firstly, this is not about the 1% associated with the Occupy WallSt campaign! As widely reported on Twitter and the blogosphere the 2012 vExpert program is up and running – I won’t go into the changes this year as there is plenty of coverage for that. In VMware’s own words;
The annual VMware vExpert title is given to individuals who have significantly contributed to the community of VMware users over the past year. The title is awarded to individuals (not employers) for their commitment to sharing their knowledge and passion for VMware technology above and beyond their job requirements.
Sounds great, let’s fill in that application form right? Before you apply have you ever paused to consider what is it you’re actually doing, and for whom? In an interesting article about ‘going social’ posted just a few weeks ago Dr Michael Hu talked about six myths companies believe are associated with a social strategy, one of which is the need to reach every customer to be effective. He refutes this, stating;
Instead, you need to discover the small number of “superfans” who want deeper engagement and then harness their enthusiasm to manage and strengthen other customer relationships on behalf of the brand. That’s the real power of community – you tend to the 1% who tend the other 99%.
That describes the vExpert in a nutshell - you are the 1%!
You could see this through cynical eyes as VMware using the community for their own benefit but like many of my peers I’ve been working in IT for well over a decade and virtualisation is the first time I’ve found a community that really benefits everyone involved. Maybe it’s the advent of social networking, maybe it’s the convergence of the various technologies or maybe it’s the time and effort expended by VMware (and geek herder extraordinaire @jtroyer) but for some reason it works where it never did before. I enjoy being part of the VMware community and I know it adds value for me (and therefore my employer) and many other people. While the 1% add great value on VMware’s behalf they also benefit greatly from the experience themselves. Just bear in mind that much as we’d all like VMware’s recognition, VMware need us too!
I’m already vExperienced and I’d love to be a vExpert. Fingers crossed!
ps. Apologies to Alex Maier who now runs the vExpert program – I’d already made up my ‘poster’ before I knew!
After being asked why I blog by a co-worker I’ve been thinking about what motivates me to blog. An inspirational blogpost by Mark Pollard on how to get into strategy identifies some traits which strike me as equally applicable to blogging;
- Curiosity. This is partly why I got into blogging as the techie in me wanted to know how it worked, which technologies were involved, what was that plugin that other bloggers were referring to? It’s the same instinct that makes good engineers – they want to know how something works so they take it apart!
- Action. Like most technologies the only way to really understand it is to get stuck in and do it. Until I started my blog I wasn’t sure what I’d blog about but I quickly found myself thinking ‘that might be interesting to others’ during my working day and I started turning thoughts into blogposts. I agree wholeheartedly with Seth Godin’s view that the process of distilling your thoughts into something readable for others is a very valuable process, and reason enough to blog – even if nobody reads it. Read more…
After several months of study (slightly longer than planned due to writing up all my study notes) I was finally notified that I’d passed the VCAP-DCA exam yesterday. Hurrah!
The VCAP-DCA blueprint is pretty comprehensive and for many will involve studying topics they’ve not used before. Regarding the exam itself I have nothing of value to add that hasn’t already been said, but it’s been nice to reflect on what I gained from taking the certification. Given that quite a few recruiters simply state ‘VCP/VCAP/VCDX’ as general requirements for job specs I’m not sure how much value the certification holds in the marketplace yet, but here are the top five ‘wins’ for me as a result of studying;
- PowerCLI. I’ve scripted in many languages over the years but none that are so easy to pick up and achieve results with. I’ve used PowerCLI in production to automate deployments, get weekly reports and automate some compliance work and I doubt I’d have done so much if I didn’t have to cover the VCAP-DCA blueprint (especially the VIX component).
- Distributed switches – my company don’t have Enterprise+ licencing so I don’t get to work with these in a production environment. Lab testing is never the same and the exam highlighted a few areas where I could improve. I like the concept, but with under a hundred hosts I’m not yet convinced of the value for money. Various features and products (vCD comes to mind) are dependant on vDS, so I think it’ll get pushed more and more by VMware however.
- Host profiles – again, I had no real world experience due to licencing restrictions.I did learn that they’re not that great though, even in limited lab testing. There are too many things they can’d do, a fairly limited interface and lack of flexibility. Definitely not the equivalent of Group Policy in an AD environment (which was my mental equivalent).
- ESXTOP. I’ve always been somewhat wary of this, especially after a presentation at the LonVMUG which was very good but hurt my brain! Despite being a Linux admin so comfortable with command line, something about the advanced ESXTOP settings seemed complex and hard to understand. After watching some VMworld sessions and working through the ESXTOP bible it’s now much clearer and I’ve found myself using it far more at work.
- vCenter Heartbeat. Like many places we’re increasingly reliant on vCenter and I worry about resilience. I now know how to use it – and the fact that I probably wouldn’t.
As with any exam though there are questions which you might not know the answer to, but you know a quick Google would tell you the answer (so have little real value in the exam, in my opinion). These aren’t quite in that category, but here’s three things which I had to learn purely for the sake of the exam;
- Fault Tolerance. Due to the 1vCPU restriction I’ve not got any servers which really benefit from this, so it was an exercise (if interesting) in theory only.
- vShield Zones. I’d actually hoped this might be in my top five, but in the end it’s in my bottom three. The interface is incredibly basic compared to any dedicated firewall so I wouldn’t want to use it in production. The exam also only covers v1.0, whereas v4.0 is the current release.
I used a wide variety of study materials, and in order of most beneficial here’s how I’d list them;
- Blogs – these complement the official docs – it’s where people spot the real challenge of a particular feature, or the unspoken gaps not mentioned in the official docs. Start at vLaunchPad.
- Official documentation
- VMworld sessions – free to view (mostly) and focused on particular subjects, these an are often overlooked treasure trove.
- Study notes – creating my own study notes definately helped me remember things, as did other people’s (Sean Crookston’s especially).
- Community forums – both the general vSphere ones and the VCAP-DCA forum are useful places to post questions, and see what everyone else is asking. vicfg-firewall anyone?
- Trainsignal’s Troubleshooting training course by David Davis. The information is very useful and goes above and beyond the blueprint requirements.
And of course I have something to add to the C.V.!