During working with python3-first goals, I have notticed the
log_generator and log_save methods was non compliance with python3.

This is what doesn't appears in integration tests because we execute
only trove-functional-mysql job which doesn't covers guest-log tests.

In separate change I will extend zull definition by scenario tests to
avoid similar issues in future.

Change-Id: If85dff57afe110991553d510c6af4468a6781f64
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
(cherry picked from commit dfba4159b8153dca0d237eff990d827dc3fc6321)

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.

This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.

This update should result in no functional change.

For more information see the thread at

 http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html

Change-Id: I030f639b9332d378080c5d41549777be7ff9a25e

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/stein branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Ic05e51ded76f8aff3636cc65ca73432e426d6534

Change-Id: I4b12fffbe4f41c00288c396d4e864cb2afd9ef2b

Currently, listing instances only allows to get basic information about
entities. To get the details, one need to query instance "show" endpoint
for each instance separately. This is inefficient and exposes API to a
heavier load.

There are use cases in which we want to obtain detailed information
about all instances. In particular, in services integrating with Trove.
For example, Vitrage project requires this information to build vertices
and edges in the resource graph for RCA analysis.

This change extends Trove client by optional parameter allowing user  to
specify whether API should include more instance details in the
response.

Change-Id: Iecea2f711a3e23fd63167beb6cab4cecc63bcabe
Signed-off-by: Bartosz Zurkowski <b.zurkowski@samsung.com>

Quotes around {posargs} cause the entire string to be combined into one
arg that gets passed to stestr. This prevents passing multiple args
(e.g. '--concurrency=16 some-regex')

Change-Id: Ieeaa82bc6fb472490d1806c41cbffac130c0d23a

Currently 'openstack database flavor list' command fails when using
'--datastore-type' and '--datastore-version-id' options. This change
fixes the issue by correcting keyword arguments.

This change also adds a test case of listing flavors with the optional
arguments.

Change-Id: I37be4911d4dda1529e2550344a912e0aa3c50558
Closes-Bug: #1794663