db monitoring on percona-server only

db_arbiter doesn't run mysql, don't put the monitoring in the
percona-common role.
Fix IPMI console config to work with our HW

The IPMI console on most of our currently deployed systems is wired to ttyS1,
while on other systems its ttyS2. Move this into a configuration
parameter `common.ipmi.serial_console`.

Update check-kernel-options to accept a console on either port and fix
double negative in warning message.

Configure primary kernel console on virtual tty 1, rather than 0 so
we can switch back to it and login prompt appears after boot as
expected.

Move update-grub into a handler
logging: first pass at logstash-forwarder
logging: use vars for upstream host:port
logging: use correct jinja var syntax, not logic
logging: use copy module, not file module
logging: lsf config per role

logging: config lsf - cinder-control, cinder-data
logging: config lsf - glance
logging: config lsf - heat
logging: config lsf - keystone
logging: config lsf - neutron-control
logging: config lsf - neutron-data
logging: config lsf - neutron-data-network
logging: config lsf - nova-control, nova-data
logging: fix test/setup config path
logging: handle when no main logs followed
logging: add cleanup tasks for rsyslog configs
logging: create config role for abstraction
logging-config: all service roles
logging: address comments on cleanup
logging-config: fix bad rebase indent
Merge pull request #664 from blueboxgroup/fix-ipmi-console

Fix IPMI console config to work with our HW
Merge pull request #648 from blueboxgroup/lsf

logging: first pass at logstash-forwarder
Merge pull request #659 from blueboxgroup/fix-arbiter-monitoring

db monitoring on percona-server only
logging-config: missing dep on logging role
Merge pull request #668 from blueboxgroup/logging-config-dep

logging-config: missing dep on logging role
testenv: cleanup nova secgroup

During the `test/setup` script a security group is created for the new
environment. Unfortunately, this fails when the security group already
exists from a previous run. Instead of trying to diff the two groups and
update, simply remove the existing security group when the instances are
deleted.