Support for upgrading neutron

With this patch grenade can be run either with nova-network or neutron.

Closes-bug: #1235149
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>

Change-Id: Ib35ee2b35155f3c7e86eef5c75f70da300fa99c7
Remove unnecessary services stopping in Neutron

Change-Id: I6c844e7e3df04d66f6255f85fded9a9398912c48
add exit trap to determine what's failing

grenade does a lot with starting and stopping processes, so if
we get a hard to diagnose fail dump the process list and disk
status.

Change-Id: Ia7377608cdc51067bc418569012df9a81d48e060
Merge "Remove unnecessary services stopping in Neutron"
support proposed/* branches

provide support for named proposed branches for selection logic

Change-Id: Ia27fc54f41404a113065258e950adb2851f1ece8
switch swift enables to specify services

in the gate we specify all the swift services directly, not the
old swift flag. We should mirror that back to grenade, as we now
really do depend on it.

Change-Id: Id0ddf92c0c2d02dd3fb86e408a84646e081944da
Merge "support proposed/* branches"
Merge "switch swift enables to specify services"
switch to icehouse -> juno upgrade

make nova rolling upgrade use base release

instead of hard coding this, always use the base release value.
This will let us roll forward gracefully in the future.

Related-Bug: #1309324

Change-Id: If9417e65c7c54d017c4c847a4020f855684c423c
Fix error message in upgrade_project()

It's not just for Cinder...

Change-Id: I285279f5e8f4b414d75be80776a039fa98dbe5c8
Merge "switch to icehouse -> juno upgrade"
Configure VPN when upgrading from Icehouse

There was a change in devstack how VPNaaS agent is started. It uses some
global variables introduced by https://review.openstack.org/#/c/86567/

Closes-Bug: #1313791
Change-Id: I76d8e8c9b9ac558f31cb3e22a936efbebff5b9a3
make the exit trap only dump on fail

We should only dump things like the process list on a failure,
not all the time.

Change-Id: Ibf6edbeedb2fdd76ee59d3908bf1991873c5e5a3
Merge "Configure VPN when upgrading from Icehouse"
Echo which services are being checked at check-sanity

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

Change-Id: I945b56867caf67680cd9b08caaa2561dc1badbf3
make grenade work out of the box

this makes it so that grenade can build the required base
directories out of the box without needing manual intervention.

Change-Id: I85dc8c9599302b0e7de7930fad246b24d4447af2
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"