openSUSE 42.3 is dead, remove the experimental job so that
CI can remove the job completely.

On master this job has been converted to 15, let's not do this on the
branch.

Change-Id: I9dd301b5e03b0d40453acbcf3a8c2d7e2232d026

This avoids falling back to the global bindep-fallback.txt which
installs a pretty big environment. Without this change, a lot
of additional but unnecessary packages are installed on the nodepool
workers.

Change-Id: Id6c17f9a53ad8ad5f0bb9d308ccf5d33a6f59f7f
(cherry picked from commit 8db99e22)

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.

Use new devstack-plugin-ceph jobs instead of legacy ones,
these are now in the devstack-plugin-ceph repo.

(partial backport of I6baeff0ed652cfad88f93c66d49bcb6f98df7e97)

Change-Id: I8d659a32f7fbdb8205ca59f4b0f1eec0ec12cd5f
(cherry picked from commit afc0ceb1)

Change-Id: Ida4e7889752c6c2219b06c1238c355e5203d8b0d

This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I4ea7c07a1da13b7693c952846e4bd0153259e3e6
Story: #2002586
Task: #24297

The displayed image attributes of the command 'openstack image list'
do not has 'Server', so this patch remove it. The available status
of image should be 'active' according to the output of the command.

Change-Id: I90efd2b3f1838cdcaa79feea78d73429cded1257
(cherry picked from commit 6f858c3c)

Add the legacy barbican-tempest experimental job
to the stable/pike branch of glance.

Depends-On: https://review.openstack.org/551372
Needed-By: https://review.openstack.org/#/c/551016/
Change-Id: Ia92e9faada4b45c4b4a7788be3f833b9d5ce7b50

Explain why 15.0.1 exists.

Change-Id: I6bf6e43f410ccf91f6bb3d08dacdffcd34703a3f

The stable maintenance tests are run using the current CI images
(appropriately enough, since that's the environment a stable branch
is likely to be deployed in).  In any case, there have been some
distro changes affecting py27 reflected in the current images and
the tests are failing [0].

This patch includes two changes:
- eventlet issue <0.22.0 (impacts functional tests)
  (cherry picked from commit 6f63d28d)

