vagrant-openstack 0.0.4

data/lib/vagrant-openstack/errors.rb

@@ -0,0 +1,15 @@
+require "vagrant"
+
+module VagrantPlugins
+  module ProviderOpenStack
+    module Errors
+      class VagrantOpenStackError < Vagrant::Errors::VagrantError
+        error_namespace("vagrant_openstack.errors")
+      end
+
+      class RsyncError < VagrantOpenStackError
+        error_key(:rsync_error)
+      end
+    end
+  end
+end

data/lib/vagrant-openstack/plugin.rb

@@ -0,0 +1,71 @@
+begin
+      require "vagrant"
+rescue LoadError
+      raise "The Vagrant OpenStack plugin must be run within Vagrant."
+end
+
+# This is a sanity check to make sure no one is attempting to install
+# # this into an early Vagrant version.
+if Vagrant::VERSION < "1.1.0"
+    raise "The Vagrant OpenStack plugin is only compatible with Vagrant 1.1+"
+end
+
+module VagrantPlugins
+  module ProviderOpenStack
+    class Plugin < Vagrant.plugin("2")
+      name "OpenStack provider"
+      description <<-EOF
+      The OpenStack provider allows Vagrant to manage and control
+      OpenStack virtual machines.
+      EOF
+
+      provider(:openstack) do
+        setup_i18n
+        setup_logging
+
+        require_relative "provider"
+        Provider
+      end
+
+      config(:openstack, :provider) do
+        require_relative "config"
+        Config
+      end
+
+      # This initializes the internationalization strings.
+      def self.setup_i18n
+        I18n.load_path << File.expand_path("locales/en.yml", ProviderOpenStack.source_root)
+        I18n.reload!
+      end
+
+      # This sets up our log level to be whatever VAGRANT_LOG is.
+      def self.setup_logging
+        require "log4r"
+
+        level = nil
+        begin
+          level = Log4r.const_get(ENV["VAGRANT_LOG"].upcase)
+        rescue NameError
+          # This means that the logging constant wasn't found,
+          # which is fine. We just keep `level` as `nil`. But
+          # we tell the user.
+          level = nil
+        end
+
+        # Some constants, such as "true" resolve to booleans, so the
+        # above error checking doesn't catch it. This will check to make
+        # sure that the log level is an integer, as Log4r requires.
+        level = nil if !level.is_a?(Integer)
+
+        # Set the logging level on all "vagrant" namespaced
+        # logs as long as we have a valid level.
+        if level
+          logger = Log4r::Logger.new("vagrant_openstack")
+          logger.outputters = Log4r::Outputter.stderr
+          logger.level = level
+          logger = nil
+        end
+      end
+    end
+  end
+end

data/lib/vagrant-openstack/provider.rb

@@ -0,0 +1,52 @@
+require "log4r"
+
+module VagrantPlugins
+  module ProviderOpenStack
+    class Provider < Vagrant.plugin("2", :provider)
+      attr_reader :driver
+
+      def initialize(machine)
+        @machine = machine
+      end
+    
+      # @see Vagrant::Plugin::V1::Provider#action
+      def action(name)
+        # Attempt to get the action method from the Action class if it
+        # exists, otherwise return nil to show that we don't support the
+        # given action.
+        action_method = "action_#{name}"
+        return Action.send(action_method) if Action.respond_to?(action_method)
+        nil
+      end
+
+      def ssh_info
+        # Run a custom action called "read_ssh_info" which does what it
+        # says and puts the resulting SSH info into the `:machine_ssh_info`
+        # key in the environment.
+        env = @machine.action("read_ssh_info")
+        env[:machine_ssh_info]
+      end
+
+      def state
+        # Run a custom action we define called "read_state" which does
+        # what it says. It puts the state in the `:machine_state_id`
+        # key in the environment.
+        env = @machine.action("state")
+
+        state_id = env[:machine_state_id]
+
+        # Get the short and long description
+        short = I18n.t("vagrant_openstack.states.short_#{state_id}")
+        long  = I18n.t("vagrant_openstack.states.long_#{state_id}")
+
+        # Return the MachineState object
+        Vagrant::MachineState.new(state_id, short, long)
+      end
+
+      def to_s
+        id = @machine.id ? @machine.id : "new VM"
+        "OpenStack (#{id})"
+      end
+    end
+  end
+end

data/lib/vagrant-openstack/version.rb

@@ -0,0 +1,5 @@
+module VagrantPlugins
+    module ProviderOpenStack
+        VERSION = "0.0.4"
+    end
+end

data/locales/en.yml

@@ -0,0 +1,57 @@
+en:
+    vagrant_openstack:
+        associating_ip: |-
+            Associating floating ip %{ip} => %{id}
+
+        ready: |-
+          The server is ready!
+
+        vm_booted: |-
+            New VM created %{id} => %{name}
+
+        vm_building: |-
+            Waiting for the VM to be built
+
+        deleting: |-
+          Deleting the instance...
+
+        rsync_folder: |-
+            Rsyncing folder: %{hostpath} => %{guestpath}
+
+        finding_flavor: |-
+          Finding flavor for server...
+        finding_image: |-
+          Finding image for server...
+        launching_server: |-
+          Launching a server with the following settings...
+        waiting_for_build: |-
+          Waiting for the server to be built...
+        waiting_for_ssh: |-
+          Waiting for SSH to become available...
+        warn_insecure_ssh: |-
+          Warning! By not specifying a custom public/private keypair,
+          Vagrant is defaulting to use the insecure keypair that ships with
+          Vagrant. While this isn't much of a big deal for local development,
+          this is quite insecure for remote servers. Please specify a custom
+          public/private keypair.
+
+        states:
+          short_not_created: |-
+            not created
+          long_not_created: |-
+            The nova instance is not created. Run `vagrant up` to create it.
+
+          short_active: |-
+            running
+          long_active: |-
+            The nova instance is running. To stop this machine, you can run
+            `vagrant halt`. To destroy the machine, you can run `vagrant destroy`.
+
+        errors:
+            rsync_error: |-
+                There was an error when attemping to rsync a share folder.
+                Please inspect the error message below for more info.
+
+                Host path: %{hostpath}
+                Guest path: %{guestpath}
+                Error: %{stderr}

data/tmp/librarian/cache/source/chef/site/877777683730772c36b1e6a3fc3aa2c3/apache2/metadata.json

@@ -0,0 +1 @@
+{"average_rating":4.75,"maintainer":"opscode","versions":["http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_6_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_5_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_4_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_4_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_3_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_3_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_2_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_16","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_12","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_10","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_8","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_6","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_4","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_1_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_0_8","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_0_6","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_0_4","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_0_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_0_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_99_4","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_99_3","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_99_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_99_1","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_99_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_12_3","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_12_2","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_12_1","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_12_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_11_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_10_1","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_10_0","http://community.opscode.com/api/v1/cookbooks/apache2/versions/0_9_1"],"latest_version":"http://community.opscode.com/api/v1/cookbooks/apache2/versions/1_6_0","created_at":"2009-10-25T23:47:55Z","description":"Installs and configures all aspects of apache2 using Debian style symlinks with helper definitions","name":"apache2","updated_at":"2013-02-23T06:46:30Z","category":"Web Servers","external_url":"github.com/opscode-cookbooks/apache2"}

data/tmp/librarian/cache/source/chef/site/877777683730772c36b1e6a3fc3aa2c3/apache2/version-uri/a7ab7e6a4c7e38e585540241cf05880e/metadata.json

@@ -0,0 +1 @@
+{"license":"Apache 2.0","file":"http://s3.amazonaws.com/community-files.opscode.com/cookbook_versions/tarballs/3141/original/apache2.tgz?1361601921","updated_at":"2013-02-23T06:45:38Z","average_rating":null,"created_at":"2013-02-23T06:45:38Z","cookbook":"http://community.opscode.com/api/v1/cookbooks/apache2","version":"1.6.0","tarball_file_size":53624}

data/tmp/librarian/cache/source/chef/site/877777683730772c36b1e6a3fc3aa2c3/apache2/version-uri/a7ab7e6a4c7e38e585540241cf05880e/package/CHANGELOG.md

