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


yum-dell (6) Versions 3.0.5

Configures Dell repositories. Installs OMSA

cookbook 'yum-dell', '~> 3.0.5', :supermarket
cookbook 'yum-dell', '~> 3.0.5'
knife supermarket install yum-dell
knife supermarket download yum-dell
Quality 17%

yum-dell Cookbook

Build Status

Configures Dell community and hardware/OMSA (Open Manage Server Assistant)
repositories. See for full details.

The default recipe configures community and hardware repositories, and installs
OMSA on Dell hardware. On non-Dell hardware, only the community repository is

The community repository provides non-Dell specific
dkms (Dynamic Kernel Module Support), and SMBIOS (Systems Management BIOS)
library packages.

The hardware repositories contain hardware drivers, firmware binaries,
BIOS updates, and OMSA software specific to Dell hardware.


There is a dependency on the dmidecode package so that Ohai can detect Dell

This cookbook depends on the yum_repository provider from the yum cookbook.
You need to have a RHEL family platform, and yum, to use the cookbook.


  • yum - Opscode maintained 3.0+ cookbook


The following are overridable attributes, in the yum['dell'] namespace.


<td>Whether Dell hardware was detected via Ohai, or not.</td>
<td><tt>Value depends on hardware.</tt></td>
<td>An array of packages from Dell repositories to install.</td>
<td><tt>srvadmin-all</tt> on Dell hardware. <tt>Empty</tt> on non-Dell hardware.</td>

Each Dell repository has its own attribute namespace. It is recommended
that you not override these, unless you have a local mirror. The attributes
correspond to the parameters in the yum_repository library.

per-repository attributes

<th>Corresponding repository</th>
<td>Community supported Open Source software.</td>
<td>Dell OMSA repository, Hardware independent</td>
<td>Dell OMSA repository, Hardware specific</td>

<td>Filename of repo file.</td>
<td><tt>dell-community</tt>, <tt>dell-omsa-indep</tt>, <tt>dell-omsa-specific</tt> respectively</td>
<td>Human readable description for repository.</td>
<td>e.g. Dell Community Repository</td>
<td>URL with list of mirrors.</td>
<td>repository specific</td>
<td>URL of public signing key for package</td>
<td>repository specific</td>
<td>Whether, or not, to check the provided gpgkey</td>
<td>Method to choose next mirror on failure. Either, priority or roundrobin.</td>



Optionally, set attributes in a role, and
include yum-dell in your node's run_list:

  :yum => {
    :dell => {
      :packages => [ "srvadmin-base" ]
  "run_list": [


This recipe does the opposite action of yum-corporate::default.

Specifically, this recipe runs to remove
all OMSA comoponents. It deletes all Dell repository .repo
files. Finally, it purges any leftover settings left after
uninstall in /opt/dell/srvadmin.


  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

Author:: Eric G. Wolfe
Copyright:: 2010-2011

Author:: Tippr, Inc.
Copyright:: 2010

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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

yum >= 3.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

yum-dell Cookbook CHANGELOG

This file is used to list changes made in each version of the yum-dell cookbook.


  • Update GPG key URL
  • Constrain yum dependency to 3.x or higher


  • Remove yum_key workaround
  • Update tests
  • Remove stale key file
  • Change kitchen plugin to docker
  • Add Jenkins task for internal testing


  • Fix i686 URI
  • Add regression tests for kernel.machine i686 case.


  • Update tests
  • Workaround for COOK-4164


Update metadata


Reworked against yum 3.0.0

  • Split dell recipe out from soon to be deprecated, yumrepo
    • Changed variable scope from yumrepo['dell'] to yum['dell']
    • Updated kitchen files
    • Added ChefSpec unit tests
    • Removed minitest unit tests
    • Added bats integration tests
    • Added Rubocop style guide linter
    • Added undo recipe


  • Pin against yum < 3.0.0


  • Add test-kitchen skeleton
    • Validated recipes against yum v2.3.0
  • Fix minitest-spec tests for Chef 11
  • Deprecated annvix repo
    • Appears to be no longer maintained for EL6


  • vmware-tools
    • Bump version to ESX 5.1
    • re-instated to default recipe
    • add upstart support for vmware-tools 9.0 packages on EL 6
    • Change LWRP action to create (updates repo file), instead of add
  • deprecate/remove epel recipe
    • has been moved over to Opscodes yum::epel
  • disable minitest spec for Travis
    • This isn't working on TravisCI, will revisit unit tests later


  • add zeromq repo
    • contributed by @BryanWB
  • Bump chef gem in Gemfile
    • Locked chef gem at 10.X, 'cause minitest spec seems to be broke on chef 11.x.

TODO - Replace tests with chefspec


Fix mirrorlist attribute in Dell recipe.


Thanks to Paul Graydon (@twirrim) for adding Percona MySQL repositories.

Thanks to Bryan Berry (@bryanwb) for adding yet another PostgreSQL
repository. :)

Breaking changes (postgresql)

  • Recipe renamed, postgresql9 -> postgresql.
  • Added node['repo']['postgresql']['version'] to select version of Postgres via attribute, from repository.


Set name/base_url to localdomain in the case Ohai domain is
unavailable. Fixes chef-solo compilation error on Vagrant boxes.


Change corporate recipe to key off domain name.


Add VMWare Tools for ESX v5.0u1, along with a vmware-tools-upgrade

recipe. The yumrepo::vmware-tools recipe is backwards incompatible.
Unfortunately there is no way to upgrade vmware-tools rpm files without
yanking them out, and replacing them.

One must ensure the `vmware-tools-upgrade` recipe will run **before**

the vmware-tools recipe. Otherwise the 4.1 recipe will directly
conflict with the 5.0u1 version of the recipe.

I also added some attribute sanity tests for this new version, enjoy!

Collaborator Number Metric

3.0.5 failed this metric

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

Contributing File Metric

3.0.5 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, and your repo must contain a file

Foodcritic Metric

3.0.5 failed this metric

FC064: Ensure issues_url is set in metadata: yum-dell/metadata.rb:1
FC065: Ensure source_url is set in metadata: yum-dell/metadata.rb:1
FC066: Ensure chef_version is set in metadata: yum-dell/metadata.rb:1
FC069: Ensure standardized license defined in metadata: yum-dell/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric

3.0.5 passed this metric

Testing File Metric

3.0.5 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, and your repo must contain a file

Version Tag Metric

3.0.5 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, and your repo must include a tag that matches this cookbook version number