While I was away on a two week holiday on the Croatia’s sunny Makarska Rivijera, Eric Siebert announced the result of his annual Top vBlog, and much to my surprise vNinja did quite the jump from last years 46th spot to this years 27th! Honestly, I thought the site would drop out of the the top 50 list this year, but once again I’m proven to be mistaken. Some times being wrong is just great!
A little while ago William Lam published a little python script called extract_vsphere_deployment_topology.py that basically lets you export your current vSphere PSC topology as a DOT (graph description language) file. Great stuff, and in itself useful as is, especially if you run it through webgraphviz.com as William suggests.
The thing is, you might want to edit the topology map, change colours and fonts, and even move the boxes around, after you get the output. If you have a large environment, you might want to combine all your PSC topologies into a single document? It turns out, that’s pretty easy to do!
Way back in late 2014 I volunteered to do technical review for a book called **IT Architect: Foundation in the Art of Infrastructure Design: A Practical Guide for IT Architects. Due to a lot of unforeseen events, the book has been delayed quite a bit, but it’s finally available as hardcopy, paperback and eBook! The book is written by J**ohn Yani Arrasjid, VCDX-001, Mark Gabryjelski, VCDX-023, Chris McCain, VCDX-079 and as the title states it really does lay out the foundation of how to approach infrastructure design in a modern virtualised data center.
PernixData, and Frank Denneman, has released vSphere Design Pocketbook v3. As the title reads, this is the third time PernixData releases one of these books, and I’m honored to be selected amongst the contributors for the second time, this time with a chapter called «VCSA vs Windows vCenter - Which One Do I Choose, and Why?«
Go grab your electronic copy now, and be sure to bug your local PernixData representative for a hard-copy later. I know I will.
Yesterday was my first real day as a Senior Solutions Architect for Proact, and today I flew to Oslo for on-boarding and some face-to-face time with my new colleagues over there. By the looks of it, there is a lot of exciting things in the pipeline, and it we land the things we have started on this should be interesting. Very interesting indeed. In addition to the excitement around changing employers, and roles, some other things have also happened.
I think Seth Godin might have been onto something with «Make something happen», so I did.
Today was my last day at EVRY. Some might already have been aware of this, mostly because of Hoff-Job-Announcement-as-a-Service, but also because of my own tweet as I left the EVRY offices in Bergen as an employee for the last time:
For some time now I’ve been advocating the usage of VCSA instead of the traditional Microsoft Windows based vCenter. It has feature parity with the Windows version now, it’s easier to deploy, gets right-sized out of the box and eliminates the need for an external Microsoft SQL server.
One of the questions I often face when talking about the appliance,_ is how do we handle backups?_ Most customers are comfortable with backup up Windows servers and Microsoft SQL, but quite a few have reservations when it comes to the integrated vPostgres database that the VCSA employs. One common misconception is that a VCSA backup is only crash-consistent. Thankfully vPostgres takes care of this on it’s own, by using what it calls Continuous Archiving and Point-in-Time Recovery (PITR).