Permalink
Commits on Feb 6, 2013
  1. Serialize :tags to state file

    jblaine committed Feb 6, 2013
    Should be harmless, and I'm looking to use it.
Commits on Dec 29, 2012
  1. Merge pull request #66 from jblaine/patch-2

    rtyler committed Dec 29, 2012
    Expose box.name as environ var. to script
  2. Merge pull request #67 from jblaine/patch-3

    rtyler committed Dec 29, 2012
    Mention "flavor" in example
  3. Merge pull request #69 from jblaine/patch-4

    rtyler committed Dec 29, 2012
    Show internal DNS as well for status
Commits on Dec 27, 2012
  1. Mention "flavor" in example

    jblaine committed Dec 27, 2012
    Had to look through source code to find that I could set this.
  2. Expose box.name as environ var. to script

    jblaine committed Dec 27, 2012
    Allows script to perform logic based on BLIMPY_SHIPNAME
Commits on Dec 19, 2012
  1. Fix a minor shell issue with the Puppet livery.

    rtyler committed Dec 19, 2012
    This will fail trying to chmod the entire puppet command string
    
        chmod: unrecognized option '--modulepath=./modules'
        Try `chmod --help' for more information.
Commits on Dec 12, 2012
  1. Merge pull request #63 from jblaine/patch-1

    rtyler committed Dec 12, 2012
    Ensure gempath.sh and livery command are executable
  2. Merge pull request #64 from jblaine/master

    rtyler committed Dec 12, 2012
    Support for RHEL
Commits on Oct 16, 2012
Commits on Oct 4, 2012
  1. Merge pull request #55 from cprice-puppet/bug/0.6.2/security-group-al…

    rtyler committed Oct 4, 2012
    …ready-exists
    
    Fix bug causing inconsistent values for security group names
Commits on Oct 3, 2012
  1. Fix bug causing inconsistent values for security group names

    Chris Price committed Oct 3, 2012
    Prior to this commit, when SecurityGroups#ensure_group was
    called with a list of ports that there was not yet a
    security group for, the array of ports would get wrapped
    in `Set.new` twice; once in the body of #group_id and once
    in the body of #ensure_group.
    
    It turns out that, based on the implementation of #group_id,
    there are cases when you'd get back a different group_id when
    you converted the array to a set twice.  So, e.g.:
    
        Zlib.crc32(Set.new([22,8140]).inspect) !=
    Zlib.crc32(Set.new(Set.new([22,8140])).inspect)
    
    but...
    
        Zlib.crc32(Set.new([22,8080]).inspect) ==
    Zlib.crc32(Set.new(Set.new([22,8080])).inspect)
    
    Good times.  This commit tweaks the tests so that they would
    repro this issue, and also cleans up the handling of the calls
    to `Set.new` so as to fix the bug.
Commits on Sep 3, 2012
  1. Version bump

    rtyler committed Sep 3, 2012
Commits on Aug 27, 2012
  1. Add a helper script to pull in the appropriate path on Debian-based h…

    rtyler committed Aug 27, 2012
    …osts for invoking the Puppet binary provided by the gem
Commits on Aug 25, 2012
  1. Add a minor optimization, don't bother bootstrapping Puppet if it's a…

    rtyler committed Aug 25, 2012
    …lready in our PATH
  2. Add a new built-in (and configurable) Puppet livery.

    rtyler committed Aug 25, 2012
    This will allow for easier bootstrapping and configuration of Puppet on a
    machine, e.g.:
    
        Blimpy.fleet do |f|
          f.add(:aws) do |s|
            s.livery = Blimpy::Livery::Puppet.configure |c|
              c.module_path = "test/modules" # This is relative to the Blimpfile's root directory
            end
          end
        end
    
    In a way, this should fix #47
Commits on Aug 23, 2012
  1. Move the concept of a Livery around to denote an actual class with mo…

    rtyler committed Aug 23, 2012
    …re "structure"
    
    This effectively breaks the crap out of existing Blimpfiles with a `ship.livery
    = :cwd` line, or something similar. I think it's worth it at this point.
    
    Liveries will have some access to the box object itself, so that API will need
    to remain consistent for some time. It's expected that every Livery will have
    at least:
    
        * setup_on(box)
        * preflight(box)
        * flight(box)
        * postflight(box)
    
    This should be enough for just about every livery to do what it needs to do
    with the created box. This should also allow (in the future) a Livery to
    express variables or other configuration information "outward" for the
    consumption of other Liveries.