- Removed .delegates_to, .parallelize in favor of manual delegation (via .each) and .parallel, to remove assumption that calls must be in the context of the individual object (preparation for fixing bootstrapping)
- Adding cluster and facet roles to server run list (fixes #160)
- Fix for snapshot_id setting in cluster DSL
- Reinstated missing group_authorized capability
- Made launch correctly create and tag secondary EBS volumes
- Adding some more warnings of code smells where separation of concerns has become blurry
- Volume information should now be correctly saving to Chef nodes
- Keep flag now respected correctly for EBS root volumes
- Added Ironfan.parallelize, to run the basic cluster commands in parallel against their servers
- Make security_group range and group authorizations store only unique values
- Don't attempt to correlate the node volumes hash unless it's set
- RaidGroup declared by the DSL should get a name (so it can be indexed correctly)
- Volume.defaults is deprecated
- First pass at a provider plugin API, with EC2 as the working example.
- Removed role_implications: these can be handled by explicit ec2.security_group calls for now. See https://github.com/infochimps-labs/ironfan/wiki/Upgrading-to-v4 for more details.
- Added default_cloud flag to cloud statement (sets that cloud as the default one, if there are multiple clouds available), added use_cloud statement to compute components (cluster/facet/server) which overrides those defaults. There are plans for a command-line override, as well.
- Rebuilt the internal models of Ironfan to use gorillib's Field/Model/Builder architecture.
- #145: node attribues should be 'normal', not 'override' -- they don't show up as printed on the node otherwise
- #144: knife cluster ssh sets exit status based on commands' exit status
- #139: Fix detection of hostname in cluster_launch
- #136: Basic support for VPC
- cleanup of gemspec version constraints, including move to chef 0.10.10
- CentOS compatibility tweaks to several cookbooks
- Bootstrap scripts with env vars were being interpolated twice, so the bootstrap script quoting was changed to use
'(single-quote) semantics. I am a bit troubled, because I can't tell when this regression happened. I believe I introduced it while merging @gpaco's bootstrap scripts and didn't notice because the bug strikes most forcefully within the fenced-off 'Is ruby installed?' part. But there's a chance I just screwed over chef 0.10.04 users.
- Lots of documentation fixes, thanks @sya!
- Yard docs render pretty now (and quietly)
- Knife cluster kick now asks for sudo correctly -- enabling knife to do its password catching thing
- 'ClusterChef has been renamed 'Ironfan'
- The 'Metachef' cookbook has been renamed 'Silverware'
- The 'Minidash' cookbook has been renamed 'Minidash'
You should reload your chef server:
knife cookbook delete metachef dashpot
knife cookbook upload --all
rake roles
-
You can now launch a cluster locally with vagrant!
- follow the instructions in ironfan-ci
- set up a credentials set for your local machine (
cp -rp knife/example-credentials knife/local-credentials ; ln -nfs local-credentials knife/credentials) - customize its
knife-org.rbfor your chef server knife cluster vagrant up sandbox-simple
-
Deprecated 'knife cluster foo nikko web 0' (many args) in favor of 'knife cluster foo nikko-web-0' (single arg).
- the latter still works, it just yells a lot.
-
Am changing
--no-cloudand--no-chefto--cloud=falseand--chef=false, opening up room for a later--cloud=rackspaceetc. -
many doc fixes, thanks @sya!
Big important change:
Due to a polite request from outside, we are changing this project's name to not include the word 'Chef'.
It's now 'Ironfan', after Princess Iron Fan from the legend of Sun Wukong (Voyage to the West). The monkey hero Sun Wukong could not reach his destination without the help of the Princess's Iron Fan. The project helps you fan out across big iron in the sky -- and "You Can't Do B.I. without a Big Ironfan".
This weekend (2/18) everything in the ironfan family of everything will get regex-replaced as ironfan. We'll track both gems for the next push or so, but new versions of the gem will not be released after Feb 2012.
Other improvements/fixes:
- knife cluster proxy now accepts additional hosts to direct to proxy -- set Chef::Config[:cluster_proxy_patterns] to an array of additional glob-style strings. Use this with the route53 support for fun and profit - if your machines look like foo-server-0-internal.whatupchimpy.com, add Chef::Config[:cluster_proxy_patterns] = 'internal.whatupchimpy.com' to your knife-org.rb -- now you can browse securely to the private interface of any machine your target can.
- FIX #76 --
knife cluster kickruns chef-client if the service is stopped. Fixes #76 . Also knife ssh will at its end show a bright red list of machines whose commands exited with a non-zero exit code -- useful when 1 out of 30 machines fails a knife cluster kick. - A limited number of commands (ssh, show, kill) now run with no requirement of cloud anything (Relates to #28). Also worked around an annoying incompatibility with chef 0.10.8 (clients have a 'name') vs 0.10.40-and-prev (clients have a 'clientname'.
- examples all live in
ironfan-homebasenow. - When you
knife cluster stopa node, it setsnode[:state]to - the cookbook linter now has its own project: ironfan-scrubby. Along the way,
- some ability to cycle comments from the attributes file into node attribute docs in the
metadata.rb. - added helpful links to the
README.mdtemplate
- some ability to cycle comments from the attributes file into node attribute docs in the
- minor fix to the new
authorized_bycalls
- You can now assemble raid groups in the cluster definition:
- node metadata instructing the volumes recipe to build the raid volume
- marks the component volumes as non-mountable, in the appropriate raid group, etc
- Changed the order of
cluster_roleandfacet_rolein the run list. It now goes::firstroles (cluster then facet):normalroles (cluster then facet)- special roles:
cluster_rolethenfacet_role :lastroles (cluster then facet)
- knife cluster launch uses ClusterBootstrap, not knife's vanilla bootstrap.
- can now do group('group_that_wants').authorized_by_group('group_that_grants') so that in cluster A I can request access to cluster B without gaining its group myself.
- push the organization (if set) into the node metadata
- security groups are now created/updated in knife cluster sync. This can't help you apply then to a node afer launch though -- nothing can, the API doesn't allow it.
- clusters now all refer to an AMI named
ironfan-nattyby default, and to customizable rolesorg_base,org_finalandorg_users(whereorg_basehas a role_implication for membership in the systemwideorg_basesecurity group) - default facet instances is now 1 who knows why it wasn't always 1.
- minor linting of cluster before launching it
- bump to latest versions of oneiric AMIs thx @redbeard
- bootstrap fixes, oneiric support, more from @gchpaco
- cookbooks all now live in their own repo, organized according to opscode standard.
- gem is now split into
ironfan(the libraries) andironfan-knife(the chef plugins) - private_key was passing its block to super, with bad results
The below-described changes are still in progress
Ironfan underwent a major upgrade with the last several commits.
- the
ironfantools -- the DSL, knife plugins, and bootstrap scripts -- have been split out of the ironfan repo into a separate repo. - The tools are now available as a gem --
gem install ironfan - Cleaned up the code
- Standardized clusters & roles
- Standardized cookbooks
The following behaviors have been removed:
-
use-- BREAKING Was supposed to let me import another cluster definition into the one calling use. However, it didn't work as advertised, was clutter-y and was actively unpopular (issue #6).- Until the usage of derived clusters becomes clear, say
merge!on a hash instead. - We do default settings for you.
- We don't put in any default roles (as the old
use :defaultsdid).
- Until the usage of derived clusters becomes clear, say
-
cloud-- BREAKING a barecloudstatement is meaningless: the attributes may be abstract, but the values are different for every provider.- Anywhere you used to say
cloud, sayec2: egec2.flavor('t1.micro')instead ofcloud.flavor('t1.micro').
- Anywhere you used to say
-
chef_attributes-- BREAKING replaced byfacet_role.override_attributes,facet_role.default_attributes(or those methods oncluster_role.) -
cluster_role_implication-- BREAKING now called role_implications, brought in by default. -
cluster.mounts_ephemeral_volumesis nowcloud.mount_ephemerals; it is not done by default.
Several knife scripts saw name changes to their params. If you have external scripts that call knife cluster XXX please update them. No futher changes to parameters are expected.
knife cluster killonly asks you once whether to kill things -- there's no more--reallyflag.- Standalone args now all properly have
--whateverand--no-whateverforms. - BREAKING The sync and kill commands both agree that
--chefand--cloudare how to restrict their attention.
- Standardized on
node[:cluster_name],node[:facet_name]andnode[:facet_index]as the way to refer to the cluster, facet and server parts of a node's name. This replaces the way-too-many names for these:node[:ironfan][:facet]andnode[:cluster_role](usenode[:facet_name]),node[:ironfan][:index]andnode[:cluster_role_index](usenode[:facet_index]) . - Ironfan family of cookbooks were updated accordingly.
- The bootstrap recipes are gone. They may come back, but for now the dance is:
- bring up the cluster ; by default the service state for all the daemons is [:disable, :stop].
- run the
/etc/hadoop/conf/bootstrap_hadoop_namenode.shto format your HDFS - move the service state to '[:enable, :start]' and re-run chef client
You must add "#{ironfan_path}/deprecated-cookbooks" to your cookbook_path in knife.rb if you would like to keep using
cluster_ebs_volumes-- usemountable_volumesinstead.