Brad Klein 0c64cfad13 Fix a couple bugs in the stack management script ... There are two use cases for a stack restart, one where you want to take a node down for maintentance, and two where you really want to stop the whole monasca stack. monasca-thresh is a cluster-wide process and can be stopped from any node in the cluster. But stopping it when taking a single node out of service isn't appropriate. Also update the lag checks for the new/correct way to get kafka consumer lag. Change-Id: I333b791c903a45e8a0fc101ade229991a03da2cc		2016-12-09 07:57:16 -07:00
..
vertica	Include vertica alarms state history table in stats update	2016-09-20 10:30:06 -06:00
agent_requirements.txt	Add support for symlinked agent virtualenv	2016-01-14 15:10:38 -07:00
monasca-api.conf	Only report STDERR to /var/log/upstart	2015-10-05 19:30:47 -06:00
monasca-thresh	Deliver our own startup scripts for monasca-api and monasca-thresh	2015-03-26 10:53:21 -06:00
monasca_stack.sh	Fix a couple bugs in the stack management script	2016-12-09 07:57:16 -07:00