As has become a yearly tradition, the vote is on. Pick your favorite VMware & virtualization blogs and give Eric Siebert loads of work.
I hope the good guys at Infinio who sponsors Top vBlog 2015 also offers some assistance in doing some of the legwork required to get the results accumulated. Also, don’t be an ass.
Last year, in November, the first ever meeting in VMUG Norway took place in my hometown of Bergen, and since then there has been meetings in Oslo, Trondheim and a second one in Bergen as well.
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.
It turns out, that all you need to get a VMUG running in your local area, is to arrange one. It is really that simple. Don’t over think it and don’t overcomplicate things. It really isn’t that hard, and honestly, it really doesn’t take that much effort either. Start small. A small venue, and a few people goes a long way.
Admittedly, the Norwegian VMUG is small in comparison to our Danish counterparts, but we all have to start somewhere, right? Sure, we can grow bigger and better, and of course we will learn and improve as we go along. I for one is really excited by the possibilities VMUG Norway has going forward, and I hope the attendees share our passion for growing the local community. If they do, I’m sure VMUG Norway is destined for success and growth.
If you plan on starting a local VMUG, just remember one thing: It is all about the U(sers), not the leadership or even the sponsors. Keep that in mind, and you’re ready to go.
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.
Currently, I use the following format to keep track of changes done to a customer environment
| Date | Task | By |
|14.02.2015|ChangeLog created| Christian Mohn
|15.02.2015|Upgraded vCenter Operations Manager 5.8.3 Build 2076729 to 5.8.4 (Build 2199700)| CM
|16.02.2015|Updated *vCSA01* from 220.127.116.1100 Build 2063318 til 18.104.22.16800 (Build 2442330)| CM
|16.02.2015|Updated *esxi01* from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374) | CM
|16.02.2015|Updated *esxi02* from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374) | CM
|16.02.2015|Updated *esxi03* from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374) | CM
Once rendered as HTML, I get a nice list displaying all the recent changes.
||Upgraded vCenter Operations Manager 5.8.3 Build 2076729 to 5.8.4 (Build 2199700)
||Updated vCSA01 from 22.214.171.12400 Build 2063318 til 126.96.36.19900 (Build 2442330)
||Updated esxi01 from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374)
||Updated esxi02 from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374)
||Updated esxi03 from 5.5.0 (Build 1623387) til 5.5.0 (Build 2456374)
As you can see this a quick and easy way to document changes. Since the markdown files are pure text files, they can easily be converted to other formats with Pandoc, or checked into a “code”-repository for easy retrieval.
Do you use a ChangeLog for your infrastructure, or how do you quickly document changes in your environment?