Brian Harring Email & Phone Number

Fort Collins, Co, Us

San Francisco, California, Us

San Francisco, California, Us

San Francisco, California, Us

* Lead engineering for a team of 5; introduced ticketing, sprints, roadmapping, code review, and CI. Responsible for hiring and onboarding.* Responsible for architectural design, security posture, and on premise production network for robotics support.* Feature development and product development; primary notables were sales tax integration, error capturing, and in general, stabilizing the site.

Leading on puppetization efforts, in parallel to git/gerrit/devops introduction. Core focus/hire was to bring modern devops concepts in house.

Mountain View, Ca, Us

ChromeOS Build; working on build speed, hermetic building (builders and build itself; whether trying to enforce homogeneity of builders or abuse of cgroups to contain errant processes from failed builds), ton of git/gerrit work (upgrades, connection flake debugging, implementing object pool sharing), rebuilding/deploying a transactional Commit Queue, or just in general trying to keep things up/running since failures in the build machinery directly translate to lost developer time; end result while fortunately rare, occasional late night/early morn debugging/restoration of the stack.

Volunteer work, with occasional gaps due to paying work. Primarily focused on package managers in conjunction w/ the standards they relied upon; very minimal infra involvement in addition. Along the way, I put in place the EAPI mechanism (used for format versioning of ebuilds), drove the package manager side of the prefix project, served as co-lead of portage for many years, and wrote half of the portage subsystems.In the early years, I was fairly active in media library maintenance; later years, more QA and python.

Elected position; monthly meetings, serving as the deciding board for questions elevated to that level, *rough* direction (it's opensource; this is cat herding at its core), signing off on new ebuild formats, identification/pushing on areas in need of work (specifically spent time trying to help w/ cvs -> git conversion were possible).

Santa Clara, California, Us

Usual crazy mix of across the map work; First year, primarily responsible for MeeGo IVI releases (1.0/1.1), integration, debugging, and release engineering work. Beyond that, interim ops (starting w/ a ~20 server live DC move) for a month or two while interviewing proper replacements, general poking at OBS (buildtime reduction for ARM from 4.8 to 3.6 days via parallelization work and Qemu mmap fixes, identifying a couple of rooting attacks against it), and a fair amount of training/helping folk in their day to day.After, helped spin up android tablet effort; developer tools/infrastructure bring up (gerrit/git training), worked on PoC boards, release engineering, interviewing, developer training, and generally trying to keep the technical centre held during bootstrapping under an aggressive schedule.

San Francisco, Ca, Us

Essentially wearing two hats-*running all things OPs: implemented monitoring and performance tracking, 24x7 on call, rebuild and secure network topology, stack auditing/hardening, rebuilding stack to be HA, establishment of internal SLAs, all things DBA; basically a full rebuild of the existent stack into a proper production setup*system engineering on the side; primarily a reimplementation of the sms relay implementation into a proper scalable high volume setup, along with internal mockups of the various providers for zero cost performance/QA testing.

Us

Primarily ops work:* running down VM performance regressions in our custom DB* developing/maintaining OS releases throughout our stack (thus responsible for any issues w/ components of said OS)* development/maintenance of our network imaging infrastructure* the usual SA tasks: configuration management, tracing/patching mem leaks, packaging third party bits, hardware maintenance, etc.* python on the side as time permitted- primarily tools, although fair bit of 2.6 related conversion issues for external sources.

Huntsville, Al, Us

Python web work, DBA/SA, scaling work (load balancing, multi-tier caching), user generated content media cluster implementation- essentially HA work, along with auditing. Fairly heavy amount of optimization/scaling work done in conjunction w/ David Cramer- at that point, we modified django the point where master/slave support was built in, db connection pooling, multiple site configurations served from the same interpreter instance (heavily matters when you've got 40 different subdomain/sites in play on a generic pool of webnodes w/ limited memory), heavy across the board django optimizations (signaling, model instance creation, addition of an identity map to the ORM, template engine optimization, etc). Pretty much heavily ahead of the curve django wise, although due to that, only chunks of it wound up folded back into upstream.

Santa Clara, California, Us

LSB work; 3.1/3.2 spec including distro analysis, tool development, and porting work.

General linux development and SA work; imaging, mysql replication, QoS.

SA for dozen linux machines, user support (approximately 150 users), network planning/management, OSX porting and webapp (php/perl) development.

Linux embedded development (buoy project ran by Paul Hanson), Windows NT/solaris maintenance, supporting userbase of approximately 25.