Service-level response times are the same as for general-release features. Although this new feature/technology has undergone significant testing and is not expected to change significantly prior to general release, the use of this feature/technology is not recommended for production environments. You are encouraged to use this feature/technology for development and testing purposes only.
|Table of Contents|
Leading edge features
To set up a Chef Client in a public or private cloud environment. The Chef Client connects either to the Chef Server inside or outside RightScale or Hosted Chef from Opscode.
This tutorial describes the steps for launching one or more Chef Clients in a public/private cloud that connect to an existing Chef Server. Use this tutorial to see how you can use your existing Chef cookbooks and recipes in the RightScale platform without refactoring any of your code.
A private key is used to authenticate client-server connections. You will use this credential later in this tutorial when you set values for the required inputs. See Create a New Credential.
Follow these steps to add Chef Client to the deployment.
The next step is to define the properties of your Chef Client by entering values for inputs. It is best to do this at the deployment level. For a detailed explanation of how inputs are defined and used in Chef recipes and RightScripts, see Inheritance of Inputs.
To enter inputs for the Chef recipes that will run on your Chef Client, open the your deployment > Inputs tab and click Edit, then follow the directions below to configure input values. We recommend that you set up credentials for password values and any other sensitive data as shown in the examples.
Note: The following examples and sample values assume that you will connect the Chef Server inside or outside RightScale or Hosted Chef from Opscode. Please refer to the runbook for proper setup instructions.
|Input Name||Description||Example Value|
|Chef Server URL||Enter the URL to connect to the remote Chef Server.|| |
To connect to a Hosted Chef server, use the format:
For a standard or open source Chef Server, use the format:
|Chef Client Validation Name||Validation name, along with the private SSH key, is used to determine whether the Chef Client may register with the Chef Server. The validation_name located on the Server and in the Client configuration file must match.||text:ORG-validator|
|Private Key to Register the Chef Client with the Chef Server|| |
Private SSH key which will be used to authenticate the Chef Client on the remote Chef Server.
Select the credential that you created in an earlier step.
|Chef Company Name||Company name to be set in the Client configuration file. This attribute is applicable for Opscode Hosted Chef Server. The company name specified in both the Server and the Client configuration file must match. Example: MyCompany||text:MyCompany|
|Data Bag Secret Key||A secret key used to encrypt data bag items. It's recommended to create and use a credential for this sensitive value.||cred:CHEF_DATA_BAG_SECRET|
|Chef Client Environment||Specify the environment type for the Chef Client configuration file.||text:development|
|Chef Client Node Name||Name which will be used to authenticate the Chef Client on the remote Chef Server. Note: If nothing is specified, the instance FQDN will be used.|| |
|Set of Client Roles||Comma-separated list of roles which will be applied to this instance. The Chef Client will execute the roles in the order specified here.||text:webserver|
|JSON String used to override the first run of chef-client||A custom JSON string to be added to the first run of chef-client||text:recipe[ntp::default]|
|Chef Client Version||Specify the Chef Client version to match the requirements of your Chef Server.||text:10.24.0-1|
After configuring your inputs, launch the Chef Client. Refer to the instructions in Launch a Server if you are not already familiar with this process.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.