Getting the Norwegian VMUG up and running was a long process. I decided to have a go at it, and I spent a lot of time talking to people, thinking, planning and generally wondering how we could get it started and how to proceed. Some might say an inordinate amount of time, and they are right. I’m lucky to have talented and passionate people on board with me for this, this is not something I have done on my own. But, someone had to get the ball rolling.
In my work as a consultant I often have many small tasks to perform for customers, all while completing a bigger project. I have found that an easy way to keep track of all the little and big changes, is to create a ChangeLog. Normally ChangeLog’s are referenced in development projects, but it also sense to use it to track of your own, or your team members, changes to an infrastructure environment.
As for just about everything else, I use Markdown to make it easy to format and edit.
The VMware Certified Design Expert: VCDX. THE certification of certifications, especially if you work with VMware based solutions. It’s often regarded as the holy grail of certifications, and rightfully so.
But why is this the case, and why does «everyone» want to become one?
The reasons for it being such a highly coveted title, are pretty obvious:
Have you ever wondered what happens if you give 10.000 people access to an open-beta that is supposed to be under NDA?
Firstly, the NDA is no-go from the get-go. There is no way you can claim that you actually expect 10.000 people to not talk about something they know about. VMware vSpere 6.0 was the worst kept secret ever, for a reason. It might have been planned that way all along for all I know, but if that was the case, the NDA should never have been in place to begin with.
So, the cat formerly known as vSphere.next is finally out of it’s rather big bag, and vSphere 6.0 has been officially announced and will be available some time in Q1 (no date has been announced yet). There is enough of posts going into details on what is new and what has been announced, so I won’t be going over that right now. If you want to hear me talk about vSphere 6.0 and related news, you can always attend VMUG Norway on the 19th of february.
I recently set up a new Veeam Backup & Replication v8 demo lab, and my intial small job that consisted of two different Linux VMs and one Windows Server 2012 R2 Domain Controller was chugging along nicely. I had one minor from the start though, and that was that file indexing consistently failed for the Windows VM. No big deal, but I thought it was strange at the time.
Inspired by Scott Lowe’s Looking Ahead: My 2015 Projects, I’ve decided to do something similar.
Since I didn’t post anything like this in 2014, I can’t really go back and see how my plans turned out, or provide any assessement of it. I can say this though, 2014 was pretty awesome. I got a promotion, my vExpert status was renewed, vNinja was voted in the top 50 of the 2014 top VMware & virtualization vote, I published a book and finally got the Norwegian VMUG up and running. My VCAP-DCA 550 should be on this list as well, and so should my failure in achieving VCAP-DCD certification status. 2014 was also the busiest year in vNinja.net’s history, with close to a doubling of traffic generated through the year. The same goes for vSoup, some of the episodes we recorded in 2014 had some rather insane listening numbers…
Obviously I’m a bit late to the party here, but I guess late is better than never. It recently dawned on me that mucking about with lots of different file formats, interfaces and ways of doing things is rather counterproductive.
A lot of my work these days are related to generating content, be it a simple blog post like this or writing customer proposals and documentation. In the end, the deliverables are often quite different, but at the core they are strangely enough very similar. After all, the main thing is content, right? The file format itself, or how it is generated, doesn’t really have a bearing on the content at all, it’s just a delivery method. Lipstick on a pig, if you will.