Profile cover photo
Profile photo
Tim Chavez
Partner / Parent / Programmer
Partner / Parent / Programmer
About
Posts

+Michael Halcrow Now that Bruce Schneier is an IBMer are you ready to come back home and work in IBM Security w/ him :)?

Google+ is still a thing?

Post has attachment
traceroute bad.horse

Post has shared content
So good: "Overwork is not defined by the amount of our day work occupies but by the amount of our selves tied up to it. We “over” work not when we work too hard but when working becomes less of a means and more of an end. When meditation, exercise, sleep, holidays, and even parenting, are cast as tools to make us better workers."

Post has shared content
At IBM, some filled and more open. So there are now a couple of openings for the Linux kernel (https://lnkd.in/esXPynw, https://lnkd.in/eVmqC3w) and one in security (https://lnkd.in/eDTyqpK).

Post has attachment
Pretty amazing.  I'll never be so good at anything as this guy is at playing the guitar :)

Post has attachment
At +HP​  I'm partially responsible for the support, operation and improvement of the foundational services that +HP​  has built its #Helion CI/CD workflow on.  These services -- gerrit, zuul, nodepool, jenkins, etc - are the very same services used upstream to build #Openstack itself.  As you might expect, things are complicated, and understanding what's going on at any given point in time can often be elusive and non-obvious.  So, to better assist us, we create and / or use tools to visualize the data we collect from the system.  Most of the time we focus on aggregate data, but some times we'd like to drill in and analyze a specific build. I've created a tool called zuul-build-viz to do this. This tool parses the zuul.log and creates charts visualizing a specific changeset build.  Because a build in the context of zuul is actually just a series of events and these events largely follow a progression (the exception being the actual jobs which run in parallel), the charts that this tool produces show when events occur and how much time passes between them.  The combination of both these bits of information can really be insightful.  For example, a long period of time between the time a job is submitted and the time it starts running could indicate that the demand for a given node type exceeds your supply of them and / or that Jenkins is saturated.  What if you saw a job ran twice in the same build?  That would indicate the job returned a "None" result and may warrant additional investigation (after all you could pay a penalty in time when this happens if it effects the overall build time). You get the idea.

I've gone ahead and made my code publicly available on GitHub (though I can't guarantee it'll stay in this repository).  Please check it out!

https://github.com/timrchavez/zuul-build-viz

Also, if you're curious about the chart this tool produces, I've attached a sample chart which shows a build for our internal config.

Post has shared content

Post has attachment
Not the Ghostbuster I imagined I'd become as a kid, but still a pretty cool gig nonetheless.

Post has shared content
Wait while more posts are being loaded