Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Reference Info > Dashboard Help Text > Cookbook_repo_sequences

Cookbook_repo_sequences

New

When you create a repository path (RepoPath) to your Chef cookbooks, simply provide a nickname. Later, you can add links to your Chef repositories.

Design > RepoPaths > New

Index

Chef is an open source configuration management and integration framework developed by Opscode. Chef allows you to write a collection of recipes and cookbooks that describe various server configurations. Chef cookbooks are the next level beyond OS distributions like RedHat or Ubuntu: a cookbook leverages the distro for getting the right bits onto the machine and then layers the operational know-how on top: how to configure everything and perform operational tasks. Add a link to a public/private Chef repository and then add recipes from your Chef cookbooks to your ServerTemplate just like you would add RightScripts.

Before you can add Chef recipes to a ServerTemplate, you must first create a RepoPath object that points to one or more Chef cookbook repositories. Currently, you can only associate a single RepoPath to a ServerTemplate.

Design > RepoPaths > Index

- -

Show

View detailed information about your Chef repositories.

Action Buttons

  • Clone - Create an editable copy of an existing RepoPath object. For example, if you want to extend the functionality of the RightScale Public RepoPath by adding your own cookbooks, you may want to clone it and then add your own private cookbook repository to the top of the list.
  • Commit - You can only commit a [HEAD] version of a RepoPath object. For production setups, ServerTemplates should always reference a committed RepoPath revision that contains cookbook repositories that have also been frozen to a specific tag/branch.
  • Delete - Permanently delete the RepoPath object.
Design > RepoPaths > Show

Revisions tab

The Revisions tab shows a history of all working revisions of a cookbook repository. Select a particular revision to view. A revision is a snapshot of a cookbook repository at a particular time whereas the HEAD revision is the working copy and only editable version.

Design > RepoPaths > Show > Revisions tab

Cookbook Repos tab

The Cookbook Repos tab shows a list of cookbook repositories associated with the RepoPath object. Add one or more paths to your cookbook repositories. You can add public or private repositories. The order of the listed repositories can affect what recipes and attributes are used. Cookbooks are used in order, and the first repository always wins. Therefore, you can use the order of repositories as a means for overwriting attributes. You should always list private cookbooks at the top of the list followed by public and Opscode cookbooks.

Add cookbook repo - When adding a path to a cookbook repository, you must specify the following:

  • URL - URL to the Chef repository. (e.g. git://github.com/opscode/cookbooks.git)
  • Type - Type of repository. At first release, please use git (not svn or download/tarball). RightScale can retrieve cookbooks from a git or svn server. You can also supply a URL to a compressed tar archive file, but it must uncompress into a valid cookbook repository. See Opscode for details. The supported compressed file extensions are '.bzip', '.bzip2', '.bz2', '.tgz', '.gzip' and '.gz'.
  • Tag/Branch - (Git/svn) Specify a specific tag or branch identifier.
    • Git - If left blank, the HEAD of the "master" branch will be used. Since tags are global in Git, you can either specify a branch name or tag. If you specify a specific branch, the HEAD version of that branch will be used.
  • Cookbooks path - The path in the repository to find the cookbooks. This is typically "cookbooks" for most cookbook repositories, including those from RightScale. If the cookbooks are located in the root directory, leave this field blank. Similarly, if they are located in a different directory, you must specify the correct path. (e.g. test/cookbooks).
  • Git SSH Key - (git) The Git SSH Key is only required for private cookbooks. You will need to provide Git with the public key and enter the private key in the Dashboard. Although you can use the Override dropdown option to enter it here, we recommend creating a credential for it.
  • Username - (svn/download) The username to access/unlock the repository. You can either choose an existing credential or use the overwrite option to manually enter the value.
  • Password - (svn/download) The password to access/unlock the repository. You can either choose an existing credential or use the overwrite option to manually enter the value.

Note: All cookbooks must supply a valid metadata file. See Opscode for details.

Design > RepoPaths > Show > Cookbook Repos tab

Info tab

The Info tab shows when you created a RepoPath object to your cookbook repositories in RightScale, as well as when the object's metadata was last updated. (It is not the time/date of when the cookbook repositories themselves were created or updated.) The Publishing status of the RepoPath object is also displayed. Currently, you cannot share a RepoPath object by itself. It can only be shared in the context of a ServerTemplate. Therefore, the only way to publish a RepoPath object is to use it in a private ServerTemplate and publish the template. When you import a ServerTemplate from the MultiCloud Marketplace, its RepoPath object will also be imported to your local collection (unless it already exists).

Design > RepoPaths > Show > Info tab

Xref tab

The Xref tab provides a cross-reference list of all ServerTemplates that are referencing the Chef Repsository and its cookbooks.

Design > RepoPaths > Show > Xref tab
You must to post a comment.
Last modified
23:25, 16 May 2013

Tags

This page has no custom tags.

Classifications

This page has no classifications.

Announcements

None


© 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.