cookbook 'smartmontools', '~> 2.0.7'
smartmontools (10) Versions 2.0.7 Follow7
Installs and configures smartmontools
cookbook 'smartmontools', '~> 2.0.7', :supermarket
knife supermarket install smartmontools
knife supermarket download smartmontools
Smartmontools Cookbook
This cookbook will install the smartmontools package and enable the service. It will also configure default email reports.
Maintainers
This cookbook is maintained by the Sous Chefs. The Sous Chefs are a community of Chef cookbook maintainers working together to maintain important cookbooks. If you’d like to know more please visit sous-chefs.org or come chat with us on the Chef Community Slack in #sous-chefs.
Requirements
Platforms
- Ubuntu
- RHEL family (Redhat Enterprise, CentOS, etc)
- Debian
Chef
- Chef 13+
Cookbooks
- none
Attributes
-
node['smartmontools']['smartd_opts']
- sets the value for thesmartd_opts
in /etc/default/smartmontools. Default is "", which leaves the option commented. -
node['smartmontools']['start_smartd']
- whether to start smartd service in /etc/default/smartmontools. Default is "yes". -
node['smartmontools']['devices']
- Array of devices to monitor with the options used in smartd.conf. May also be a hash to provide different options for each device. Default is []. See Usage. -
node['smartmontools']['device_opts']
- If set, these options will be used by default in /etc/smartd.conf for each of thedevices
above. Default is "-H -l error -l selftest". -
node['smartmontools']['run_d']
- Array of scripts to drop off in/etc/smartmontools/run.d
. Default is ["10mail"].
Templates
/etc/smartd.conf
Note: The default /etc/smartd.conf configuration file from the package itself does not recommend using DEVICESCAN, despite it being enabled by default. The template will only use DEVICESCAN if node['smartmontools']['devices']
is not set.
The template for this file will iterate over the node['smartmontools']['devices']
attribute and write the configuration out. If no specific options are set for a device, it will get the options from node['smartmontools']['device_opts']
. See Usage below.
/etc/default/smartmontools
Starts smartd by default using node['smartmontools']['start_smartd']
. The enable_smart
option is not recommended by smartmontools per the comment and is not managed via the template. Modify your local copy of the template if you wish to change this.
Cookbook Files
/etc/smartmontools/run.d/*
Each filename in the array node['smartmontools']['run_d']
will be dropped off via a cookbook file. By default the only one is 10mail, which exists, and came from the package. These files should be in files/default
.
Usage
By default, the recipe is not set up to monitor any particular devices in smartd.conf, and will use DEVICESCAN. Set the attribute node['smartmontools']['devices']
to monitor a specific list of disk devices. If you don't require device specific options, this should be an array. A default set of options will be used for all disks from the node['smartmontools']['device_opts']
attribute.
For example:
name "base" ... default_attributes( "smartmontools" => { "devices" => ['sda','sdb','sr0'], "device_opts" => "-H -l error -l selftest -m root@example.com" } )
If you need different configuration options for each device, specify the devices as Hash with the device name as key and the options as value. If the value for a device is nil, the default options from the node['smartmontools']['device_opts']
attribute are used. For example:
name "base" ... default_attributes( "smartmontools" => { "devices" => { "hda" => "-a -o on -S on -s (S/../.././02|L/../../6/03)", "hdb" => nil, "hdc" => nil }, "device_opts" => "-H -l error -l selftest -m root@example.com" } )
For different kinds of hard drive configurations in your data center, use default_attributes
in separate roles. For example if web servers have only a single internal disk, but database servers have two disks:
name "webserver" ... default_attributes( "smartmontools" => { "devices" => ['sda'] } ) name "database_server ... default_attributes( "smartmontools" => { "devices" => ['sda', "sdb"] } )
Contributors
This project exists thanks to all the people who contribute.
Backers
Thank you to all our backers!
Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website.
Dependent cookbooks
This cookbook has no specified dependencies.
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
smartmontools Cookbook CHANGELOG
This file is used to list changes made in each version of the smartmontools cookbook.
2.0.7 - 2024-05-06
2.0.6 - 2024-05-06
2.0.5 - 2023-11-01
2.0.4 - 2023-02-14
2.0.3 - 2022-02-08
- Remove delivery folder
2.0.2 - 2021-08-31
- Standardise files with files in sous-chefs/repo-management
2.0.0 (2020-05-05)
- Depreciated support for centos 6
- Minimum chef version bumped to 13
- Remove
if responds_to?
check around metadata in metadata.rb - Remove unnecessary long_description metadata from metadata.rb
- Migrate to github actions
1.1.0 (2017-02-04)
- Move ownership of the cookbook to the Sous Chefs organization
- Add full integration testing with kitchen-dokken in Travis CI
- Add missing license file
- Don't fail if there is no node['virtualization']
- Add chefignore file to limit which files are uploaded to the chef server
- Add gitignore, berksfile, Gemfile, Rakefile, and rubocop config files
- Added CONTRIBUTING and CODE_OF_CONDUCT files
- Resolve cookstyle warnings
- Add new supermarket metadata
- Remove the init-smartmontools init script that wasn't used anymore
- Remove support for Debian 6 in the metadata since its EoL and we don't support it
- Remove workaround that supported Ubuntu 10.04
Collaborator Number Metric
2.0.7 passed this metric
Contributing File Metric
2.0.7 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
Cookstyle Metric
2.0.7 passed this metric
No Binaries Metric
2.0.7 passed this metric
Testing File Metric
2.0.7 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
2.0.7 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
2.0.7 passed this metric
2.0.7 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
Cookstyle Metric
2.0.7 passed this metric
No Binaries Metric
2.0.7 passed this metric
Testing File Metric
2.0.7 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
2.0.7 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
2.0.7 passed this metric
2.0.7 passed this metric
Testing File Metric
2.0.7 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
2.0.7 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
2.0.7 failed this metric
2.0.7 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