Skip to content
Commits on Oct 5, 2012
  1. Ironfan.cluster() gives you back cluster if defined, does not overrid…

    …e it
    
    This makes its behavior consistent with gorillib collection behavior everywhere else.
    Philip (flip) Kromer committed Oct 4, 2012
  2. Specs around facet (does not help #183)

    dsl seems to handle override of facet instances just fine; error must lie elsewhere
    Philip (flip) Kromer committed Oct 4, 2012
Commits on Oct 3, 2012
  1. @temujin9
  2. @temujin9

    Version bump to 4.3.2

    temujin9 committed Oct 3, 2012
  3. @temujin9
  4. @temujin9
  5. @temujin9

    Version bump to 4.3.1

    temujin9 committed Oct 3, 2012
  6. @temujin9
Commits on Oct 2, 2012
  1. @temujin9
  2. @temujin9

    Version bump to 4.3.0

    temujin9 committed Oct 2, 2012
  3. @temujin9
  4. @temujin9
  5. @temujin9
  6. @temujin9
  7. @temujin9

    Version bump to 4.2.3

    temujin9 committed Oct 2, 2012
  8. @temujin9
  9. @temujin9

    Merge pull request #181 from nickmarden/nick/set_chef_environment_per…

    …_chef_semantics
    
    Use Chef::Node-friendly semantics for chef_environment
    temujin9 committed Oct 2, 2012
  10. @temujin9
  11. @temujin9
  12. @nickmarden

    Use Chef::Node-friendly semantics for chef_environment

    Chef::Node uses a single function #set_or_return to manage the chef_environment
    instance variable, but Ironfan::Provider::ChefServer::Node uses delegation
    through #chef_environment and #chef_environment=. Unfortunately, magic in the
    Chef mixins causes #chef_environment to go through the "correct" get/setter
    while the call to #chef_environment= gets stashed useless in self's Hash
    representation (rather than an instance variable of self). The net result is
    that the attempt to copy server.environment into a new Node's chef_environment
    attribute was getting silently dropped on the floor, and all new nodes were
    being created in the _default environment :-(
    
    This patch fixes that disconnect, and also allows nice folks to use symbols
    for their Chef environment names if that sort of thing makes them happy.
    nickmarden committed Oct 2, 2012
  13. @temujin9

    Start of serious VPC support - can launch, with correct groups, but f…

    …ails to correctly tweak those group's permissions
    temujin9 committed Oct 1, 2012
  14. @temujin9

    Cleaner messages on kill

    temujin9 committed Oct 1, 2012
Commits on Oct 1, 2012
  1. @temujin9
  2. @temujin9

    Version bump to 4.2.2

    temujin9 committed Oct 1, 2012
  3. @temujin9

    Merge remote-tracking branch 'origin/model_cleanup'

    Conflicts:
    	CHANGELOG.md
    	VERSION
    	ironfan.gemspec
    	lib/gorillib/resolution.rb
    	lib/ironfan.rb
    	lib/ironfan/dsl/facet.rb
    	lib/ironfan/provider/chef/client.rb
    	lib/ironfan/provider/chef/node.rb
    	lib/ironfan/provider/chef/role.rb
    	lib/ironfan/provider/ec2/ebs_volume.rb
    	lib/ironfan/provider/ec2/placement_group.rb
    	lib/ironfan/provider/ec2/security_group.rb
    	spec/spec_helper.rb
    temujin9 committed Oct 1, 2012
  4. @temujin9
  5. @temujin9

    Merge branch 'master' of github.com:infochimps-labs/ironfan into secu…

    …rity_group_rescue
    
    Conflicts:
    	lib/ironfan/provider/chef/client.rb
    	lib/ironfan/provider/chef/node.rb
    	lib/ironfan/provider/chef/role.rb
    	lib/ironfan/provider/ec2/ebs_volume.rb
    	lib/ironfan/provider/ec2/key_pair.rb
    	lib/ironfan/provider/ec2/machine.rb
    	lib/ironfan/provider/ec2/placement_group.rb
    	lib/ironfan/provider/ec2/security_group.rb
    temujin9 committed Oct 1, 2012
  6. @temujin9
  7. @temujin9
  8. @temujin9

    Version bump to 4.2.1

    temujin9 committed Oct 1, 2012
  9. @nickmarden
  10. @nickmarden
  11. Ignore deleting, deleted, or errored volumes in discovery

    Philip (flip) Kromer committed Sep 30, 2012
  12. Ignore deleting, deleted, or errored volumes in discovery

    Philip (flip) Kromer committed Sep 30, 2012
Commits on Sep 30, 2012
  1. knife cluster bootstrap sets Chef::Config[:environment] (fixes #148)

    I did a little dip into the bootstrap code; in order to make bootstrap work if there are multiple environments in the slice, you'll have to identify the subgroups with each environment and coordinate launching an ssh session on each.
    knife bootstrap prepares a single template file that draws on the Chef::Config[:environment] setting, and uses that as the command to a knife::Ssh session. at that point it's in Net::Ssh's hands. Anything we did that was non-uniform would lose parallel ssh sessions.
    
    Instead, knife checks the slice and, as long as all the machines you're bootstrapping live in the same environment, sets the Chef::Config and carries on. If you have multiple environments it explains and raises an exception.
    
    So you can still have a cluster with multiple environments, you just have to bootstrap them in groups by environment.
    Philip (flip) Kromer committed Sep 30, 2012
Something went wrong with that request. Please try again.