CHANGELOG.md

2.3.1 (2016-3-24)

2.3.0 (2015-9-28)

• Enhancement for multi template support
• Compatible with Chef 12

2.2.0 (2015-5-8)

• Some enhancement

2.1.0 (2014-9-15)

• Remove unnecessary Chef API calls and disable some Ohai plugins to improve Chef performance
• Add more UT
• Some minor enhancement

2.0.0 (2014-4-1)

• Rename gem to ironfan_serengeti
• if any key nodes (e.g. namenode/jobtracker) failed during bootstrapping, notify all nodes of cluster to stop bootstrapping.
• Save bootstrap error msg to each Chef Nodes
• Improve Ironfan UT coverage
• Some bug fix and enhancement

3.1.4.serengeti.1.1.0 (2013-11-11)

• Fix incompatibiliy in Ironfan after switching from Chef Server 10 to 11
• Use Chef 11 Partial Search API to reduce memory consumption and response time
• Enable SSL certificate validation between Chef Server and Chef nodes
• Add Support for Multi Network on VMs
• Some bug fix and enhancement

3.1.4.serengeti.1.0.0 (2013-8-2)

• Limit the number of concurrent bootstrapping nodes to 100 (configurable via knife[:maximum_concurrent_nodes] in .chef/knife.rb) to support large scale cluster provision (200+ nodes)
• Some bug fix and enhancement

3.1.4.serengeti.0.9 (2013-6-8)

• Add support for deploying CDH4 and PivotalHD YARN cluster
• Some bug fix and enhancement

3.1.4.serengeti.0.8 (2013-2-21)

• Add support for installing software packages using yum server
• Generate random password for user root and serengeti on each VM
• Add support for run 'knife cluster ssh cluster_name --no-cloud shell_commands'
• Several bug fix

3.1.4.serengeti.0.7 (2012-10-8)

• Setup password-less ssh login to cluster nodes
• Bootstrap all nodes in a cluster in paralell instead of facet by facet
• Clear service registry entries before bootstrapping cluster to ensure all nodes and its service daemons are synced up
• Avoid naming conflict between Chef roles and Ironfan generated cluster/facet roles
• Enable configuration for Hadoop Topology Rack Awareness and Hadoop Virtualization Extensions
• Several bug fix

3.1.4.serengeti.0.6 (2012-8-21)

• Add support for setting cluster level and facet level cluster configuration in cluster definition json file
• Report ERROR when bootstrapping a VM with no valid IP
• Report correct progress when decreasing the instance number
• Report correct progress when performing actions on a facet or a node
• Save package repository info (e.g. yum, apt) into cluster role
• Several bug fix

3.1.4.serengeti.0.5 (2012-6-13): Refactor Ironfan to work with VMware vSphere 5.0 in addition to EC2

• Refactor Ironfan code architecture to support multi cloud providers gracefully.
• Add full support for vSphere Cloud (i.e. create and manage VMs in VMware vCenter server).
• Add monitor function to Ironfan to enable Ironfan report progress of cluster operation and bootstrap to a RabbitMQ server.

v3.1.4: The inevitable post-launch tweaks

• 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

v3.1.1: I am Ironfan danananananabumbumbum

• '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.rb for 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-cloud and --no-chef to --cloud=false and --chef=false, opening up room for a later --cloud=rackspace etc.

• many doc fixes, thanks @sya!

---

---

v3.0.14:

Big important change:

ClusterChef is now Ironfan

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 kick runs 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-homebase now.
• When you knife cluster stop a node, it sets node[: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.md template
• minor fix to the new authorized_by calls

v3.0.11: We Raid at Dawn

• 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_role and facet_role in the run list. It now goes:
  • :first roles (cluster then facet)
  • :normal roles (cluster then facet)
  • special roles: cluster_role then facet_role
  • :last roles (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

v3.0.10: Cloud fixes

• 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-natty by default, and to customizable roles org_base, org_final and org_users (where org_base has a role_implication for membership in the systemwide org_base security 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

v3.0.6: schism of cookbooks and tools

• cookbooks all now live in their own repo, organized according to opscode standard.
• gem is now split into ironfan (the libraries) and ironfan-knife (the chef plugins)
• private_key was passing its block to super, with bad results

Changes from v2 => v3 [2011 October]

The below-described changes are still in progress

---

Ironfan underwent a major upgrade with the last several commits.

• the ironfan tools -- 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

Ironfan DSL Changes

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 :defaults did).

• cloud -- BREAKING a bare cloud statement is meaningless: the attributes may be abstract, but the values are different for every provider.

  • Anywhere you used to say cloud, say ec2: eg ec2.flavor('t1.micro') instead of cloud.flavor('t1.micro').

• chef_attributes -- BREAKING replaced by facet_role.override_attributes, facet_role.default_attributes (or those methods on cluster_role.)

• cluster_role_implication -- BREAKING now called role_implications, brought in by default.

• cluster.mounts_ephemeral_volumes is now cloud.mount_ephemerals; it is not done by default.

Knife Changes

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 kill only asks you once whether to kill things -- there's no more --really flag.
• Standalone args now all properly have --whatever and --no-whatever forms.
• BREAKING The sync and kill commands both agree that --chef and --cloud are how to restrict their attention.

Cookbook-affecting changes

• Standardized on node[:cluster_name], node[:facet_name] and node[: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] and node[:cluster_role] (use node[:facet_name]), node[:ironfan][:index] and node[:cluster_role_index] (use node[:facet_index]) .
• Ironfan family of cookbooks were updated accordingly.

hadoop_cluster cookbook

• 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.sh to format your HDFS
  • move the service state to '[:enable, :start]' and re-run chef client

Deprecated cookbooks

You must add "#{ironfan_path}/deprecated-cookbooks" to your cookbook_path in knife.rb if you would like to keep using

• cluster_ebs_volumes -- use mountable_volumes instead.