- From: Tyler Ball <
>
- To:
,
- Subject: [chef-dev] Re: [chef] kitchen-ec2 0.9.0 released
- Date: Thu, 21 May 2015 11:50:13 -0700
I just released 0.9.1 which includes the two PRs referenced below. The CHANGELOG has been copied below: • Pull Request #124: AWS SDK V2 returns instance.public_dns_name as empty string instead of nil, and we were only checking for nil. Caused timeouts trying to connect. (@tyler-ball) • Fixed regression: Adding back `interface` config value that I accidently removed, code is now in line with README.
• Pull Request #125: When specifying associate_public_ip we must send the subnet (if provided) in the network_interfaces section of the payload instead of the main section. (@tyler-ball) • Fixed regression: Accidently renamed config `associate_public_ip` to `associate_public_ip_address`, reverting.
• Fixed regression: Accidently renamed config `iam_profile_name` to `iam_instance_profile`, reverting.
-T On May 21, 2015, at 9:24 AM, Tyler Ball <
" class="">
> wrote:
I’ve opened up 2 PRs ( #125 and #124) to address #1, #2 - there will be a patch fix incoming as soon as those are fixed. I’ll look into the other issues you referenced.
You can include driver-specific information under the provisioning hash. For example,
driver: subnet_id: subnet-12345 ... platforms: - ubuntu 14.04 driver: security_group_ids: [“sg-abc”] - centos-6.4 driver: security_group_ids: [“sg-def”]
I don’t think there is a regular chef-client provisioner included in base Test Kitchen, but I think someone may have written one at some point...
-T On May 20, 2015, at 3:45 PM, Yoshi Spendiff <
" class="">
> wrote:
Hi Tyler,
I'm having a few issues. 1. IAM profiles don't assign, there's another email thread about that 2. associate_public_ip_address doesn't work for a VPC instance, there's a github issue for that 3. I get asked for a password as soon as the instance is 'ready,' even if there's no ssh connection available (there's no public IP address and I have interface: public in the .yml file). I'm not sure why it's even asking for a password when I have ssh_key set under the transport section of the .yml file. 4. availability_zone is asking for a full path instead of a letter, but this is not needed anyway as the subnet should define that. There's another github issue for that I just started trying this out as the inability to quickly run vagrant provision when using vagrant-ec2 is driving me nuts, so I have a couple of questions about usage too: 1. Is it possible to put some settings under the suites section of the .yml file instead of under the driver? Specifically I'm asking about security groups and an iam role but I think subnet-id could be useful too. I'm trying to use this to test a role cookbook with a couple of role recipes and in actuality these roles would have different security groups and iam roles (I know the best practice is one cookbook per role but that's another story). 2. Is there a chef-client provisioner or only chef-solo or chef-zero?
|
Archive powered by MHonArc 2.6.16.