@@ -0,0 +1,150 @@
+## v1.6.0:
+
+* [COOK-2372] - apache2 mpm_worker: add ServerLimit attribute (default
+  to 16)
+
+## v1.5.0:
+
+**NOTE** The `mod_auth_openid` attributes are changed. The upstream
+  maintainer deprecated the older release versions, and the source
+  repository has releases available at specific SHA1SUM references.
+  The new attribute, `node['apache']['mod_auth_openid']['ref']` is
+  used to set this.
+
+* [COOK-2198] - `apache::mod_auth_openid` compiles from source, but
+  does not install make on debian/ubuntu
+* [COOK-2224] - version conflict between cucumber and other gems
+* [COOK-2248] - `apache2::mod_php5` uses `not_if` "which php" without
+  ensuring package 'which' is installed
+* [COOK-2269] - Set allow list for mod_status incase external monitor scripts need
+* [COOK-2276] - cookbook apache2 documentation regarding listening
+  ports doesn't match default attributes
+* [COOK-2296] - `mod_auth_openid` doesn't have tags/releases for the
+  version I need for features and fixes
+* [COOK-2323] - Add Oracle linux support
+
+## v1.4.2:
+
+* [COOK-1721] - fix logrotate recipe
+
+## v1.4.0:
+
+* [COOK-1456] - iptables enhancements
+* [COOK-1473] - apache2 does not disable default site when setting
+  "`default_site_enabled`" back to false
+* [COOK-1824] - the apache2 cookbook needs to specify which binary is
+  used on rhel platform
+* [COOK-1916] - Download location wrong for apache2 `mod_auth_openid`
+  >= 0.7
+* [COOK-1917] - Improve `mod_auth_openid` recipe to handle module
+  upgrade more gracefully
+* [COOK-2029] - apache2 restarts on every run on RHEL and friends,
+  generate-module-list on every run.
+* [COOK-2036] - apache2: Cookbook style
+
+## v1.3.2:
+
+* [COOK-1804] - fix `web_app` definition parameter so site can be
+  disabled.
+
+## v1.3.0:
+
+* [COOK-1738] - Better configuration for `mod_include` and some
+  overrides in `web_app` definition
+* [COOK-1470] - Change SSL Ciphers to Mitigate BEAST attack
+
+## v1.2.0:
+
+* [COOK-692] - delete package conf.d files in module recipes, for EL
+* [COOK-1693] - Foodcritic finding for unnecessary string interpolation
+* [COOK-1757] - platform_family and better style / usage practices
+
+## v1.1.16:
+
+re-releasing as .16 due to error on tag 1.1.14
+
+* [COOK-1466] - add `mod_auth_cas` recipe
+* [COOK-1609] - apache2 changes ports.conf twice per run when using
+  apache2::mod_ssl
+
+## v1.1.12:
+
+* [COOK-1436] - restore apache2 web_app definition
+* [COOK-1356] - allow ExtendedStatus via attribute
+* [COOK-1403] - add mod_fastcgi recipe
+
+## v1.1.10:
+
+* [COOK-1315] - allow the default site to not be enabled
+* [COOK-1328] - cookbook tests (minitest, cucumber)
+
+## v1.1.8:
+
+* Some platforms with minimal installations that don't have perl won't
+  have a `node['languages']['perl']` attribute, so remove the
+  conditional and rely on the power of idempotence in the package
+  resource.
+* [COOK-1214] - address foodcritic warnings
+* [COOK-1180] - add `mod_logio` and fix `mod_proxy`
+
+## v1.1.6:
+
+FreeBSD users: This release requires the `freebsd` cookbook. See README.md.
+
+* [COOK-1025] - freebsd support in mod_php5 recipe
+
+## v1.1.4:
+
+* [COOK-1100] - support amazon linux
+
+## v1.1.2:
+
+* [COOK-996] - apache2::mod_php5 can cause PHP and module API mismatches
+* [COOK-1083] - return string for v_f_p and use correct value for
+  default
+
+## v1.1.0:
+
+* [COOK-861] - Add `mod_perl` and apreq2
+* [COOK-941] - fix `mod_auth_openid` on FreeBSD
+* [COOK-1021] - add a commented-out LoadModule directive to keep apxs happy
+* [COOK-1022] - consistency for icondir attribute
+* [COOK-1023] - fix platform test for attributes
+* [COOK-1024] - fix a2enmod script so it runs cleanly on !bash
+* [COOK-1026] - fix `error_log` location on FreeBSD
+
+## v1.0.8:
+
+* COOK-548 - directory resource doesn't have backup parameter
+
+## v1.0.6:
+
+* COOK-915 - update to `mod_auth_openid` version 0.6, see __Recipes/mod_auth_openid__ below.
+* COOK-548 - Add support for FreeBSD.
+
+## v1.0.4:
+
+* COOK-859 - don't hardcode module paths
+
+## v1.0.2
+
+* Tickets resolved in this release: COOK-788, COOK-782, COOK-780
+
+## v1.0.0
+
+* Red Hat family support is greatly improved, all recipes except `god_monitor` converge.
+* Recipe `mod_auth_openid` now works on RHEL family distros
+* Recipe `mod_php5` will now remove config from package on RHEL family so it doesn't conflict with the cookbook's.
+* Added `php5.conf.erb` template for `mod_php5` recipe.
+* Create the run state directory for `mod_fcgid` to prevent a startup error on RHEL version 6.
+* New attribute `node['apache']['lib_dir']` to handle lib vs lib64 on RHEL family distributions.
+* New attribute `node['apache']['group']`.
+* Scientific Linux support added.
+* Use a file resource instead of the generate-module-list executed perl script on RHEL family.
+* "default" site can now be disabled.
+* web_app now has an "enable" parameter.
+* Support for dav_fs apache module.
+* Tickets resolved in this release: COOK-754, COOK-753, COOK-665, COOK-624, COOK-579, COOK-519, COOK-518
+* Fix node references in template for a2dissite
+* Use proper user and group attributes on files and templates.
+* Replace the anemic README.rdoc with this new and improved superpowered README.md :).

