Knife-ec2 0.6.6 Release Candidate available for testing

Chef Infra (archive)
1

Ohai Chefs. A knife-ec2 gem release is finally upon us just in time for
Halloween and ready for you to try out. We’re planning a final release on
10/31. We’d 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/CHEF.

To test, you’ll need to do the following rather than a gem install (skip to
the end of the message if you’d like to know why):

gem install bundler # if it’s 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 knife-ec2@master: "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

*Gem testing note: Due to https://tickets.opscode.com/browse/CHEF-4696,
pre-release knife gems won’t 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
that’s being tested for a future release of Chef.

Thank you everyone.

-Adam

2

Great news,

I can see https://tickets.opscode.com/browse/KNIFE-154 is closed. Is there
a reason this is not included?

/Jeppe

On Wed, Oct 30, 2013 at 3:50 PM, Adam Edwards adamed@opscode.com wrote:

Ohai Chefs. A knife-ec2 gem release is finally upon us just in time for
Halloween and ready for you to try out. We’re planning a final release on
10/31. We’d 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/CHEF.

To test, you’ll need to do the following rather than a gem install (skip
to the end of the message if you’d like to know why):

gem install bundler # if it’s not already installed

git clone GitHub - chef/knife-ec2: Chef knife plug-in for AWS 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 knife-ec2@master: "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

*Gem testing note: Due to https://tickets.opscode.com/browse/CHEF-4696,
pre-release knife gems won’t 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
knife-ec2 | RubyGems.org | your community gem host. CHEF-4696 has a
fix that’s being tested for a future release of Chef.

Thank you everyone.

-Adam

3

Yes, it is there, so feel free to try it out. I generated the results below
from a query on resolution date, and that one issue had a resolution date
outside my chosen Window, despite being (apparently) resolved well within
it. I’ve done a scan for other similar issues and that’s the only one that
fits that – odd.

Good catch Jeppe, thank you – I’ve added it to the list in my reply.

From: Jeppe Nejsum Madsen [mailto:jeppe@ingolfs.dk]
Sent: Wednesday, October 30, 2013 3:02 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Knife-ec2 0.6.6 Release Candidate available for
testing

Great news,

I can see https://tickets.opscode.com/browse/KNIFE-154 is closed. Is there
a reason this is not included?

/Jeppe

On Wed, Oct 30, 2013 at 3:50 PM, Adam Edwards adamed@opscode.com wrote:

Ohai Chefs. A knife-ec2 gem release is finally upon us just in time for
Halloween and ready for you to try out. We’re planning a final release on
10/31. We’d 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, you’ll need to do the following rather than a gem install (skip to
the end of the message if you’d like to know why):

gem install bundler # if it’s 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 knife-ec2@master: "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 won’t 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
that’s being tested for a future release of Chef.

Thank you everyone.

-Adam