![]() I returned to my tdi user, changed into my chef-repo directory, and validated my setup as follows: $ cd ~/chef-repo I then assumed administrator privileges, ensured the /etc/chef directory existed, and copied the client.rb and validation.pem files into the /etc/chef directory, with the following result: # find /etc/chef/ I ran the following to create the files: $ knife configure client /tmp I read the manual page for knife configure and determined that knife configure client would read my knife.rb and create a client.rb file and a validation certificate. chef directory under my chef-repo and moved these three files under it: $ ls -1F chef-repo/.chef/ Verify that your user has the version of Ruby you desired. Update the node’s run list, replacing the irc and git recipes with the role you created. Upload the role and cookbooks to Hosted Chef. Read the documentation shipped with the chruby cookbook to understand which attributes can be set.Ĭreate a role that, in addition to the git and irc recipes, applies the system recipe from the chruby cookbook, and set the attributes to install the latest Ruby 1.9.3, and set it as default. Run chef-client again with the dna.json file created in the previous exercise.ĭownload the chruby, ark, and ruby_build cookbooks and place them in your chef-repo. Upload the cookbooks required to satisfy the run list to the Chef server. Run chef-client with the dna.json file created in the previous exercise. Look at the chef-client help page, and identify how to pass JSON to a chef-client run. Validate your setup by running knife client list. Read the knife configure documentation, and use it to create a client.rb file and validation certificate in /etc/chef. ![]() chef directory under your chef-repo directory, and place your two keys and knife.rb inside this directory. Navigate to the Hosted Chef Operations Console.Ĭreate an organization, if you don’t already have one, selecting the free tier.ĭownload your organization’s validation key.ĭownload the knife.rb configuration file for your organization.Ĭreate a. Create an Opscode community login (if you don’t have one already).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |