Additional ssh tests with tempest

The run_ssh option is used on the default 'false',
 so several test case and validation step was disabled.

It was disabled because:
 * Admin password injection with the cirros image is not supported.
  (We 'cannot' inject password/shadow to a ram disk.)
 * In the current system setup floating IP is required for connecting
   with neutron

The run_ssh boolean option will be removed from tempest, it will be replaced
with ssh_connect_method and ssh_auth_method.

Since using a floating ip with nova flat network is not required in these
case, the 'fixed'/private IPs (ssh_connect_method) will be used with nova network
, and we will use the 'floating' IPs with neutron when the NAMESPACES
are enabled(default).

The default value of ssh_auth_method is keypair, it works in both cases.

Change-Id: I3d47811d801985687526749a430ed6db64224f99
Robustify shocco install and config

* shocco has some non-optional prereqs, make sure they are present if
shocco is being installed
* set the path to installed shocco correctly
* add the working dir to .gitignore

Change-Id: If786ea9e28d3595775f7b86d2fe760dff8047f49
Add driver_cert wrapper for cinder

This adds a simple wrapper to call tempest volume tests.
The idea is to make it easy to execute and capture results
from tempest.api.volume.test_*

Concept is for drivers in Cinder to configure cinder.conf as
needed and then run this script which will restart services and
kick off the tempest tests, and capture the output to a logfile
for submission.

To run,
1. deploy devstack as normal with tempest included in enabled_services
2. modify cinder.conf appropriately for your driver
3. execute the script devstack/driver_certs/cinder_driver_cert.sh

Change-Id: I98ec9e1e418a8416406db5e2e6ffd21992e392cf
Keystone don't use deprecated token_format option

devstack was setting the token_format option in the keystone
configuration file. This option is deprecated so should not be
used.

Change-Id: I047de155f0d9d2a1c009533c2f97f505cc80c6de
Handle Savanna service availability in tempest

Change-Id: I51300304655803f114d3bb911086cd88aa09638f
Remove powervm nova virt driver support

The powervm virt driver was removed from nova in a
recent change. This functionality is no longer needed in
devstack.

Change-Id: Iec620938a8cce63e0830fc7b9e9a679b361b4389
fixup_stuff prettytable min version

The minimum prettytable version is changed from 0.6 to 0.7
 in the global requirements.

If the system has an older prettytable version the fixup_stuff does not
takes effect in time, because at fixup time the system has the old
version.

Ensure the fixup installs the minimum required version in time.

Change-Id: If1737dacb25db73b68e707953d05576ad8a97da7
Merge "fixup_stuff prettytable min version"
Merge "Additional ssh tests with tempest"
Merge "Handle Savanna service availability in tempest"
Merge "Remove powervm nova virt driver support"
Merge "Add driver_cert wrapper for cinder"
Merge "Keystone don't use deprecated token_format option"
Merge "Robustify shocco install and config"
xenapi: enable user interaction with stack.sh

In XenServer, devstack runs inside a virtual machine. This makes it hard
for the user to interact with stack.sh should a parameter be missing.
This change will create an upstart job (devstack) that runs
stack.sh with console enabled so user can interact with it by running
vncviewer or using XenCenter.

Logging the output is also disabled, stamp files are used instead to
detect the script run status in case install_os_domU.sh is used.

As run.sh.log is removed, standard devstack logging should be used.

The change also removes the environment settings from run.sh, as they
are not needed, they should be specified in localrc. This way user
cannot get different experiences by using unstack.sh/stack.sh or run.sh

Also a proper unstack.sh is called instead of killing screen in run.sh

Change-Id: I7eb12bd74746cc7a1db3aa9fd68ece645a50001d
xenapi: display IP and DevStack result on console

The devstack setup service can update /etc/issue, displaying the status
of the installation and the VM's management IP. With this change, after
the devstack service finsihed, the login prompt will look like this:

OpenStack VM - Installed by DevStack
  Management IP:   10.219.3.108
  Devstack run:    SUCCEEDED

DevStackOSDomU login:

This helps people to log in to their system.

Change-Id: Idd6bbd5faf9ced5618cd3e95191bfc3b89473fa2