| #!/bin/bash | |
| ### BEGIN INIT INFO | |
| # INIT INFO | |
| # Provides: docker | |
| # Required-Start: networking | |
| # Required-Stop: networking | |
| # Default-Start: 2 3 4 5 | |
| # Default-Stop: 0 1 6 | |
| # Short-Description: docker |
Chef Metal now supports LXC! All the benefits of Metal, including idempotent, versioned, reusable cluster definitions can be realized. You can use LXC containers for testing, or you can use them as a part of your application stack. You can now write a Metal recipe like so:
chef-metal is still alpha software. People are experimenting with it and contributing to it, but it is still evolving.
require 'chef_metal_lxc'
There is a long standing issue in Ruby where the net/http library by default does not check the validity of an SSL certificate during a TLS handshake. Rather than deal with the underlying problem (a missing certificate authority, a self-signed certificate, etc.) one tends to see bad hacks everywhere. This can lead to problems down the road.
From what I can see the OpenSSL library that Rails Installer delivers has no certificate authorities defined. So, let's go fetch some from the curl website. And since this is for ruby, why don't we download and install the file with a ruby script?
| #!/usr/bin/perl | |
| # HAProxy Performance Statistics | |
| # by Steve Kamerman | |
| # | |
| # To use, pipe your HAProxy log with timing information (like "0/0/1/1/3 200") to | |
| # this script. It will output min, max, med, avg and a latency distribution graph. | |
| # | |
| # Info on timing logging in HAProxy: http://code.google.com/p/haproxy-docs/wiki/TimingEvents | |
| # |
| development: | |
| adapter: mysql2 | |
| encoding: utf8 | |
| database: my_database | |
| username: root | |
| password: |
| name "base" | |
| description "Baseline configuration for all systems." | |
| run_list( | |
| "recipe[ohai]", | |
| "recipe[chef-client::delete_validation]", | |
| "recipe[chef-client]", | |
| "recipe[zsh]", | |
| "recipe[git]", | |
| "recipe[users]", |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.
Install latest Ansible via pip + dependencies via a shell script
This file is used to install ansible in test kitchen when you set in the kitchen.yaml file
require_ansible_omnibus: true
By default test kitchen will always download and use the latest version of this install file.
WARNING: AS SOON AS YOU MERGE CODE HERE IT IS INSTANTLY AVAILABLE TO EVERYONE DOING OMNIBUS KITCHEN ANSIBLE INSTALLS:
The steps in this guide are available as an autobuild shell script
Because the OpenConnect package from Ubuntu is a bit outdated, and if you have a recent AnyConnect server, you need a newer OpenConnect to play with it.