vagabond 0.2.8 → 0.2.10

data/lib/vagabond/cookbooks/apt/CONTRIBUTING

@@ -1,29 +0,0 @@
-If you would like to contribute, please open a ticket in JIRA:
-
-* http://tickets.opscode.com
-
-Create the ticket in the COOK project and use the cookbook name as the
-component.
-
-For all code contributions, we ask that contributors sign a
-contributor license agreement (CLA). Instructions may be found here:
-
-* http://wiki.opscode.com/display/chef/How+to+Contribute
-
-When contributing changes to individual cookbooks, please do not
-modify the version number in the metadata.rb. Also 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
-handle the version updates during the release process. You are welcome
-to correct typos or otherwise make updates to documentation in the
-README.
-
-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.'
-
-In the ticket itself, it is also helpful if you include log output of
-a successful Chef run, but this is not absolutely required.

data/lib/vagabond/cookbooks/apt/LICENSE

@@ -1,201 +0,0 @@
-                              Apache License
-                        Version 2.0, January 2004
-                     http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-   "License" shall mean the terms and conditions for use, reproduction,
-   and distribution as defined by Sections 1 through 9 of this document.
-
-   "Licensor" shall mean the copyright owner or entity authorized by
-   the copyright owner that is granting the License.
-
-   "Legal Entity" shall mean the union of the acting entity and all
-   other entities that control, are controlled by, or are under common
-   control with that entity. For the purposes of this definition,
-   "control" means (i) the power, direct or indirect, to cause the
-   direction or management of such entity, whether by contract or
-   otherwise, or (ii) ownership of fifty percent (50%) or more of the
-   outstanding shares, or (iii) beneficial ownership of such entity.
-
-   "You" (or "Your") shall mean an individual or Legal Entity
-   exercising permissions granted by this License.
-
-   "Source" form shall mean the preferred form for making modifications,
-   including but not limited to software source code, documentation
-   source, and configuration files.
-
-   "Object" form shall mean any form resulting from mechanical
-   transformation or translation of a Source form, including but
-   not limited to compiled object code, generated documentation,
-   and conversions to other media types.
-
-   "Work" shall mean the work of authorship, whether in Source or
-   Object form, made available under the License, as indicated by a
-   copyright notice that is included in or attached to the work
-   (an example is provided in the Appendix below).
-
-   "Derivative Works" shall mean any work, whether in Source or Object
-   form, that is based on (or derived from) the Work and for which the
-   editorial revisions, annotations, elaborations, or other modifications
-   represent, as a whole, an original work of authorship. For the purposes
-   of this License, Derivative Works shall not include works that remain
-   separable from, or merely link (or bind by name) to the interfaces of,
-   the Work and Derivative Works thereof.
-
-   "Contribution" shall mean any work of authorship, including
-   the original version of the Work and any modifications or additions
-   to that Work or Derivative Works thereof, that is intentionally
-   submitted to Licensor for inclusion in the Work by the copyright owner
-   or by an individual or Legal Entity authorized to submit on behalf of
-   the copyright owner. For the purposes of this definition, "submitted"
-   means any form of electronic, verbal, or written communication sent
-   to the Licensor or its representatives, including but not limited to
-   communication on electronic mailing lists, source code control systems,
-   and issue tracking systems that are managed by, or on behalf of, the
-   Licensor for the purpose of discussing and improving the Work, but
-   excluding communication that is conspicuously marked or otherwise
-   designated in writing by the copyright owner as "Not a Contribution."
-
-   "Contributor" shall mean Licensor and any individual or Legal Entity
-   on behalf of whom a Contribution has been received by Licensor and
-   subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   copyright license to reproduce, prepare Derivative Works of,
-   publicly display, publicly perform, sublicense, and distribute the
-   Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   (except as stated in this section) patent license to make, have made,
-   use, offer to sell, sell, import, and otherwise transfer the Work,
-   where such license applies only to those patent claims licensable
-   by such Contributor that are necessarily infringed by their
-   Contribution(s) alone or by combination of their Contribution(s)
-   with the Work to which such Contribution(s) was submitted. If You
-   institute patent litigation against any entity (including a
-   cross-claim or counterclaim in a lawsuit) alleging that the Work
-   or a Contribution incorporated within the Work constitutes direct
-   or contributory patent infringement, then any patent licenses
-   granted to You under this License for that Work shall terminate
-   as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-   Work or Derivative Works thereof in any medium, with or without
-   modifications, and in Source or Object form, provided that You
-   meet the following conditions:
-
-   (a) You must give any other recipients of the Work or
-       Derivative Works a copy of this License; and
-
-   (b) You must cause any modified files to carry prominent notices
-       stating that You changed the files; and
-
-   (c) You must retain, in the Source form of any Derivative Works
-       that You distribute, all copyright, patent, trademark, and
-       attribution notices from the Source form of the Work,
-       excluding those notices that do not pertain to any part of
-       the Derivative Works; and
-
-   (d) If the Work includes a "NOTICE" text file as part of its
-       distribution, then any Derivative Works that You distribute must
-       include a readable copy of the attribution notices contained
-       within such NOTICE file, excluding those notices that do not
-       pertain to any part of the Derivative Works, in at least one
-       of the following places: within a NOTICE text file distributed
-       as part of the Derivative Works; within the Source form or
-       documentation, if provided along with the Derivative Works; or,
-       within a display generated by the Derivative Works, if and
-       wherever such third-party notices normally appear. The contents
-       of the NOTICE file are for informational purposes only and
-       do not modify the License. You may add Your own attribution
-       notices within Derivative Works that You distribute, alongside
-       or as an addendum to the NOTICE text from the Work, provided
-       that such additional attribution notices cannot be construed
-       as modifying the License.
-
-   You may add Your own copyright statement to Your modifications and
-   may provide additional or different license terms and conditions
-   for use, reproduction, or distribution of Your modifications, or
-   for any such Derivative Works as a whole, provided Your use,
-   reproduction, and distribution of the Work otherwise complies with
-   the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-   any Contribution intentionally submitted for inclusion in the Work
-   by You to the Licensor shall be under the terms and conditions of
-   this License, without any additional terms or conditions.
-   Notwithstanding the above, nothing herein shall supersede or modify
-   the terms of any separate license agreement you may have executed
-   with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-   names, trademarks, service marks, or product names of the Licensor,
-   except as required for reasonable and customary use in describing the
-   origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-   agreed to in writing, Licensor provides the Work (and each
-   Contributor provides its Contributions) on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-   implied, including, without limitation, any warranties or conditions
-   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-   PARTICULAR PURPOSE. You are solely responsible for determining the
-   appropriateness of using or redistributing the Work and assume any
-   risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-   whether in tort (including negligence), contract, or otherwise,
-   unless required by applicable law (such as deliberate and grossly
-   negligent acts) or agreed to in writing, shall any Contributor be
-   liable to You for damages, including any direct, indirect, special,
-   incidental, or consequential damages of any character arising as a
-   result of this License or out of the use or inability to use the
-   Work (including but not limited to damages for loss of goodwill,
-   work stoppage, computer failure or malfunction, or any and all
-   other commercial damages or losses), even if such Contributor
-   has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-   the Work or Derivative Works thereof, You may choose to offer,
-   and charge a fee for, acceptance of support, warranty, indemnity,
-   or other liability obligations and/or rights consistent with this
-   License. However, in accepting such obligations, You may act only
-   on Your own behalf and on Your sole responsibility, not on behalf
-   of any other Contributor, and only if You agree to indemnify,
-   defend, and hold each Contributor harmless for any liability
-   incurred by, or claims asserted against, such Contributor by reason
-   of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS
-
-APPENDIX: How to apply the Apache License to your work.
-
-   To apply the Apache License to your work, attach the following
-   boilerplate notice, with the fields enclosed by brackets "[]"
-   replaced with your own identifying information. (Don't include
-   the brackets!)  The text should be enclosed in the appropriate
-   comment syntax for the file format. We also recommend that a
-   file or class name and description of purpose be included on the
-   same "printed page" as the copyright notice for easier
-   identification within third-party archives.
-
-Copyright [yyyy] [name of copyright owner]
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/lib/vagabond/cookbooks/apt/README.md

