tknerr

#!/bin/bash

# This is the current stable release to default to, with Omnibus patch level (e.g. 10.12.0-1)
# Note that the chef template downloads 'x.y.z' not 'x.y.z-r' which should be a duplicate of the latest -r
use_shell=0

prerelease="false"

# Check whether a command exists - returns 0 if it does, 1 if it does not
exists() {

tknerr

#!/bin/bash

# This is the current stable release to default to, with Omnibus patch level (e.g. 10.12.0-1)
# Note that the chef template downloads 'x.y.z' not 'x.y.z-r' which should be a duplicate of the latest -r
use_shell=0

prerelease="false"

# Check whether a command exists - returns 0 if it does, 1 if it does not
exists() {

tknerr

#!/bin/ruby

require 'json'

# parse locked dependencies
json = JSON.parse(`berks list -F json`)
# transform them to metadata.rb format
deps = json['cookbooks'].map { |cb| %Q(depends "#{cb['name']}", "#{cb['version']}") }

# output for copy/paste to metadata

tknerr

package com.acme;

/**
 * alternative implementation of Bar, provided by com.acme, will be packaged alongside org.sample
 *
 * mappedName is required here, see http://stackoverflow.com/questions/7443306/javaee-6-javax-naming-namealreadyboundexception-use-rebind-to-override
 */
@Stateless(mappedName = "AlternativeBarBean")
public class AlternativeBarBean implements Bar {
...

tknerr

--------------------------------
Torben Knerr     • 19 days ago 
Nice post! Finally some clarification on the different interpretations of what an application, library or wrapper cookbook is :-)

I have one question about the environment cookbooks though: what if you have two different applications (e.g. my_face and your_face) requiring a different set of dependencies running in the same environment?

IMHO locking dependency versions and exposing the public recipes / attributes via metadata.rb is a great thing, but it should be doable on a finer-grained basis than environments, namely on a per application (e.g. my_face) basis. For this exact reason I'm not using chef environments to lock the dependency versions, but rather something like an "uber application cookbook" which combines the properties of an application cookbook and the locking and documentation of an environment cookbook.

What do you think? And what would be a good name for it?

tknerr

#!/bin/sh
# WARNING: REQUIRES /bin/sh
#
# - must run on /bin/sh on solaris 9
# - must run on /bin/sh on AIX 6.x
# - if you think you are a bash wizard, you probably do not understand
#   this programming language.  do not touch.
# - if you are under 40, get peer review from your elders.
#
# Author:: Tyler Cloke ([email protected])

tknerr

Vagrant / Chef Workshop

This DevOps / Infrastructure-As-Code with #Vagrant and #Chef workshop is all about automation, configuration management and being able to spin up everything from single servers to whole infrastructures at the push of a button.

Why?

Because your infrastructure should be:

• reliably and repeatedly reproducible
• described in a human readable DSL

tknerr

# show system info
cat /etc/lsb-release
uname -a

# set locale to UTF-8
locale -a
export LANG=C.UTF-8
export LC_ALL=C.UTF-8

# TMP is unset, makes vagrant use . instead

tknerr

source "https://supermarket.chef.io"

# manage direct dependencies here in Berksfile
cookbook "apache2", "1.10.4"

# dependency on self
cookbook "my-app", path: "."

tknerr

 INFO global: Vagrant version: 1.6.3
 INFO global: Ruby version: 2.0.0
 INFO global: RubyGems version: 2.0.14
 INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.3/bin/vagrant"
 INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/bin/../embedded"
 INFO global: VAGRANT_INSTALLER_VERSION="2"
 INFO global: VAGRANT_DETECTED_OS="Linux"
 INFO global: VAGRANT_INSTALLER_ENV="1"
 INFO global: VAGRANT_INTERNAL_BUNDLERIZED="1"
 INFO global: VAGRANT_LOG="debug"