Updated from global requirements

Change-Id: I5fe5a2d38871bec2796c0b42a02ecc061db9ebbd
Catch loading failures if transport_url is not set

The current implementation always tries to get a transport from
oslo.messaging assuming the transport_url option has been set. This is
done to keep backwards compatibility. However, since the default
`rpc_backend` is rabbit, it'll always try to load such driver. The
problem raises when `kombu` is not installed and the `notifier_strategy`
is set to qpid. This will make glance-api fail because it'll try to load
the rabbit driver *before* loading the qpid one.

This patch puts the first load attempt in a try / except block. The
error caught (if any) will be re-raised *just* if transport_url has been
configured, otherwise it'll move forward and try to load the notifier
driver using the old configuration options.

The patch also removes an obsolete test.

Change-Id: I00e653704463ea8245e2960050e0d5e6839f278a
Closes-bug: #1302661
(cherry picked from commit 164d1ab46f06141e2c12b944e15ae10f20dace38)
Fix Jenkins translation jobs

The -propose-translation-update and -upstream-translation-update
jobs do not update from transifex since our po files contain
duplicate entries where obsolete entries duplicate normal entries.

Remove all obsolete entries to fix the jobs.

Change-Id: Ib0fab723f245a87bb116ca21db31841574f7dc7f
Closes-Bug: #1299349
Merge "Catch loading failures if transport_url is not set" into milestone-proposed
To prevent remote code injection on Sheepdog store

Change-Id: Iae92eaf9eb023f36a1bab7c20ea41c985f2bf51b
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Update Glance configuration sample files for database options

Sample configuration files are out of date with respect to database
options. This change makes the options up-to-date.

Closes-bug: #1285617
Change-Id: I2694425a0b1610f37e77f1bc81aebed850a16348
Signed-off-by: Zhi Yan Liu <zhiyanl@cn.ibm.com>
Fixes Glance Registry V2 client

Add an optional configuration step to glance.db.get_api().

This step is then used in glance.db.registry.api in order to ensure that
the registry client has been configured in time for the registry db
driver's use.

Closes bug: #1302345

Change-Id: Id2c52c423b411ec20bdfa76ee91837c98b1613ef
Co-Authored-By: Mark J. Washenberger <mark.washenberger@markwash.net>