@@ -1,243 +0,0 @@
-Description
-===========
-
-This cookbook includes recipes to execute apt-get update to ensure the
-local APT package cache is up to date. There are recipes for managing
-the apt-cacher-ng caching proxy and proxy clients. It also includes a
-LWRP for managing APT repositories in /etc/apt/sources.list.d as well as
-an LWRP for pinning packages via /etc/apt/preferences.d.
-
-Requirements
-============
-
-Version 2.0.0+ of this cookbook requires **Chef 11.0.0** or later.
-
-If your Chef version is earlier than 11.0.0, use version 1.10.0 of
-this cookbook.
-
-See [COOK-2258](http://tickets.opscode.com/browse/COOK-2258) for more
-information on this requirement.
-
-Version 1.8.2 to 1.10.0 of this cookbook requires **Chef 10.16.4** or
-later.
-
-If your Chef version is earlier than 10.16.4, use version 1.7.0 of
-this cookbook.
-
-See [CHEF-3493](http://tickets.opscode.com/browse/CHEF-3493) and
-[this code comment](http://bit.ly/VgvCgf) for more information on this
-requirement.
-
-## Platform
-
-* Debian
-* Ubuntu
-
-May work with or without modification on other Debian derivatives.
-
-Recipes
-=======
-
-## default
-
-This recipe installs the `update-notifier-common` package to provide
-the timestamp file used to only run `apt-get update` if the cache is
-more than one day old.
-
-This recipe should appear first in the run list of Debian or Ubuntu
-nodes to ensure that the package cache is up to date before managing
-any `package` resources with Chef.
-
-This recipe also sets up a local cache directory for preseeding packages.
-
-## cacher-ng
-
-Installs the `apt-cacher-ng` package and service so the system can
-provide APT caching. You can check the usage report at
-http://{hostname}:3142/acng-report.html. The `cacher-ng` recipe
-includes the `cacher-client` recipe, so it helps seed itself.
-
-## cacher-client
-
-Configures the node to use the `apt-cacher-ng` server as a client. If you
-want to restrict your node to using the `apt-cacher-ng` server in your
-Environment, set `['apt']['cacher-client']['restrict_environment']` to `true`.
-
-To use a cacher server (or standard proxy server) not available via search
-set the atttribute `['apt']['cacher-ipaddress']` and for a custom port
-set `['apt']['cacher_port']`.
-
-Resources/Providers
-===================
-
-## Managing repositories
-
-This LWRP provides an easy way to manage additional APT repositories.
-Adding a new repository will notify running the `execute[apt-get-update]`
-resource immediately.
-
-### Actions
-
-- :add: creates a repository file and builds the repository listing
-- :remove: removes the repository file
-
-### Attribute Parameters
-
-- repo_name: name attribute. The name of the channel to discover
-- uri: the base of the Debian distribution
-- distribution: this is usually your release's codename...ie something
-  like `karmic`, `lucid` or `maverick`
-- components: package groupings..when it doubt use `main`
-- arch: constrain package to a particular arch like `i386`, `amd64` or
-  even `armhf` or `powerpc`. Defaults to nil.
-- deb_src: whether or not to add the repository as a source repo as
-  well - value can be `true` or `false`, default `false`.
-- keyserver: the GPG keyserver where the key for the repo should be retrieved
-- key: if a `keyserver` is provided, this is assumed to be the
-  fingerprint, otherwise it can be either the URI to the GPG key for
-  the repo, or a cookbook_file.
-- key_proxy: if set, pass the specified proxy via `http-proxy=` to GPG.
-- cookbook: if key should be a cookbook_file, specify a cookbook where
-  the key is located for files/default. Defaults to nil, so it will
-  use the cookbook where the resource is used.
-
-### Examples
-
-    # add the Zenoss repo
-    apt_repository "zenoss" do
-      uri "http://dev.zenoss.org/deb"
-      components ["main","stable"]
-    end
-
-    # add the Nginx PPA; grab key from keyserver
-    apt_repository "nginx-php" do
-      uri "http://ppa.launchpad.net/nginx/php5/ubuntu"
-      distribution node['lsb']['codename']
-      components ["main"]
-      keyserver "keyserver.ubuntu.com"
-      key "C300EE8C"
-    end
-
-    # add the Nginx PPA; grab key from keyserver, also add source repo
-    apt_repository "nginx-php" do
-      uri "http://ppa.launchpad.net/nginx/php5/ubuntu"
-      distribution node['lsb']['codename']
-      components ["main"]
-      keyserver "keyserver.ubuntu.com"
-      key "C300EE8C"
-      deb_src true
-    end
-
-    # add the Cloudkick Repo
-    apt_repository "cloudkick" do
-      uri "http://packages.cloudkick.com/ubuntu"
-      distribution node['lsb']['codename']
-      components ["main"]
-      key "http://packages.cloudkick.com/cloudkick.packages.key"
-    end
-
-    # add the Cloudkick Repo with the key downloaded in the cookbook
-    apt_repository "cloudkick" do
-      uri "http://packages.cloudkick.com/ubuntu"
-      distribution node['lsb']['codename']
-      components ["main"]
-      key "cloudkick.packages.key"
-    end
-
-    # add the Cloudera Repo of CDH4 packages for Ubuntu 12.04 on AMD64
-    apt_repository "cloudera" do
-      uri "http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh"
-      arch "amd64"
-      distribution "precise-cdh4"
-      components ["contrib"]
-      key "http://archive.cloudera.com/debian/archive.key"
-    end
-
-    # remove Zenoss repo
-    apt_repository "zenoss" do
-      action :remove
-    end
-
-## Pinning packages
-
-This LWRP provides an easy way to pin packages in /etc/apt/preferences.d.
-Although apt-pinning is quite helpful from time to time please note that Debian
-does not encourage its use without thorough consideration.
-
-Further information regarding apt-pinning is available via
-http://wiki.debian.org/AptPreferences.
-
-### Actions
-
-- :add: creates a preferences file under /etc/apt/preferences.d
-- :remove: Removes the file, therefore unpin the package
-
-### Attribute Parameters
-
-- package_name: name attribute. The name of the package
-- glob: Pin by glob() expression or regexp surrounded by /.
-- pin: The package version/repository to pin
-- pin_priority: The pinning priority aka "the highest package version wins"
-
-### Examples
-
-    # Pin libmysqlclient16 to version 5.1.49-3
-    apt_preference "libmysqlclient16" do
-      pin "version 5.1.49-3"
-      pin_priority "700"
-    end
-
-    # Unpin libmysqlclient16
-    apt_preference "libmysqlclient16" do
-      action :remove
-    end
-
-    # Pin all packages from dotdeb.org
-    apt_preference "dotdeb" do
-      glob "*"
-      pin "origin packages.dotdeb.org "
-      pin_priority "700"
-    end
-
-Usage
-=====
-
-Put `recipe[apt]` first in the run list. If you have other recipes
-that you want to use to configure how apt behaves, like new sources,
-notify the execute resource to run, e.g.:
-
-    template "/etc/apt/sources.list.d/my_apt_sources.list" do
-      notifies :run, resources(:execute => "apt-get update"), :immediately
-    end
-
-The above will run during execution phase since it is a normal
-template resource, and should appear before other package resources
-that need the sources in the template.
-
-Put `recipe[apt::cacher-ng]` in the run_list for a server to provide
-APT caching and add `recipe[apt::cacher-client]` on the rest of the
-Debian-based nodes to take advantage of the caching server.
-
-If you want to cleanup unused packages, there is also the `apt-get autoclean`
-and `apt-get autoremove` resources provided for automated cleanup.
-
-License and Author
-==================
-
-Author:: Joshua Timberman (<joshua@opscode.com>)
-Author:: Matt Ray (<matt@opscode.com>)
-Author:: Seth Chisamore (<schisamo@opscode.com>)
-
-Copyright 2009-2013 Opscode, Inc.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.