Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

The vmwaretools cookbook has been deprecated

Author provided reason for deprecation:

The vmwaretools cookbook has been deprecated and is no longer being maintained by its authors. Use of the vmwaretools cookbook is no longer recommended.

You may find that the vmware-tools cookbook is a suitable alternative.

RSS

vmwaretools (2) Versions 0.9.0

Installs/Configures vmware-tools

Policyfile
Berkshelf
Knife
cookbook 'vmwaretools', '= 0.9.0', :supermarket
cookbook 'vmwaretools', '= 0.9.0'
knife supermarket install vmwaretools
knife supermarket download vmwaretools
README
Dependencies
Quality 29%

vmware-tools Cookbook

Chef cookbook for installing vmware tools. Currently supports installation from source (default) or from VMWare's yum repo

Github: https://github.com/andrewfraley/chef-vmware-tools

Requirements

  • If you're going to install from source, you'll need the minimum requirements to build vmware tools. On a RHEL or CentOS system, you'll need: make gcc kernel-devel kernel-headers glibc-headers perl

  • This has only been tested on RHEL6, but should probably work on Debian/Ubuntu if building from source. On Ubuntu you'll need build-essential.

Attributes

Source Install (default)

  • node['vmware-tools']['url'] - URL to download the source tarball. No default.
  • node['vmware-tools']['version'] - Version of VMWare tools you're installing, e.g. "9.4.0". Used to prevent installing over automatically upgraded versions.
  • node['vmware-tools']['upgrade_only'] - When set to true (default), only install the specified version if it's newer than the installed version
  • node['vmware-tools']['src_path'] - Path to store the vmware-tools source. Default: /usr/local/src

RPM Install

  • node['vmware-tools']['graphical-tools'] - Set if you're running X
  • node['vmware-tools']['esx_version'] - Should correspond to directories seen here: http://packages.vmware.com/tools/esx/index.html
  • node['vmware-tools']['repo_base_url'] - ESX versions seen here: http://packages.vmware.com/tools/esx/
  • node['vmware-tools']['gpg_key_url'] - URL for the repo's gpg key. Default is set to VMWare's. Leave default unless you're using you're own yum repo

Usage

vmware-tools::default

The default recipe will install vmware-tools from source downloaded from a web server that you specify.

Example Role:
name "vmware-tools_role"
description "vmware-tools install"
run_list [
    "recipe[vmware-tools]",
    ]

default_attributes(
  "vmware-tools" => {
    "url" => "http://yourserver.local/vmware/latest-tools.tgz",
    "version" => "9.4.0"
  }
)

vmware-tools::rpm

This recipe will install vmware-tools from VMWare's yum repo. Do not include the default recipe if using this recipe.

Example Role:
name "vmware-tools-rpm_role"
description "vmware-tools rpm install"
run_list [
    "recipe[vmware-tools::rpm]",
    ]
 # Note you don't need to set any attributes

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  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 using Github

License and Authors

Dependent cookbooks

ark >= 0.0.0
yum >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.9.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.9.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.9.0 failed this metric

FC007: Ensure recipe dependencies are reflected in cookbook metadata: vmwaretools/recipes/rpm.rb:2
FC064: Ensure issues_url is set in metadata: vmwaretools/metadata.rb:1
FC065: Ensure source_url is set in metadata: vmwaretools/metadata.rb:1
FC066: Ensure chef_version is set in metadata: vmwaretools/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: vmwaretools/metadata.rb:1
Run with Foodcritic Version 12.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.9.0 passed this metric

No Binaries Metric
            

0.9.0 passed this metric

Testing File Metric
            

0.9.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.9.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number