Installs lvm2 package and includes resources for managing LVM. The default recipe simply installs LVM and the supporting Ruby gem. The cookbook includes providers for managing LVMs.
- Chef 10 or higher
Manages LVM physical volumes.
Action | Description |
---|---|
:create | (default) Creates a new physical volume |
Parameter | Description | Example | Default |
---|---|---|---|
name | (required) The device to create the new physical volume on | '/dev/sda' |
lvm_physical_volume '/dev/sda'
Manages LVM logical volumes.
Action | Description |
---|---|
:create | (default) Creates a new logical volume |
Attribute | Description | Example | Default |
---|---|---|---|
name | (name attribute) Name of the logical volume | bacon | |
group | (required) Volume group in which to create the new volume (not required if the volume is declared inside of an `lvm_volume_group` block) | bits | |
size | (required) Size of the volume.
|
|
|
filesystem | The format for the file system | 'ext4' | |
mount_point |
Either a String containing the path to the mount point, or a Hash with the following keys:
|
'/var/my/mount' | |
physical_volumes | Array of physical volumes that the volume will be restricted to | ['/dev/sda', '/dev/sdb'] | |
stripes | Number of stripes for the volume | 5 | |
stripe_size | Number of kilobytes per stripe segment (must be a power of 2 less than or equal to the physical extent size for the volume group) | 24 | |
mirrors | Number of mirrors for the volume | 5 | |
contiguous | Whether or not volume should use the contiguous allocation policy | true | false |
readahead | The readahead sector count for the volume (can be a value between 2 and 120, 'auto', or 'none') | 'auto' |
lvm_logical_volume 'home' do
group 'vg00'
size '25%VG'
filesystem 'ext4'
mount_point '/home'
stripes 3
mirrors 2
end
Manages LVM volume groups.
Action | Description |
---|---|
:create | (default) Creates a new volume group |
Attribute | Description | Example | Default |
---|---|---|---|
name | (required) Name of the volume group | 'bacon' | |
physical_volumes | (required) The device or list of devices to use as physical volumes (if they haven't already been initialized as physical volumes, they will be initialized automatically) | ['/dev/sda', '/dev/sdb'] | |
physical_extent_size | The physical extent size for the volume group | ||
logical_volume | Shortcut for creating a new `lvm_logical_volume` definition (the logical volumes will be created in the order they are declared) |
lvm_volume_group 'vg00' do
physical_volumes ['/dev/sda', '/dev/sdb', '/dev/sdc']
logical_volume 'logs' do
size '1G'
filesystem 'xfs'
mount_point location: '/var/log', options: 'noatime,nodiratime'
stripes 3
end
logical_volume 'home' do
size '25%VG'
filesystem 'ext4'
mount_point '/home'
stripes 3
mirrors 2
end
end
If you're using Berkshelf, just add this cookbook to your Berksfile
:
cookbook 'lvm'
You can also install it from the community site:
knife cookbook site install lvm
Include the default recipe in your run list on a node, in a role, or in another recipe:
run_list(
'recipe[lvm::default]'
)
Depend on lvm
in any cookbook that uses its Resources/Providers:
# other_cookbook/metadata.rb
depends 'lvm'
This cookbook depends on the di-ruby-lvm and di-ruby-lvm-attrib gems. The di-ruby-lvm-attrib gem in particular is a common cause of failures when using the providers. If you get a failure with an error message similar to
No such file or directory - /opt/chef/.../di-ruby-lvm-attrib-0.0.3/lib/lvm/attributes/2.02.86(2)/lvs.yaml
then you are running a version of lvm that the gems do not support. However, getting support added is usually pretty easy. Just follow the instructions on "Adding Attributes" in the di-ruby-lvm-attrib README.
This section details "quick development" steps. For a detailed explanation, see [[Contributing.md]].
-
Clone this repository from GitHub:
$ git clone [email protected]:opscode-cookbooks/lvm.git
-
Create a git branch
$ git checkout -b my_bug_fix
-
Install dependencies:
$ bundle install
-
Make your changes/patches/fixes, committing appropiately
-
Write tests
-
Run the tests:
bundle exec foodcritic -f any .
bundle exec rspec
bundle exec rubocop
bundle exec kitchen test
In detail: - Foodcritic will catch any Chef-specific style errors - RSpec will run the unit tests - Rubocop will check for Ruby-specific style errors - Test Kitchen will run and converge the recipes
- Author:: Joshua Timberman [email protected]
- Author:: Greg Symons [email protected]
Copyright:: 2011, 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.