Devops

Vagrant RackSpace Cloud Provider This is a Vagrant 1.1+ plugin that adds a RackSpace Cloud provider to Vagrant, allowing Vagrant to control and provision machines within RackSpace cloud. Note: This plugin requires Vagrant 1.1+.

"Microsoft provides virtual machine disk images to facilitate website testing in multiple versions of IE, regardless of the host operating system. With a single command, you can have IE6, IE7, IE8, IE9 and IE10 running in separate virtual machines."

Using Vagrant for Continuos Integration

"I have worked in environments where reacting was the "normal" way to approach issues and being proactive was just a waste of time... *facepalm* The seemingly simple idea of changing the workplace culture from reactive to proactive was hard to pitch, let alone implement on my own. 18 months ago, I knew there was a better way of doing things and I was determined to find something. I had been watching developers implement Agile Development processes with great envy and I was starting to see concepts that would have great outcomes if adopted in a traditional operations environment. Finally having something tangible to explore I started looking into Agile Operations, which led me DevOps. Lurking in the shadows for a while, I digested as much as I could of the DevOps movement. I thought it was  time to talk to some of the developers and get them on board. 6 months on and here we are... "

The DevOps team is "a growing group of people practicing a new way of combining development and system administration for more speed, quality, revenues and fun."

Elegant deployment with Fabric and Puppet. Loom does the stuff Puppet doesn't do well or at all: bootstrapping machines, giving them roles, deploying Puppet code and installing reusable Puppet modules. It's useful for both serverless and master/agent Puppet installations.

DevOps is evolving from what started as little more than a rally cry, into a culture for continuous delivery of IT services. As more pieces of the puzzle fall into place, we understand that DevOps is primarily a matter of human collaboration -- assisted, but not encompassed by, certain tools and technologies. This essay is my take on DevOps, and why I think it is about embracing distributed, autonomous operational methods that support scalable human-computer processes.

An Opscode Chef knife plugin to manage Chef Servers. Currently only bootstrapping new Chef Servers is supported (on Amazon's EC2) but node data backup and restore is planned.

Interview with Patrick Debois

Kibana is an open source (MIT License), browser based interface to Logstash and ElasticSearch. Once you have those in place, Kibana is a breeze to install and configure (really, I swear). And as you'll see below, none too hard to operate. Check out the screenshots for an idea of what Kibana is all about.

This is the official Opscode Knife plugin for HP Cloud. This plugin gives knife the ability to create, bootstrap and manage instances in the HP Cloud.

Juju is DevOps DistilledTM. Through the use of charms, juju provides you with shareable, re-usable, and repeatable expressions of DevOps best practices. You can use them unmodified, or easily change and connect them to fit your needs. Deploying a charm is similar to installing a package on Ubuntu: ask for it and it's there, remove it and it's completely gone.

Vagrant automates creation and provisioning of virtual machines within VirtualBox via the command line, whilst also allowing for easy distribution and reuse across multiple projects. In this article, I'm going to look at how it can make life considerably easier when dealing with development environments.

Webistrano is a easy-to-use graphical deployment tool. It is based on the deployment tool Capistrano and offers a substantial graphic interface including user-management and logging. It lets you manage projects and their stages like test, production, and staging with different settings. Those stages can then be deployed with Capistrano through Webistrano.

Whoever has used Puppet on production servers has probably lived, at least once, the uncomfortable situation when a change on Puppet manifests has introduced "unwanted effects" on target nodes if not real failures.