option in knife ec2 for specifying block-device-mapping ?
I would like to specify the block device mapping (—block-device-mapping in the ec2-run-instances command) for ec2 machines in the “knife ec2 create command”. I don’t see an option for this in the help.
newbie: support both AWS and ESX VM targets?
I’ve just signed up to the freebie version of Chef and want to validate that the tool can handle my basic requirement.
I have a web app that includes Tomcat based Java web apps with a SQL-Server database backend. I’m looking for a cloud deployment/config management tool that allows me to build deployment scripts that will work against either internal vmWare ESX virtual machine or external AWS targets. Can Chef handle this?
If so. are there any idiot level tutorials available to explain how to achieve this?
How to install aws-sdk gem and use it at the same time?
I am relatively new to Chef, but have a built a few working modules and love it. I am trying to integrate with AWS and use the AWS-SDK for Ruby, so that I can create script that can be run in Chef as well as stand-alone. My problem is that I cannot figure out how to get Chef to recognize or install the aws-sdk rubygem. I have tried
but this runs before the packages required to build the gem are installed. I am sure that I am missing something simple and obvious, but I cannot figure out what it is.
Any help would be greatly appreciated.
Bootstrapping EC2 instance from Chef server at AWS
I am running a Chef server at AWS in the us-east region. I have no problem boostrapping and running chef-client on servers created in the us-east region, but I am unable to launch instances in the us-west region using my Chef server in the us-east region. The reason being that the instances are communicating using the internal AWS ip addressing for the region. And the AWS regions do not talk to each other internally. I can install the chef-client and then modify the client.rb file to point to the external IP of my Chef server. But that is a manual process.
Anyone know how to pre-modify the client.rb file before bootstrapping an instance?? Or find a way to specify what client.rb file is installed depending on the AWS region???