Ohai Chefs. A knife-ec2 gem release is finally upon us just in time for Halloween and ready for you to try out. Were planning a final release on 10/31. Wed love it if you could give it a try on your favorite scenarios and report any issues you find with a ticket in https://tickets.opscode.com/browse/KNIFE.
To test, youll need to do the following rather than a gem install (skip to the end of the message if youd like to know why):
gem install bundler # if its not already installed
git clone https://github.com/opscode/knife-ec2
cd knife-c2
bundle install
bundle exec knife ec2 server list -c path-to-your-knife-config
The list of issues addressed in this knife-ec2 0.6.6 release is given below:
KNIFE-387 knife ec2 server create should accept bootstrap proxy option
KNIFE-364
: "Can not find bootstrap definition for "
KNIFE-349 Propagate "secret" and "secret-file" values for use when bootstrapping a new EC2 instance
KNIFE-346 Fix deprecations and test on Ruby 2.0.0
KNIFE-345 Updated README and gemspec
KNIFE-342 Include AZ in output and colorize flavor column for easy reading.
KNIFE-328 Remove Gemfile.lock
KNIFE-327 Travis CI
KNIFE-321 knife-ec2 does not inform the user of the default us-east region
KNIFE-294 Use credential file to specify access/secret keys
KNIFE-290 fix tags output
KNIFE-284 Unable to bootstrap windows node using ssh
KNIFE-265 knife-ec2 master breaks the knife command
KNIFE-254 Error::ECONNRESET (Connection reset by peer) when knife ec2 server create on 3G connection
KNIFE-253 knife-ec2 should be able to delete instance based on chef node name
KNIFE-161 Integrate WinRM bootstrap to allow knife ec2 server create to bootstrap a Windows instance
KNIFE-160 Add support for EC2 Placement Groups when creating new instances
KNIFE-154 Support new IAM Role feature in Knife EC2 Server Create
*Gem testing note: Due to https://tickets.opscode.com/browse/CHEF-4696, pre-release knife gems wont be loaded by recent versions of Chef, hence the bundler workaround given above. The ticket lists additional workarounds. If your version of Chef is not affected by the bug (Chef 11.4.0 or earlier), you can test the release candidate through a normal gem install since we have published the gem at http://rubygems.org/gems/knife-ec2/versions/0.6.6.rc.0. CHEF-4696 has a fix thats being tested for a future release of Chef.
Thank you everyone.
-Adam