Spring has officially erupted in Sonoma county, with the immense amount of biological activity we have come to expect from one of the more productive regions of the country. On our meager parcel we have more plants, with more variety, than ever before going into the ground. With two seasons under our belts in the "south crop" and one season with the "north crop," I absolutely couldn't wait for the cold nights to pass, and am pleased beyond belief that Spring is finally upon us.
My neighbors must surely think that I am some kind of lunatic. Last spring I dug up half of the dying sod in the front yard and installed three 8x4 foot raised garden beds. Then, last fall, I started banging around with a few, bright blue, 55 gallon food-grade steel drums, in the car port, which I picked up to catch rainfall for my garden. In this post, I will detail my initial results using a home-brew system using these metal barrels.
Somewhere along the line, safety became a crucial part of my decision-making process. I always wear my bike helmet. I put on my protective safety glasses when wielding an axe or doing something which might splinter or launch debris. In my tool closet I have a big bag of ear plugs which I put in whenever working with a power tool bigger than my cordless drill. When riding a motorcycle I always wear my full-face helmet, armored jacket, and sturdy gloves. And of course, when I am driving a car, I always check my blind spots.
As part of SCaLE 15x, I took part in the first Open Source Infra Day where a number of other sysadmins and I shared stories and patterns which have helped us maintain open source infrastructure. As part of the "unconference" tracks, I suggested and then led the session "Running containers in production." As my luck would have it, in a group of roughly 10 people representing various groups, Jenkins was the only project running production services in containers. I thought I should share what it's like, and why you should stop standing on the sidelines and give containers in production a try.
Unfortunately the Jenkins project will not be participating in the Google Summer of Code (GSoC) 2017. While I am disappointed, I am not all that surprised. Last year, our inaugural year in GSoC, was tough insofar that we had to learn many things the hard way, did a poor job of selecting student proposals, and failed to recruit a satisfactory number of mentors.
I have been "farming" for a few years now and as the beginning of the 2017 season in northern California approaches, I wanted to share some advice to consider, regardless of whether you're a gardener or not.
Most people would consider me to be a nerd. I work in the tech industry, my laptop looks quite non-standard (a stickered Thinkpad), and I tend to travel with suitable amount of electronic kit. Within what I would call "the nerd community," I sometimes get looks as if I'm especially nerdy. I use a tiling window manager on my Linux desktop, I have strong opinions on free and open source software, and above all else, I use a myriad of "super nerdy" console-only applications like mutt and irssi.
FOSDEM is quite the experience, thousands of geeks running around, dozens of free and open source projects, and plenty of Club-Mate and beer for every attendee to purchase. The weekend is exceptionally busy, and for me, the sleep at night between the chaos is always interesting.
When I first started hacking on what I knew to be called "free and open source software," I had never met another "hacker" in real life. It felt like a very niche, almost insignificant community until my first FOSDEM in 2006, where for the first time I saw hundreds of free and open source hackers scurrying about. It may have been a niche community existing primarily on IRC and mailing lists, but I finally had proof that there were actual people involved in the endeavor.
The Jenkins project is currently undergoing a major infrastructure migration to Microsoft Azure as our primary infrastructure provider, and as a result, I have been spending a tremendous amount of time getting friendly with Azure tooling.