With CloudSlang you can orchestrate popular DevOps technologies, such as Docker and CoreOS in an agentless manner. You can also define custom workflows that are reusable, shareable and easy to understand.

Discover what top companies are using Learn about the tech stack behind some of the world's best software companies. See which tools and services they use, and how they're using them.

Why tools like Docker, Vagrant, and Ansible are hotter than ever

An excellent piece on leadership, mentoring and the soft skills required to help build a high functioning devops team.

... created a tool which will allows their customer-facing engineers to programmatically deploy infrastructure for new customers and to update the infrastructure of existing customers through a single, defined interface. This tool uses Consul as the foundation for continuous deployment to these environments. Consul's DNS, Key-Value store, and GUI have given DeltaForce a simple mechanism for reliably delivering software.

Security + DevOps Automatic Server Hardening

System administration is in a sad state. It in a mess. I'm not complaining about old-school sysadmins. They know how to keep systems running, manage update and upgrade paths. This rant is about containers, prebuilt VMs, and the incredible mess they cause because their concept lacks notions of "trust" and "upgrades".

A list of software and SaaS, PaaS etc offerings that have free tiers for devs

We have a variety of tutorial videos all related to DevOps. Our goal is to make the lives of SysAdmins everywhere easier by helping them use the tools that developers have been using for a long time, as well as helping developers realize how to solve some of the issues that Operations has traditionally had to deal with. If you have any comments or suggestions, please let us know!

DevOps Knowledge Base - This knowledge base includes topics of: Software Configuration Management, Continuous Delivery, Infrastructure Orchestration and DevOps

Until recently I was not able to clearly articulate what DevOps is. Then one day, when trying to describe what we are building at Nirmata to an investor, I said something to the effect of, "its all about enabling developers to perform operations, using automation". That made sense to them; and, I've since started using the following definition for DevOps: Developers doing Operations using Automation

The Shutl engineering team has been operating with a DevOps mentality for over two years. We started by rebuilding our infrastructure under Chef and embedding our operations engineers into our agile product development process. We made great progress and saw a big improvement in delivery and quality as all team members were responsible for getting things live and ensuring their long-term maintainability. But… we still had a silo. Only a few of our team were doing the lion's share of the work when it came to maintaining our infrastructure, and on-call duties were shared by just a small number of people. Over the past six months, we've changed that. So, rather than extol the virtues of this approach - there are plenty of articles doing that! - we thought we'd share some of the steps we took to make every engineer a DevOps engineer.

This checklist is comprised of 48 items you can use to gauge the maturity of your software delivery competency, and form a baseline to measure your future improvements. It's not meant to say "you're failing DevOps" or deprive you of a badge (make yourself a badge just for reading this!), but surface areas of potential improvement.