My career as a software engineer started in 2007 at Purdue University. I was working in the Linux kernel and researching how data was shuffled between the kernel and the user application layers. This was happening in huge clusters of machines that all talked to each other using OpenMPI — how supercomputers, like those at Los Alamos National Labs, operate to perform their enormous calculations around meteorology, physics, chemistry, etc.

Although AWS sometimes feels like magic, it’s just software that controls capacity and allocation on their previously provisioned hardware. RDS is one of the services that can feel especially magic, because of the general difficulty and drudgery required to set up and manage a production database. In a matter of minutes, anyone can have a production database, complete with replication, automatic failover, backup schedules, and point-in-time recovery.

We've been fairly public about the amount of testing we have for Oh Dear!. Freek has been showing bits and pieces on his Twitter to show the extent of that effort. Having a huge test suite is nice, but integrating it into your development workflow is even better.

Ankur Agarwal, Rancher's Head of Product Management, describes new features in Rancher 2.2. Learn how to monitor multiple Kubernetes clusters in this step-by-step tutorial and how our Alpha Release process works.

With the recent panic over the zero-day Kubernetes vulnerability CVE-2018-1002105, Kubernetes administrators are scrambling to ensure their Kubernetes clusters are upgraded to a version that is patched for the vulnerability. As of this writing, the minimum versions that have the patch are 1.10.11, 1.11.5, 1.12.3, and 1.13.0-rc.1.

Today Rancher announces a partnership with Arm to create a Kubernetes-based platform for IoT, edge, and data center nodes, all powered by Arm servers. Rancher and Arm are working jointly on a Smart City project in China. Read more here.

A decade ago, an enterprise adopting DevOps was a rare event. In the last decade, some businesses dipped their toes in, others spent big money going all in. Now the question isn’t whether to make the culture shift, but how to be successful as it grows. It’s how to scale the adopted DevOps practices in the enterprise. This article is going to focus on highlighting common missteps and offer advice that can help you make decisions to handle the challenges ahead.

As the year draws to a close, for many of us this is a time to slow down, kick back and look forward to holiday time. For others, the work certainly isn’t done yet. The “S” word comes down to bear. Like it or not, this time of year – it’s all about the Shopping.

Google has effectively made the discipline of site reliability engineering (SRE) a DevOps best practice by publishing two decades’ worth of lessons in keeping alive the most scalable apps on the planet. As more organizations make the shift (or “transformation,” as it were) to becoming IT organizations, the demand for reliability increases substantially for customer-facing services.

We read with interest a recent article from CloudBees published in The New Stack: How Culture Will Make or Break Cloud Native DevOps and have seen some highly differing views on where the adoption of DevOps is. The Cloudbees article starts by saying that “Software delivery cycles are becoming faster thanks to DevOps-backed continuous integration/continuous delivery (CI/CD) as production pipelines are increasingly ported to scale with microservices on cloud-native environments.”