data/tmp/librarian/cache/source/chef/site/877777683730772c36b1e6a3fc3aa2c3/apache2/version-uri/a7ab7e6a4c7e38e585540241cf05880e/package/CONTRIBUTING.md

@@ -0,0 +1,257 @@
+# Contributing to Opscode Cookbooks
+
+We are glad you want to contribute to Opscode Cookbooks! The first
+step is the desire to improve the project.
+
+You can find the answers to additional frequently asked questions
+[on the wiki](http://wiki.opscode.com/display/chef/How+to+Contribute).
+
+You can find additional information about
+[contributing to cookbooks](http://wiki.opscode.com/display/chef/How+to+Contribute+to+Opscode+Cookbooks)
+on the wiki as well.
+
+## Quick-contribute
+
+* Create an account on our [bug tracker](http://tickets.opscode.com)
+* Sign our contributor agreement (CLA)
+[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L)
+(keep reading if you're contributing on behalf of your employer)
+* Create a ticket for your change on the
+  [bug tracker](http://tickets.opscode.com)
+* Link to your patch as a rebased git branch or pull request from the
+  ticket
+* Resolve the ticket as fixed
+
+We regularly review contributions and will get back to you if we have
+any suggestions or concerns.
+
+## The Apache License and the CLA/CCLA
+
+Licensing is very important to open source projects, it helps ensure
+the software continues to be available under the terms that the author
+desired. Chef uses the Apache 2.0 license to strike a balance between
+open contribution and allowing you to use the software however you
+would like to.
+
+The license tells you what rights you have that are provided by the
+copyright holder. It is important that the contributor fully
+understands what rights they are licensing and agrees to them.
+Sometimes the copyright holder isn't the contributor, most often when
+the contributor is doing work for a company.
+
+To make a good faith effort to ensure these criteria are met, Opscode
+requires a Contributor License Agreement (CLA) or a Corporate
+Contributor License Agreement (CCLA) for all contributions. This is
+without exception due to some matters not being related to copyright
+and to avoid having to continually check with our lawyers about small
+patches.
+
+It only takes a few minutes to complete a CLA, and you retain the
+copyright to your contribution.
+
+You can complete our contributor agreement (CLA)
+[ online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L).
+If you're contributing on behalf of your employer, have your employer
+fill out our
+[Corporate CLA](https://secure.echosign.com/public/hostedForm?formid=PIE6C7AX856)
+instead.
+
+## Ticket Tracker (JIRA)
+
+The [ticket tracker](http://tickets.opscode.com) is the most important
+documentation for the code base. It provides significant historical
+information, such as:
+
+* Which release a bug fix is included in
+* Discussion regarding the design and merits of features
+* Error output to aid in finding similar bugs
+
+Each ticket should aim to fix one bug or add one feature.
+
+## Using git
+
+You can get a quick copy of the repository for this cookbook by
+running `git clone
+git://github.com/opscode-coobkooks/COOKBOOKNAME.git`.
+
+For collaboration purposes, it is best if you create a Github account
+and fork the repository to your own account. Once you do this you will
+be able to push your changes to your Github repository for others to
+see and use.
+
+If you have another repository in your GitHub account named the same
+as the cookbook, we suggest you suffix the repository with -cookbook.
+
+### Branches and Commits
+
+You should submit your patch as a git branch named after the ticket,
+such as COOK-1337. This is called a _topic branch_ and allows users to
+associate a branch of code with the ticket.
+
+It is a best practice to have your commit message have a _summary
+line_ that includes the ticket number, followed by an empty line and
+then a brief description of the commit. This also helps other
+contributors understand the purpose of changes to the code.
+
+    [COOK-1757] - platform_family and style
+
+    * use platform_family for platform checking
+    * update notifies syntax to "resource_type[resource_name]" instead of
+      resources() lookup
+    * COOK-692 - delete config files dropped off by packages in conf.d
+    * dropped debian 4 support because all other platforms have the same
+      values, and it is older than "old stable" debian release
+
+Remember that not all users use Chef in the same way or on the same
+operating systems as you, so it is helpful to be clear about your use
+case and change so they can understand it even when it doesn't apply
+to them.
+
+### Github and Pull Requests
+
+All of Opscode's open source cookbook projects are available on
+[Github](http://www.github.com/opscode-cookbooks).
+
+We don't require you to use Github, and we will even take patch diffs
+attached to tickets on the tracker. However Github has a lot of
+convenient features, such as being able to see a diff of changes
+between a pull request and the main repository quickly without
+downloading the branch.
+
+If you do choose to use a pull request, please provide a link to the
+pull request from the ticket __and__ a link to the ticket from the
+pull request. Because pull requests only have two states, open and
+closed, we can't easily filter pull requests that are waiting for a
+reply from the author for various reasons.
+
+### More information
+
+Additional help with git is available on the
+[Working with Git](http://wiki.opscode.com/display/chef/Working+with+Git)
+wiki page.
+
+## Functional and Unit Tests
+
+This cookbook is set up to run tests under
+[Opscode's test-kitchen](https://github.com/opscode/test-kitchen). It
+uses minitest-chef to run integration tests after the node has been
+converged to verify that the state of the node.
+
+Test kitchen should run completely without exception using the default
+[baseboxes provided by Opscode](https://github.com/opscode/bento).
+Because Test Kitchen creates VirtualBox machines and runs through
+every configuration in the Kitchenfile, it may take some time for
+these tests to complete.
+
+If your changes are only for a specific recipe, run only its
+configuration with Test Kitchen. If you are adding a new recipe, or
+other functionality such as a LWRP or definition, please add
+appropriate tests and ensure they run with Test Kitchen.
+
+If any don't pass, investigate them before submitting your patch.
+
+Any new feature should have unit tests included with the patch with
+good code coverage to help protect it from future changes. Similarly,
+patches that fix a bug or regression should have a _regression test_.
+Simply put, this is a test that would fail without your patch but
+passes with it. The goal is to ensure this bug doesn't regress in the
+future. Consider a regular expression that doesn't match a certain
+pattern that it should, so you provide a patch and a test to ensure
+that the part of the code that uses this regular expression works as
+expected. Later another contributor may modify this regular expression
+in a way that breaks your use cases. The test you wrote will fail,
+signalling to them to research your ticket and use case and accounting
+for it.
+
+If you need help writing tests, please ask on the Chef Developer's
+mailing list, or the #chef-hacking IRC channel.
+
+## Code Review
+
+Opscode regularly reviews code contributions and provides suggestions
+for improvement in the code itself or the implementation.
+
+We find contributions by searching the ticket tracker for _resolved_
+tickets with a status of _fixed_. If we have feedback we will reopen
+the ticket and you should resolve it again when you've made the
+changes or have a response to our feedback. When we believe the patch
+is ready to be merged, we will tag the _Code Reviewed_ field with
+_Reviewed_.
+
+Depending on the project, these tickets are then merged within a week
+or two, depending on the current release cycle.
+
+## Release Cycle
+
+The versioning for Opscode Cookbook projects is X.Y.Z.
+
+* X is a major release, which may not be fully compatible with prior
+  major releases
+* Y is a minor release, which adds both new features and bug fixes
+* Z is a patch release, which adds just bug fixes
+
+A released version of a cookbook will end in an even number, e.g.
+"1.2.4" or "0.8.0". When development for the next version of the
+cookbook begins, the "Z" patch number is incremented to the next odd
+number, however the next release of the cookbook may be a major or
+minor incrementing version.
+
+Releases of Opscode's cookbooks are usually announced on the Chef user
+mailing list. Releases of several cookbooks may be batched together
+and announced on the [Opscode Blog](http://www.opscode.com/blog).
+
+## Working with the community
+
+These resources will help you learn more about Chef and connect to
+other members of the Chef community:
+
+* [chef](http://lists.opscode.com/sympa/info/chef) and
+  [chef-dev](http://lists.opscode.com/sympa/info/chef-dev) mailing
+  lists
+* #chef and #chef-hacking IRC channels on irc.freenode.net
+* [Community Cookbook site](http://community.opscode.com)
+* [Chef wiki](http://wiki.opscode.com/display/chef)
+* Opscode Chef [product page](http://www.opscode.com/chef)
+
+
+## Cookbook Contribution Do's and Don't's
+
+Please do include tests for your contribution. If you need help, ask
+on the
+[chef-dev mailing list](http://lists.opscode.com/sympa/info/chef-dev)
+or the
+[#chef-hacking IRC channel](http://community.opscode.com/chat/chef-hacking).
+Not all platforms that a cookbook supports may be supported by Test
+Kitchen. Please provide evidence of testing your contribution if it
+isn't trivial so we don't have to duplicate effort in testing. Chef
+10.14+ "doc" formatted output is sufficient.
+
+Please do indicate new platform (families) or platform versions in the
+commit message, and update the relevant ticket.
+
+If a contribution adds new platforms or platform versions, indicate
+such in the body of the commit message(s), and update the relevant
+COOK ticket. When writing commit messages, it is helpful for others if
+you indicate the COOK ticket. For example:
+
+    git commit -m '[COOK-1041] - Updated pool resource to correctly
+    delete.'
+
+Please do use [foodcritic](http://acrmp.github.com/foodcritic) to
+lint-check the cookbook. Except FC007, it should pass all correctness
+rules. FC007 is okay as long as the dependent cookbooks are *required*
+for the default behavior of the cookbook, such as to support an
+uncommon platform, secondary recipe, etc.
+
+Please do ensure that your changes do not break or modify behavior for
+other platforms supported by the cookbook. For example if your changes
+are for Debian, make sure that they do not break on CentOS.
+
+Please do not modify the version number in the metadata.rb, Opscode
+will select the appropriate version based on the release cycle
+information above.
+
+Please do not update the CHANGELOG.md for a new version. Not all
+changes to a cookbook may be merged and released in the same versions.
+Opscode will update the CHANGELOG.md when releasing a new version of
+the cookbook.