Provision a AWS ec2 vm using chef<\/p>\n
Step 1: Install chefdk<\/a><\/strong><\/p>\n Step 2: Setup AWS Credentails<\/a><\/strong><\/p>\n Step X: Setup your knife config<\/a><\/strong><\/p>\n Step X: Make sure following is set and exported in env.<\/p>\n Step 3: Genrate a new repository using the chef generate command<\/strong> > chef generate repo chefdk-provision-demo Step 4: Generate a provision cookbook. This is the required name, and it must be in the current directory.<\/strong> Step 5: Edit the default recipe, $EDITOR provision\/recipes\/default.rb with following code…<\/strong><\/p>\n Understand the code: Step 6: Generate a Policyfile.rb and And edit its content, $EDITOR Policyfile.rb.<\/strong> Here we\u2019re simply getting the libuuid-user cookbook from Supermarket and applying the default recipe to the nodes that have this policy.<\/p>\n Step 7: The next step is to install the Policyfile. This generates the Policyfile.lock.json, and downloads the cookbooks to the cache, ~\/.chefdk\/cache\/cookbooks. If this isn\u2019t run, chef will complain, with a reminder to run it.<\/strong><\/p>\n > chef install<\/p>\n Step 8: Finally, we can provision a testing system with this policy:<\/p>\n > chef provision testing –sync -n debian-libuuid<\/p>\n Reference:<\/strong>AWS_ACCESS_KEY_ID=secrets AWS_SECRET_ACCESS_KEY=secrets AWS_DEFAULT_REGION=us-east-1 AWS_SSH_KEY=your_ssh_key_name AWS_ACCESS_KEY=secrets AWS_SECRET_KEY=secrets<\/code><\/pre>\n<\/code><\/pre>\n
\n<\/a><\/strong><\/p>\n
\n> cd chefdk-provision-demo<\/p>\n
\n> chef generate cookbook provision<\/p>\ncontext = ChefDK::ProvisioningData.context with_driver 'aws::us-west-2' options = { ssh_username: 'admin', use_private_ip_for_ssh: false, bootstrap_options: { key_name: 'jtimberman', image_id: 'ami-0d5b6c3d', instance_type: 'm3.medium', }, convergence_options: context.convergence_options, } machine context.node_name do machine_options options action context.action converge true end<\/pre>\n
\n> To break this down, first we get the ChefDK provisioning context that will pass in options to chef-provisioning.
\n> Then we tell chef-provisioning to use the AWS driver, and in the us-west-2 region.
\n> The options hash is used to setup the instance.
\n> We\u2019re using Debian 8, which uses the admin user to log in, an SSH key that exists in the AWS region, the actual AMI, and finally the instance type.
\n> Then, we\u2019re going to set the convergence options automatically from ChefDK. This is the important part that will ensure the node has the right run list.<\/p>\n
\n> chef generate policyfile
\n> vi policyfile.rb<\/p>\nname \"chefdk-provision-demo\" default_source :community run_list \"recipe[libuuid-user]\" cookbook \"libuuid-user\"<\/pre>\n
\nhttp:\/\/jtimberman.housepub.org\/blog\/2015\/05\/15\/quick-tip-chefdk-provision\/<\/a><\/p>\n\n