openstack/devstack
Code Issues Proposed changes

don't check for service enabled

Browse Source 
service enabled is something that's not required for sysstat and
friends, because instead we actually can do this with screen_it.

Change-Id: I4aa5787101cb0def46690f38a7f82effbb85f502
This commit is contained in:
Sean Dague 2014-02-11 17:28:56 -05:00 committed by Gerrit Code Review
parent 4df996bcc6
commit f1eb0475d9
1 changed files with 23 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
stack.sh
View File

@ -863,11 +863,10 @@ fi
init_service_check
# Sysstat
# Sysstat and friends
# -------
# If enabled, systat has to start early to track OpenStack service startup.
if is_service_enabled sysstat; then
# what we want to measure
# -u : cpu statitics
# -q : load
@ -879,19 +878,15 @@ if is_service_enabled sysstat; then
else
screen_it sysstat "./tools/sar_filter.py $SYSSTAT_OPTS $SYSSTAT_INTERVAL"
fi
fi
if is_service_enabled dstat; then
# Per-process stats
# A better kind of sysstat, with the top process per time slice
DSTAT_OPTS="-tcndylp --top-cpu-adv"
if [[ -n ${SCREEN_LOGDIR} ]]; then
screen_it dstat "cd $TOP_DIR; dstat $DSTAT_OPTS | tee $SCREEN_LOGDIR/$DSTAT_FILE"
else
screen_it dstat "dstat $DSTAT_OPTS"
fi
fi
if is_service_enabled pidstat; then
# Per-process stats
PIDSTAT_OPTS="-l -p ALL -T ALL"
if [[ -n ${SCREEN_LOGDIR} ]]; then
@ -899,7 +894,6 @@ if is_service_enabled pidstat; then
else
screen_it pidstat "pidstat $PIDSTAT_OPTS $PIDSTAT_INTERVAL"
fi
fi
# Start Services