- fixtures must be imported absolutely or they aren't monkey patched
  (change could not be cherry-picked from master because some other
  refactoring occurred that would make for a non-trivial backport, and
  it's not worth the risk)

[0] http://lists.openstack.org/pipermail/openstack-stable-maint/2018-February/007235.html

Co-authored by: Erno Kuvaja <jokke@usr.fi>
Co-authored by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Closes-bug: #1747304
Change-Id: Ib9f8a52136e25d1cb609d465ca5d859523d9acc6

This is required because oslo_policy's 'enforce' method expects a dict-like
object as its second argument.

Change-Id: I9187b6805d3b2cd351189e34dd2f9db3158f6b8d
Closes-Bug: #1720354
(cherry-picked from commit 3134ee07)

When sending a SIGTERM to the main glance-api process,
it was sending a SIGTERM to its children
but then also re-spawning its first dead child.

Closes-bug: #1714240

Change-Id: Ibef426c198d287bbdac4e764fd654edba4b7c2d6
(cherry picked from commit 877cd166)

The indentation of glance database creation was incorrect.
This patch fixes it.

Change-Id: If3ca607258363f5b6e8e1b86e0425fd74da2e62a
Closes-Bug: #1718125
Closes-Bug: #1720108
(cherry picked from commit 2f8edeed)

Add the missing i18n import in db.utils

Change-Id: I51cca19f2ce82ee28187b0a23d658bbe39376675
(cherry picked from commit c80d032c)

The immediate cause was that the api_image_import flow was not
listed in the entrypoints in setup.cfg, so stevedore couldn't find
it.  After the entrypoint was added, the task was going to failure
because it couldn't find the image_id.  So this patch has the
import controller add the image_id to the task_input dict.  Next
the flows were having trouble finding the image_id, so I just
passed it to them.  There's probably a more elegant way to have
taskflow handle this, so this patch could use a refactoring.  On
the plus side, the interoperable image import process does appear
to work with this patch.

NOTE: if you want to test this in devstack, use the stable/ocata
devstack but with the master branch of glance.  The tasks engine
doesn't appear to be running under the Pike devstack configuration.
(Use defect 1712463 if you have an idea what might be the problem.)

Change-Id: Ic68c17f4cb671eb664e2de331787b55fe9878a27
Closes-bug: #1712462
(cherry picked from commit 4366a749)

This commit adds a note to the docs further explaining how to run glance
as a wsgi script with uwsgi. Since pike doesn't support chunked encoding
on requests we need apache to dechunk them before forwarding the request
to glance/uwsgi.

Change-Id: Ib09d2196d038d5f591d47349e66eba1bf609fcaa

A correction in the help text of a configuration option (see
Change Icd79be4eb9d363e70955dbe208aba8564cf21e8e) requires that
the sample config files be regenerated to include the correction.

Change-Id: I6ae336f472bb88a4a6ea1748db5fa936c702e36f

Help text for enable_image_import refers to [TASKS] whereas the
related option group is named [task].  This patch corrects the
text so that operators don't add config for a group that doesn't
exist and then wonder why it's not having any effect.

Closes-bug: #1712110

Change-Id: Icd79be4eb9d363e70955dbe208aba8564cf21e8e
(cherry picked from commit d38c8d23)

Change-Id: I3815305e3b9d86eadfbaf6b9cf4d0867fc664fb5
(cherry picked from commit 2efc5b8f)

Adds documentation of the interoperable image import process
introduced in Pike in the EXPERIMENTAL Image API v2.6.

Change-Id: Ifbedc2e5e566db084bc7028ed4239485f0d68b18
(cherry picked from commit 8005ee99)

Whether or not the v2.6 EXPERIMENTAL API is exposed at a site
depends on the enable_image_import config value.  If it's False
(the default), then the API a client sees is the CURRENT v2.5
API, and any of the v2.6 calls made against 2.5 return a 404
(same as if you were running Ocata).  This patch adjusts the
'versions' response so that when enable_image_import=False,
the EXPERIMENTAL v2.6 does not appear in the response.

Change-Id: Ibe164f02c99d10f5a5edd0de96c665413a12f700
Closes-bug: #1711829
(cherry picked from commit d3871a57)

Change the response to GET v2/info/import to be a 404 when Glance is
configured with enable_image_import = False so that the response is
consistent with the v2.5 API.  See the bug for details.

Change-Id: Ib56b600dbf53672bcaa4fd959adb736de4cdff50
Closes-bug: #1711362
(cherry picked from commit 692dc040)

This patch modifies the images controller to accept a body (which
is required) for the image import call and cleans up a bit around
the request deserialization/response serialization.

Co-authored-by: Abhishek Kekane <abhishek.kekane@nttdata.com>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>

Change-Id: I08783e28719e63b5a4b2115b8fce135e55be460a
Closes-bug: #1708702
(cherry picked from commit d4917cf6)

This patch updates the disk_format description to include "ploop"
(added in Ocata).  It also rewrites the container_format description
to indicate that the actual values depend on how the API being queried
is configured.

This patch does not update the api-ref for the deprecated v1 API.

Change-Id: I3385b3f628b74b109c05108e331085c54b0126a1
(cherry picked from commit 08cd24d2)

The Tasks API was made admin-only in Mitaka to prevent it from being
exposed directly to end users.  The interoperable image import
process introduced in Pike uses the tasks engine to perform the
import.  This patch introduces a new policy, 'tasks_api_access',
that determines whether a user can make Tasks API calls.

The currently existing task-related policies are retained so that
operators can have fine-grained control over tasks.  With this
new policy, operators can restrict Tasks API access to admins,
while at the same time, admin-level credentials are not required
for glance to perform task-related functions on behalf of users.

Change-Id: I3f66f7efa7c377d999a88457fc6492701a894f34
Closes-bug: #1711468
(cherry picked from commit b90ad252)

The glanceclient relies on the schemas being accurate so it can
format responses.  Without this update, admins won't be able to
use the glanceclient generate a task list containing the
api_image_import task that the task engine uses to process the
new image import process being introduced in Pike.

Closes-bug: #1711018

Change-Id: I5bcc9f4cdc55635809e8a90be555a367348a58c2
(cherry picked from commit b6e4ddaf)

Adds a RequestDeserializer for the stage and adjusts the image
status transitions so that they can handle the 'uploading' status
of an image with data in the stage.

Closes-bug: #1710958

Change-Id: I6f1cfe44a01542bc93a43cbd518956686adb366d
(cherry picked from commit e17a3493)