Now that the seasons have changed, it’s time to look at 2017 and start planning the year. First up, when is VMworld 2017, and perhaps most importantly where? There has been a lot of speculation about this, and the perhaps strongest rumour was that it was moving to Berlin.
I’ve been fleshing out a proper Veeam Backup & Replication Demo lab at work, but doing demos on static VMs isn’t all that much fun and doesn’t really give us much. Doing scheduled backups of non-changing data is really boring.
So, in order to get some changes done on the file system on a few Linux VMs running in the environment, I came up with the following solution:
I’ve been a big proponent of the VMware vCenter Appliance for a long time, I even did a talk called VCS to VCSA Converter or How a Fling Can Be Good for You! on migrating to the VCSA at the Nordic VMUG last year.
The VCSA has gone through a few iterations and versions by now, coinciding with the vSphere releases.
A while ago I decided to try and gather a bunch of non-public information in an easy to write and consume fashion. After a bit of fiddling, and testing different potential solutions, GitBook emerged as the best option. By using MarkDown as the markup language, it’s both cross-platform and easy to manage, as the content is nothing but raw text files.
Since I “launched” my In the Bag series of weekly links yesterday, I figured I should really show what is indeed in the bag. Lifehacker runs a series called Featured Bag and the voyeur in me finds it interesting what other people carry around, and how they organize it.
This is my attempt at doing the same. This is my everyday carry, most of these items are always in the bag when I leave the house in the morning. I’ve been using backpacks for years, but noticed I always just carry it around on righ shoulder, so I decided to go for a shoulder bag instead. For the most part this works our fine, if I’m travelling for more than a day, I tend to re-pack in one of the backpacks I have instead.
As mentioned before, I’ve kinda turned my home lab into some sort of Slack-Ops deal, where various services in my home lab notify me of events in a private Slack channel. The latest rendition of that, is adding Slack notifications from phpipam. Once phpipam detects a new device picking up an IP in my network, it notifies me like this: In order to get this working, I had to edit the /var/www/phpipam/functions/scripts/discoveryCheck.