In this post I would like to share a handy little workaround for returning to Google Hangouts, despite Google Meet. Having narrowly escaped working at Google via acquisitions twice, I have stood by and watched as the Ad Words money-pipe funded rewrite after boondoggle after rewrite. When Google announced "Google Meet" earlier this year as an "enterprise-friendly version" of Google Hangouts, I was annoyed, but not surprised.
After learning how to build my first terrible website, in ye olden days, perhaps the second useful thing I ever really learned was to run multiple websites on a single server using Apache VirtualHosts. The novelty of being able to run more than one application on a server was among the earliest things I recall being excited about. Fast forward to the very different deployment environments we have available today, and I find myself excited about about the same basic kinds of things. Today I thought I would share how one can implement a concept similar to Apache's VirtualHosts across Namespaces in Kubernetes.
This research was funded by CloudBees as part of my work in the CTO's Office with the vague guideline of "ask interesting questions and then answer them." It does not represent any specific product direction by CloudBees and was performed with Jenkins, rather than CloudBees products, and Kubernetes 1.8.1 on Azure.
Months ago Microsoft announced Azure Container Instances (ACI), which allow for rapidly provisioning containers "in the cloud." When they were first announced, I played around with them for a bit, before realizing that the pricing for running a container "full-time" was almost 3x what it would cost to deploy that container on an equitable Standard A0 virtual machine. Since then however, Azure has added support for a "Never" restart policy, which opens the door for using Azure Container Instances for arbitrary task execution.
A couple weeks ago I boarded a plane at the always-adorable Charles M. Schulz Sonoma County Airport en route to Seattle to participate in a Microsoft Azure OpenDev Event. Thanks to my pal Ken Thompson, who recently joined Microsoft as a product marketing manager for their Open Source DevOps team, I was invited to talk about all things Jenkins with a dash of Azure.
2018 will be the sixth year for the Testing/Automation dev room at FOSDEM. This room is about creating better software through a focus on testing and automation at all layers of the stack. From creating libraries and end-user applications all the way down to packaging, distribution and deployment. Testing and automation is not isolated to a single toolchain, language or platform, there is much to learn and share regardless of background!
The traffic on the Bay Bridge connecting San Francisco to Oakland is one of the most congested routes of traffic in all of Northern California. Somehow it gets even worse on Saturday and Sunday. One weekend, a few years ago, I was driving my wife and some of the women from her soccer team back to Berkeley, from a game in San Francisco's Golden Gate Park. On the east side of the bridge, before inching onto I-580N, I was pretty pissed off, and half-joking half-frustrated shook back-and-forth at the steering wheel "GAHHHHHHHHHHHH." The woman sitting behind me, who was certainly the "funny one" of the group, put her hand on my arm and gently said "Tyler, this is your reality now."
The insanely strong gusts of wind would not stop clattering the tin roof panels over the back patio. Begrudgingly, I awoke, dressed, and tried to secure the roof panels before the neighbors got too ornery. Stepping up the ladder, I noticed an orange glow north of the house. Just after midnight, I had not heard any sirens, I jumped into the car on the assumption that one of those houses by the park was burning and had not yet been reported.
Quite possibly my favorite part about working on open source infrastructure is that I can share as much as I want! Contrary to corporate infrastructures, where most of it is closed source and hidden away, open source project infrastructure is by its very nature open. From a pedagogic standpoint, this allows me to teach others without needing to create contrived demonstrations or examples, but we can instead refer to the real code being used to deploy the Jenkins project.
Over the past decade two things have become increasingly clear: practically every modern industry is part of "the software industry," in one way or another, and "the software industry" is rife with shortcuts and technical debt. Working in an Operations or Systems Administration capacity provides a front-row seat to many of these dysfunctional behaviors. But it's not just sysadmins, many developers are also called to engage in or allow: half-baked product launches, poor-quality code deployments, or subpar patch lifecycle management.