Skip to content

Latest commit

 

History

History
58 lines (40 loc) · 2.19 KB

README.md

File metadata and controls

58 lines (40 loc) · 2.19 KB
Raw

Build Status

chef-orchestrator-cookbook

This cookbook sets up and runs mysql-orchestror.

Presumptions

  • The backend mysql for orchestrator is going to run on the same server as orchestrator itself
  • That backend DB is going to use Percona MySQL which is setup using the chef-percona cookbook by Philiper
  • That you, the end user, own adding privileges for orchestrator to access your existing DB infrastructure
  • That you wrap this cookbook to use the CLI and add your production databases for discovery

Supported Platforms

  • Centos 6.5
  • Ubuntu 12.04

Attributes

Key Type Description Default
['orchestrator']['package']['version'] nil string version to install, nil provides latest (and will upgrade)
['orchestrator']['package']['url'] nil string URL to download the RPM from
['orchestrator']['package']['checksum'] nil string Checksum for the file provided by URL

Usage

Installation

Starting in version 2.1.0, the orchestrator cookbook now respects the version attribute. If set to nil (the default), the cookbook will perform the same steps as previous versions -- always upgrade to the latest version available via the repos available on a node. Setting this attribute to a specific package version will result in that version being installed. If you want to install the package from an internal source, you can also specify the url and optional checksum to download the orchestrator package.

orchestrator::default

Include orchestrator in your node's run_list:

{
  "run_list": [
    "recipe[orchestrator::default]"
  ]
}

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

License and Authors

Author:: Silvia Botros([email protected])