You might have noticed that Go SDDC has been lagging behind for a while, this is not due to my proverbial ADD (not this time at least) but to work I’ve been doing behind the scenes.

I’ve spent almost every single non-working hour since VMworld on my DevOps projects, mostly around my Vagrant and Packer plugins/providers, at some point (I don’t even remember how that started) I’ve got involved with the new 3rd Platform team that was being built inside VMware, that blossomed in what is now called Cloud Native, led by Kit Colbert and part of the Office of the CTO (commonly called OCTO inside VMware).

Kit asked me to join the fledging team back in November and I’m extremely excited to say I will officially transition to the Cloud Native team under him on January 15th.

Leaving the Global Center of Excellence is a tough choice, the team is extremely talented and John, my manager, is the kind of guy everyone wish to have as a boss, but joining the Cloud Native team was the natural choice for me at this point, as I will help shape the company strategy for our 3rd Platform efforts and continue working on my projects full time. It’s also a fundamental change because I will shift to an R&D role and I will no longer be part of the Field org, having spent the last 10 years as a Field person, this is a real “back to the roots” move for me.

My role in the team will be to work on the integration points between our current and future products and the Open Source players (the unofficial title I picked is “Research Engineer”), we have several interesting projects in the pipeline and exciting stuff is going to be announced and released in 2015.

If you’re interested in Docker (who isn’t these days?) You probably heard of the new Docker “Machine” tool that was unveiled during DockerCon EU back in December, I was behind the packaging and development of our tech preview (along with Yang Yang and Zee Yang who respectively built the vSphere and Fusion driver), that was my first “unofficial” assignment :-).

I’m not saying I will update the blog more often (hopefully I will :-) but given my new role I will probably be much more active on GitHub than I ever was before and given this blog is now hosted there… Who knows :-)

If you’re following my Twitter or GitHub feed you probably know that is now served by GitHub Pages and the Jekyll source is publicly available (so feel free to send me a pull request if you want to see something changed :-).

I used to host the static HTML output on Amazon S3, but the whole pipeline left a lot to be desired, so I started fixing things here and there and ended up with a much more streamlined (and open) way to build this website.

eating my own CI dogfood

I’ve been a very strong advocate of employing CI/CD patterns internally at work, this prompted me to move this very website to an automated testing environment.

To automate the website testing I’m employing the html-proofer gem, tests run from a Rakefile that automates the test launch in a Travis-CI environment, Travis is also extremely well integrated with GitHub and fits perfectly in the Pull Request workflow that we all know and love.

what is left behind

There are a couple of things I had to leave behind due to various reasons, namely:

  • The tchort gem I use to disseminate links on social media (it’s really just a glorified interface to Buffer) is not public, I will probably open source it in the future but right now it’s so primitive and vertical that it would be of very little use to anybody else.

  • The RSS feeds are no longer available, I used to create them with a Jekyll plugin that ran on my machine but it’s not supported by the Jekyll instance used by GitHub Pages so I decided to trade RSS for source openness.

Feel free to poke around in the source, I haven’t done any deep cleanup yet so feel free to contribute with a PR if you feel to :).

Just a quick heads up, our vagrant-vcenter and vagrant-vcloudair providers for Vagrant are incompatible with the newly released version 1.6.5, to function properly you must install Version 1.6.3.

This is due to a conflicting version of a Ruby Gem (Nokogiri) that is being introduced in the embedded Ruby that ships with Vagrant 1.6.5 which now includes a much newer version of the Gem and is incompatible with the version currently required by our Plugins.

I plan to ship a new version of the providers before the end of next week, in the meantime, please revert back to version 1.6.3.

Happy Vagrant!