search menu icon-carat-right cmu-wordmark

Posts by Tim Palko

Vagrant Box Wrangling

Vagrant Box Wrangling

• Blog
Tim Palko

So, you're using Vagrant, and maybe you've even read my earlier post on it, but your Vagrant box doesn't have everything you need. Or maybe it has too much, and you need something simpler. For instance, do you find yourself installing or removing packages or fixing packages to specific versions to get parity with your production platform? Or maybe you need more extensive auditing over your environment, such as when you (or your customer) can't...

Read More
From Vagrant to Victory

From Vagrant to Victory

• Blog
Tim Palko

A few years ago, my team took the task of designing and writing a new (and fairly large) web application project that required us to work collaboratively on features, deploy to unfamiliar environments, and work with other teams to complete those deployments. Does this sound like DevOps yet? Our task was to make these deployments happen with limited resources; however, we didn't want to sacrifice environment parity or automation, knowing that these would help our...

Read More
Monitoring in the DevOps Pipeline

Monitoring in the DevOps Pipeline

• Blog
Tim Palko

By Tim PalkoSenior Member of the Technical StaffCERT Cyber Security Solutions Directorate In the realm of DevOps, automation often takes the spotlight, but nothing is more ubiquitous than the monitoring. There is value to increased awareness during each stage of the delivery pipeline. However, perhaps more than any other aspect of DevOps, the act of monitoring raises the question, "Yes, but what do we monitor?" There are numerous aspects of a project you may want...

Read More
DevOps for Contractors

DevOps for Contractors

• Blog
Tim Palko

The challenges of DevOps--a cultural change, learning new technologies, and making a big-picture impact for a software project team--are possibly even more challenging in contract work. In this blog post, I'll expand on some of my past experiences as a contract software developer and discuss, in retrospect, how DevOps could have worked in different scenarios....

Read More
The Missing Metrics of DevOps

The Missing Metrics of DevOps

• Blog
Tim Palko

This post is the latest installment in a series aimed at helping organizations adopt DevOps.Some say that DevOps is a method; others say it is a movement, a philosophy, or even a strategy. There are many ways to define DevOps, but everybody agrees on its basic goal: to bring together development and operations to reduce risk, liability, and time-to-market, while increasing operational awareness. Long before DevOps was a word, though, its growth could be tracked...

Read More
DevOps Technologies: Fabric or Ansible

DevOps Technologies: Fabric or Ansible

• Blog
Tim Palko

The workflow of deploying code is almost as old as code itself. There are many use cases associated with the deployment process, including evaluating resource requirements, designing a production system, provisioning and configuring production servers, and pushing code to name a few. In this blog post I focus on a use case for configuring a remote server with the packages and software necessary to execute your code....

Read More
DevOps Technologies: Vagrant

DevOps Technologies: Vagrant

• Blog
Tim Palko

Environment parity is the ideal state where the various environments in which code is executed behave equivalently. The lack of environment parity is one of the more frustrating and tenacious aspects of software development. Deployments and development both fall victim to this pitfall too often, reducing stability, predictability, and productivity. When parity is not achieved, environments behave differently, which makes troubleshooting hard and can make collaboration seem impossible. This lack of parity is a burden...

Read More

Contact the Author

Tim Palko

SEI Digital Library

SEI Publications

Visit the SEI Digital Library to see other publications by Tim Palko

View publications