Devops

Please don’t let SRE go the way of DevOps

 Opinions  ,

It always starts with a Tweet heard around the world state, amirite? Here’s my answer come at me https://t.co/gpTD54xcjy — Ernest Mueller (@ernestmueller) October 2, 2018 I will start this by saying I respect both of these gents immensely. Both help put on DevOps Days Austin and are really key figures in the Texas tech scene. Whether you reside in Dallas or San Antonio you probably know both of these Austin residents names.

Read more →

Let’s talk DevOps job titles

 Opinions  ,

I’ve watched the community struggle on and off with job titles for those working in the DevOps market. DevOps is and always will be simply a set of philosophies, beyond that are three major systems-type fields I see companies using DevOps in: Operations, Platform Engineering, and Release Management. Site Reliability Engineering To avoid some initial confusion I’m going to address the topic of Site Reliability Engineering. For those that’ve read the book and heard the hype you’ll realize that SRE is Google’s implementation of Operations.

Read more →

Splitting up Terraform & state file separation

 Workshops  , ,

Terraform is fundamentally operated off of these things called “state files”. State files literally are the single source of truth, as far as Terraform is concerned, in regard to your infrastructure. They’re formatted in regular JSON but carry a lot of metadata that helps Terraform plan and predict what will happen with your infrastructure.

All infrastructure orchestrators have to work off of some sort of state. Interpreting live infrastructure state is complicated and sluggish at scale so many of them resort to some sort of centrally hosted file system that indicates this state to them. CloudFormation actually does much of the same thing with CloudFormation templates in S3 Buckets, you just see less of it exposed to you.

What Terraform really enables is an organization of infrastructure that can be reused, version controlled, and browsed by anyone in the organization. Nobody goes to the S3 bucket and views the Terraform state file, rather, they view the code that generated that state file hence it’s important not to make manual modifications to infrastructure once an orchestrator has run.

Read more →

DevOps and SRE in the Enterprise

 Opinions  , ,

At start ups we have the luxury of starting from the ground up. Philosophical and cultural revolutions are always easier to consider when simply nothing exists. This is a common complaint of large enterprises when they examine DevOps, SRE, or Production Engineering for their own organizations. Subsequently they end up morphing the core beliefs of those philosophies to fit their existing culture. While this can be done it really results in a lot of confusion and frustration especially at the ground level where, in the aforementioned disciplines, most of the work and decision making takes place.

Read more →

Testing Jekyll with Travis CI

 Workshops  , ,

I’ve finally settled with the fact that Jekyll is going to be my mainstay for a while. It’s got a lot of features I like some of which are subsequent to being a static site generator, others being thoughtful implementations. Here’s a few highlights: Kramdown. If you haven’t heard of Kramdown, it’s like normal markup language on steroids. It gave me a lot of bootstrap-esque features I liked, like notifications.

Read more →

Starting a Career in DevOps

 Opinions  

A few years ago I got out of the military as a radio technician, but before I got out I had a ominous conversation with a long time friend explaining that I thought the future of an IT career lied in a mix of systems, programming and virtualization. At the time I really knew nothing about virtualization, had really only web and some Perl/Python experience and a life long love of Linux. Since then, my experience has turned it into a beautiful well-rounded career that’s only growing.

Read more →
Social Media
  • @codencombovers
  • mattouille
  • code_n_combovers
  • mattouille
  • 5854293/matt-o