Let's Talk DevOps

Real-World DevOps, Real Solutions

  • The journey

    My journey into this space began a very long time ago so I’ll skip all the gory details and jump into how I managed to get to this point. The gist of it is I was a “sysadmin” running IT for what was at the time a very large systems integrator. We had ~200 or so people and processed roughly 300 orders per day. It was a “paperless” warehouse running on OS/2. Told you it was “long ago”. Let’s fast forward…

    Started working for a company who was starting their transformation journey (this is well before Covid) and had been using large numbers of virtual machines. I was brought in because they had an outage due to a hardware failure and new management decided it was best to take advantage of AWS. The current AWS infrastructure was created by the old school datacenter admins so it, too was a catastrophe waiting to happen.

    I had been working with AWS for a while so I had been taking my knowledge of puppet and applying it to help automate some of the mundane tasks. The old school devs were used to using mercurial so I encouraged them to pull some of the tasks created in puppet into their code and got them started deploying their apps on their own to AWS. This was working.

    Fast forward a bit and the dev teams had evolved to a really nice Agile based setup. I had spent a ton of time learning how to manage pipelines, transitioning from puppet to terraform, and had educated a lot of the newer operations folks on automating everything.

    My journey is probably very similar to most. In my case I never really got into windows. I had started down the linux path very early in the big scheme of things and stuck with it. This really helped when it came to running and managing things in the cloud. Transitioning all of the various scripting languages was pretty straightforward because I had a good grasp on how to script. I had bash scripts for everything and that helped tremendously when I dove into Terraform and other tools. Plus I was very comfortable with the command line.

    The one thing I suggest is read, read, read. O’Reilly is a great resource. No matter where you are coming from the most important thing to remember is look at the box and think INSIDE of it. Never try to apply knowledge from what you are currently doing into what you want to do. What I mean by this is managing VMs is very different from managing container images, but they are the same. Yea…I know confusing, but so is “cloud-native”.

    I did it. You can, too.

  • Where did Kubernetes come from?

    There’s a lot of great articles about how containers and subsequently Kubernetes came about…just search kubernetes with your favorite search engine!

    From a devops perspective the virtual machine’s (VM’s) movement created a bunch of issues for operators mostly because of how developers took advantage of the monolithic stack which VM’s proliferated.

    Google started down the path when they realized the opportunities based on how some older technologies consumed compute resources and added a cgroup functionality to the kernel. The container movement was officially underway.

    This also started a movement to change how applications are developed. They say “timing is everything” and it all fell into place. If you think about how the basic elements of container technologies (images, containers, and registries) are used today the concept of develop once, run anywhere has taken hold.

    BUT…this really is only one part of the full equation. Developers now have a lot more resources at their disposal and these resources are what operators have to manage.

    That’s where Kubernetes comes into the picture. Kubernetes helps solve the operational issues around managing or orchestrating all of the containers and their requirements around scale, load balancing, service discovery, observability, etc.

    Kubernetes originated with Google primarily because Google was well ahead of most everyone hence the work on cgroups. Google created a platform they called Borg well before Docker was conceived and right about the time Amazon started their “web services” division.

    Google released Borg in 2015 to a new foundation created with the Linux Foundation called the CNCF or Cloud Native Compute Foundation. Borg was donated as Kubernetes which stands for “Helmsman”. K8s (short hand for Kubernetes) is now one of thousands of CNCF projects.

    With 10 years of experience behind them and the reputation of Google, Kubernetes was then and continues today to be the de facto standard platform of modern cloud native computing.

  • New to DevOps? Start here…

    New to the devops scene? Want to get started with a career supporting application operations, managing Kubernetes, running docker, or just browsing around. This site is going to be designed to provide some interesting anecdotes, entertaining articles, and how-tos for getting started with a career in the field of “devops”.

    Ah yes…what is this “devops”. Everyone has an opinion for sure. Some call it a “paradigm“. That word has negative connotations though. Some actually feel it is a “engineering position”. Ok. Acceptable. Others just call it what it is…an operator who supports the development efforts of an enterprise. Dev-Ops. No matter, the idea here is to provide info for every opinion.

    Want to know more about a topic whether it is Kubernetes, Application Development, Devops, or other enterprise datacenter topic? Speak up. Comments are welcome.

    Next up…Getting Started in DevOps