Quietly handle manually created snapshots

[tux-o-matic]

Today when using the Gluster snapshot feature, a Puppet run will generate a notify and potentially a rather long one because of the path change for bricks.

notify{ "unable to resolve brick changes for Gluster volume ${title}!\nDefined: ${_bricks}\nCurrent: ${vol_bricks}": }

Gluster, by default uses a known path for snapshots (/run/gluster/snaps/) which will include the name of the snapshot or a UID and the name of the volume. Something like:

/run/gluster/snaps/123456789abcdef/storage_gv

By adding the common part of the path used by snapshots as a class parameter in volume.pp, and using ${title} we could have quiet Puppet run without long and confusing Puppet events.

And maybe down the line it will open the door for managing snapshots fully from the module.