adding raid to doc list
Fix volume_compatible_with_resource_definition?

If the new resource does not specify a snapshot_id, the check to see if
we have an existing volume will always fail if the existing volume had a
snapshot made elsewhere. The fix is to bypass the volume snapshot
comparison if the new_resource snapshot_id is nil.
Merge remote-tracking branch 'upstream/master'
exclude tags with the aws prefix from update
Merge pull request #18 from streeter/snapshot-check

COOK-2659: Fix volume_compatible_with_resource_definition?
Merge pull request #22 from charity/charity.awstags

Charity.awstags
release v0.101.0
fixing foodcritic alerts
Merge pull request #26 from ranjib/foodcritic_fix

[COOK-2951] aws cookbook has foodcritic failures
[COOK-1471] - mention route53 cookbook
release v0.101.2
increment version for development
tidy up readme, add note about right_aws gem
fix values for IOPS in readme
[COOK-3264] file ownership and mode for ebs raid mount point
Merge pull request #28 from tabolario/COOK-3264

file ownership and mode for ebs raid mount point
Adding logic to RAID creation and volume attachments to ensure mdadm properly allocates the device number. If a block device triggers a mdadm scan, for instance during a EBS snapshot attachment, without having a proper mdadm.conf, a random device number is chosen (md127) and the assembly will fail. To ensure this doesn't happen we're queueing udev events, letting the RAID create or the existing snapshot volumes attach, then querying mdadm for its UUID and device number and tee'ing it to mdadm.conf. Once the RAID is in tact by means of creation or assembly, we're safe to start the udev message queue and finally we update initramfs to be sure the configuration perists reboots.
Fixing the md_device grep so it finds devices on ubuntu 12.04
Merge pull request #34 from joshuatobin/COOK-3308

[COOK-3308] Adding logic to RAID creation and volume attachments to ensure mdadm pro...
Trim all that whitespace :)