Clean up style

Fix puppet-lint violations as a step toward running puppet-lint
at the gate.

Change-Id: I97d9ab7e5f3b009987d7d3e20fb8b5db68fea825
Store reports in PuppetDB

We configure Puppet with PuppetDB but are not currently enabling
PuppetDB as a report processor. Enable storing both YAML and PuppetDB
reports.

Change-Id: I2166eb2d1c429661db0b36c4087307c62d3a4b9e
Closes-Bug: #1282578
Remove deprecation warning/unify package_ensure

Puppet-coi calls the ntp class with a parameter that has been
deprecated in newer versions of the PuppetLabs NTP module that
manages whether the NTP package gets updated as new packages are
made available, or is merely installed once.  Presumably deployers
will want to manage that setting the same way they manage the
settings for other packages in the system, so it makes far more
sense to map it to the package_ensure variable at the composition
layer.  This patch does that.  Note also that a separate patch
to puppet-coi has removed the deprecated param.

Change-Id: I6d0eae7d6fead8ccd64bfa7fae1ec5694580f627
Partial-Bug: #1281896
Resolve deprecation warnings

Currently, there are several deprecation warnings emitted by
catalog runs that are due to changes in parameters for various
modules.  These include:

Warning: Scope(Class[Neutron::Server]): sql_connection deprecated
  for database_connection
Warning: Scope(Class[Nova]): sql_connection deprecated for
  database_connection
Warning: Scope(Class[Neutron::Server]): sql_idle_timeout deprecated
  for database_idle_timeout
Warning: Scope(Class[Nova::Keystone::Auth]): cinder parameter is
  deprecated and has no effect.

This patch resolves those warnings by updating data mappings
to use more modern parameter names.  The last warning above is
caused by the presence of the old "grizzly_hack.yaml" file that
was necessary before a stable/grizzly branch was created, so
that file is removed since it's no longer needed.

Change-Id: I706ea95ea25a94388fdfb4ded34c8ea9d52cd7b2
Partial-Bug: #1281896
Expose VRRP router VRIDs for HA scenario

Expose the VRIDs assigned to the controller and swift VRRP groups
created in HA scenarios to allow users to avoid conflicts with existing
VRIDs in their environment.

Change-Id: I6c0c63dc9115f8fafbd78d00c9012011d900e0d5
Closes-Bug: #1280277
Merge "Resolve deprecation warnings"
Merge "Expose VRRP router VRIDs for HA scenario"
Merge "Remove deprecation warning/unify package_ensure"
Merge "Store reports in PuppetDB"
Merge "Clean up style"
Merge remote-tracking branch 'upstream/master' into coi-development