Echo which services are being checked at check-sanity

make it explicit what services we confirm are running in
check-sanity.

Change-Id: I945b56867caf67680cd9b08caaa2561dc1badbf3
Don't reset IFS when calling screen_stop

Looking through logs I saw a whole bunch of

  2014-05-23 01:36:30.263 | /opt/stack/old/devstack/functions-common:
    line 1442: set -o xtrace: command not found

which was very strange, until I noticed grenade is changing IFS when
it calls screen_stop, so when that calls ${xtrace} the spaces aren't
split-up.

Change-Id: I20eb7d86839ea813a662e35b7d281382c085baa9
don't corrupt grenade exit value

The grenade exit value was getting masked in the exit handler
by doing something else before we captured it. Fix that, which
should make gate fails a little easier to resolve.

Change-Id: I61a950bf25319945292a36a70b7508839014d59f
Source lib/apache before lib/keystone

DevStack's lib/keystone depends on lib/apache. When lib/keystone
depends on any change introduced in lib/apache the build is broken as
lib/apache was not being sourced before that.

This change sources lib/apache just before sourcing lib/tls, as is
done in devstack/stack.sh.

Change-Id: Id0f51c678d4f16aaece08a4e5a74c48cc2ab1e6c
Merge "Source lib/apache before lib/keystone"
Merge "Don't reset IFS when calling screen_stop"
Merge "Echo which services are being checked at check-sanity"