You've heard about Devops and you like the idea. But how can you grow a Devops culture in your organization? In my series about Devops Protocols I talk about the fundamental building blocks for growing a Devops culture. No Manual Changes refers to the behavioural trait of not messing with any productive systems. Let's discuss … Continue reading Devops Protocol: No Manual Changes
Tag: configuration management
Chef: RVM + Ruby Enterprise Edition as Default Ruby
The opscode chef bootstrap installs Matz Ruby on the node automatically. There are cookbooks for installing ruby enterprise edition on a node, but they create a separate Ruby "universe" on your box: You will have to be very careful how you install gems to make sure they are used by either the default Ruby or … Continue reading Chef: RVM + Ruby Enterprise Edition as Default Ruby
How to Deploy Ruby on Rails With The Opscode Chef Application Cookbook
I already wrote about how to get started with the Opscode Chef Platform. In this article I want to show you a very elegant way to deploy a Ruby on Rails stack with Chef. One of the strengths of Chef is the decent set of available cookbooks. @jtimberman does an especially excellent job in writing … Continue reading How to Deploy Ruby on Rails With The Opscode Chef Application Cookbook
Getting Started With The Opscode Chef Platform – Configuration Management In The Cloud
In "The Moving Parts of Opscode Chef" there was an interesting discussion about the need of a highly available chef server if you want to use opscode chef as your configuration management tool of choice. Especially for small to medium sized enviroments running your own chef server is overkill. If you don't want to use … Continue reading Getting Started With The Opscode Chef Platform – Configuration Management In The Cloud
Automated Configuration Management With Opscode Chef: The Basic Moving Parts
The Moving Parts Managing your infrastructure with Opscode Chef involves a few moving parts you need to be aware of. As I found it quite hard to differentiate, I want to share the basics with you: Chef server There you manage all your nodes and roles. The chef server distributes cookbooks to the nodes. Chef … Continue reading Automated Configuration Management With Opscode Chef: The Basic Moving Parts
Sprinkle – Automated Infrastructure for the Rest of us
Automatically setting up and maintaining my servers is a must for me. Only if everything I install and configure on a server is scripted I'm sure I know what's there and that it stays that way. Having automated infrastructure enables me to schedule a critical setup change at 3 am and be on the safe … Continue reading Sprinkle – Automated Infrastructure for the Rest of us
Howto Get Started With Carpet
In my post about Carpet is a re-mix of existing configuration management solutions, I gave you a rough overview of the problems I tried to address with Carpet. In this article, I want to show you how you can set up a complete Ruby on Rails stack with only a few lines of configuration while … Continue reading Howto Get Started With Carpet
Configuration Management remixed: Introducing Carpet
Migrating our production environment from debian to OpenSolaris I wanted to simplify our configuration management recipes along the way. What I came up with is a mixture of Puppet style manifests and Capistrano backed ease of use in a new open source project called: Carpet. Building Your Infrastructure With Plain Capistrano Initially we've built our … Continue reading Configuration Management remixed: Introducing Carpet
Puppet or Capistrano – Use the Right Tool for the Job
This is a guest post by Andrew Shafer, who is part of Reductive Labs, the people behind Puppet. Reductive Labs is helping people build better systems with better tools and processes. Andrew has been on several Agile software teams in various capacities for the past few years, and has a passion for applying Agile principles … Continue reading Puppet or Capistrano – Use the Right Tool for the Job
Limiting Access to Test and Production Systems
How do you decide who in the company should have access to the test and production environments? Opening it up to everyone is one extreme which in today's security sensitive world is no longer an option. At the far other end, granting only one person access, while perhaps more secure (depending on who you've entrusted … Continue reading Limiting Access to Test and Production Systems
