Merge "Fixed db conn recovery issue. Fixes bug 954971."
Specify location when creating s3 bucket.

Fixes bug 961050

Avoids bucket creation failure when a region-specific S3 endpoint
(e.g. s3-eu-west-1.amazonaws.com) and also bucket create-on-demand
are configured.

Change-Id: Ieba9c535ccb961a1f81bd2632b5ac49c23ac7901
Merge "Specify location when creating s3 bucket."
Use unique per-test S3 bucket name.

Addresses bug 955527

Avoids a race between the S3 testcase body and the bucket clean-out
in the S3 test teardown, running near concurrently in the Jenkins
python26 and python27 builds.

Change-Id: I10f013b02bb74db2cbfc692ed372121d21bca3fb
Send output of stty test cmd to stderr.

Send the output of the stty test for terminal size to stderr.

Fixes LP Bug #961820.

Change-Id: Ifc46632c9cf8bffb2dec7ef48f17157bf8ae1199
Fixes lp959670

Manually sets the content_type in the notification message body. This allows any
tools dependent on the content_type to function correctly.

Change-Id: I496c005b84df5f4aa2c18ab2b3a4ab136b840111
Avoid leaking secrets into config logging.

Fixes bug 962385

Configuration option values are logged when debug is enabled,
which is in turn exposed via the glance-logcapture nose plugin
when tests fail in Jenkins.

Allow options to be declared secret so that their value is
obfuscated before logging.

Also proposed to openstack-common as:

  https://review.openstack.org/5694

Change-Id: Ifdd1696f40c069f83c160afb0bf399da21796b8a
Merge "Avoid leaking secrets into config logging."
Merge "Fixes lp959670"
Set content_type for messages in Qpid notifier.

Fix bug 963050.

This patch is the Qpid equivalent for a patch that just went in for the
rabbit/kombu notifier.  Glance encodes the message in json format before
passing it in to the notifier.  Explicitly set the content type for the
messages to 'application/json'.

Change-Id: I2f83f51487541b951f3eca0ae4d160a64f5a3db1
Ensure functional db connection in configure_db()

During initial database setup, ensure we can physically connect
to the database and allow a failed connection to make use of the
new retry mechanism instead of registry startup failing outright.

Fixes lp bug #959426.

Change-Id: I1c87b19913c4204465e5d2027f2f184f0f358fd0
Typo.

* doc/source/configuring.rst
  Fix typo.

* Authors
  Add my name in this file.

Change-Id: I23cea08560a02897c85d031bd0f16f22d7d84db0
Adding versioned namespaces in test dir

This is being done in preparation for the v2 API.

Change-Id: Ie2fc4df77740b6d1cd629a21942850fd24eb7d60
Merge "Adding versioned namespaces in test dir"
Support owner paramater to glance add

Fixes bug 962998

Allow the owner to specified as a first class image attribute
when creating a new image via the CLI, as it is currently for
image update.

Also added a simple fakeauth pipeline to allow the user, tenant
and admin status of API requests to be easily controlled by
functional tests.

Change-Id: I0f83d55d4a96ad3632fb238ad1758ec3f00ed3fd
Merge "Support owner paramater to glance add"
Allow yes-like values to be interpreted as bool

* Accept 'YES', 'yes', 'Y' and 'y'
* Remove duplicate function bool_from_header_value
* Fixes bug 965563

Change-Id: I593a50117fd339a8ab281a8daad734770ca9960c
Merge "Ensure functional db connection in configure_db()"
Allow specifying the current version in 'glance-manage version_control'

Fixes bug #966242

The version_control command is a bit useless since you can't actually
specify what version to  use and it defaults to version=0.

Allow the user to specify a version:

  $> glance-manage version_control 9 # set the diablo version

and default to the latest version if none is specified.

Also, allow db_sync to be supplied a version for the case where we're
upgrading an unversioned DB.

Finally, re-work the argument handling in glance-manage to more easily
handle optional args.

The tests are extended to test using db_sync for upgrades and to test
placing an existing database under version control.

Change-Id: I231dc710554198bfd1fdcb82c3c3768963f64bd8
Run version_control after auto-creating the DB

Fixes bug #966241

Currently, we auto-create an unversioned DB. This makes it awkward to
later upgrade it, especially since our 'glance-manage version_control'
command doesn't support retroactively versiioning it.

This is easily avoided by running version_control() after creating the
DB.

Change-Id: I935c06fcbcd3611c65d464850ca05445129f905f