Mounting NFS-Shares with Puppet

Welcome to the next part of my little blog entry series about comparing Cfengine 3 with Puppet.
In this issue, we will write a Puppet manifest for mounting a NFS share. You can compare it directly to the Cfengine 3 code snippet if you click here.

Summary
Mounting the NFS share via Puppet was easy. In addition, Puppet added a new entry in /etc/fstab:

cat /etc/fstab
# HEADER: This file was autogenerated at Sat Jan 19 21:27:19 +0100 2013
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=f89cb605-8324-424f-9a0c-c555e7e0e779 / ext4,acl errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a66917ea-c89b-4067-80ec-7c13f0a4bd1c none swap sw 0 0
localhost:/blubb /mnt nfs defaults 0 0

When comparing both the Cfengine 3 and Puppet snippets with each other, I do not see which configuration management tool does it the more effective or easy way. Both do a good job when looking at the amount of lines you need to write for this purpose. However, one could argue that Puppet does the job a little bit better since you can directly provide the info if the NFS share should be mounted at boots or not (fstab entry).