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: I645c9d81d18435957f55168b8a9b7e18e4ef96a0

aodh-dsvm-functional-mysql and aodh-dsvm-functional-postgresql jobs
fail on stable/ocata with:
  "chown: invalid user: jenkins:jenkins"

This patch is only needed on stable/ocata as on newer branches does
not contain this post-test hook anymore.

Change-Id: I084959f672c33f942c732953ea039f975091499d

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: I786172f269415ad7dcf1437dc9f1f8c27bb7151f
Story: #2002586
Task: #24339

the code[1] we needed from tempest was removed.

[1] I1c02fd88c3d93b511ff4a6b54b668ebd306481a9

Change-Id: I0b0d418772949b89af6072269745eab5f110bc80
(cherry picked from commit 37f0e708)

Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.

Change-Id: Ib7cffd1b06b81c0c31fd2f6f3894d3810117cea9

oslo.config doesn't support %{} or %() variable interpolation while
ConfigParser does.

So when a password contains a '%', it's fine for oslo.config
But the Python ConfigParser will raise the exception.

Since alembic use ConfigParser and not oslo.config, we have to escape
the url ourself.

This is not a big deal since, we don't want alembic doing variable
interpolation.

Change-Id: If7bfe7f082f4352fb49992a2216f2dd5b8993711
(cherry picked from commit 268c1e8e)

also cherry-pick If8df8a6e8cad2d9247f07c9ed7a71f29b19f7d51

Related-bug: #1737115
Change-Id: Id8368c0091ef8eb6a567ba9036bd11d656bcf8d4
(cherry picked from commit 607d4e87)

Add an empty line so that display of the release notes works and it gets
passed as proper RST enumeration. Fix also a typo.

Additionally, cap oslotest to < 3.0 since version 3.0 removes Mockpatch
which the tests uses. This fixes failing functional tests.

Change-Id: I994aa3cf173ec8a9412239544e3269aca17adc25
(cherry picked from commit de4eb0c8)

Zuul now supports including the file extension on the playbook path
and omitting the extension is now deprecrated.  Update references
to include the extension.

Change-Id: If0052ee3a357c332d3c069c2c58446e25d1a0374

This reverts commit 8ca7f267.

we uncapped pbr here: 0ffb1da9



combined with zuulv3 job patch to fix:
Change-Id: I741ede216374b6bb93dab3960e8018e3a5204484
Co-Authored-By: Kien Nguyen <KienNT@vn.fujitsu.com>
Co-Authored-By: gord chung <gord@live.ca>
(cherry picked from commit c49ae680)

Change-Id: I5cad9aac7649f1133118073de7661cb74e59163b

Add missing granularity value which should
be sent to Gnocchi.

Change-Id: I246763514a98d17f3f2ea53cec2b5cc8a25fc9cb
Related-Bug: #1719931
(cherry picked from commit 442a435c)

aodh is set to gnocchiclient>=2.1.0. therefore, it cannot support
gnocchiclient 4.0.0+ without breaking 2.1.0 constraint. cap its
requirement

Change-Id: I9017b284dfc13ca638d091fbc76b29ef2dda4003

Zane Bitter authored Aug 15, 2017 and Julien Danjou committed Aug 15, 2017

Since Aodh uses trust IDs stored in alarm URLs unconditionally - without
checking for tenant safety - it is not safe to allow users to pass in their own
trust IDs. Forbid this and allow only trusts created by Aodh to be used. It is
highly unlikely that there is any (legitimate) use of this feature in the wild,
since allowing Aodh to create the trust is easier anyway.

Change-Id: I8fd11a7f9fe3c0ea5f9843a89686ac06713b7851
Closes-Bug: #1649333

Tempest provides stable library interfaces under tempest.lib.
This patch switches to use it for data_utils.

Change-Id: I10b5877b12e2c28515b49c8b9221590cb7aa4f30
(cherry picked from commit 55e63d4e)

When an unprivileged user want to access to Gnocchi resources
created by Ceilometer, that doesn't work because the filter scope
the Gnocchi query to resource owner to the user. To fix we introduce
a new configuration option "gnocchi_external_project_owner" set by
default to "service". The new filter now allow two kind of Gnocchi
resources:
* owned by the user project
* owned by "gnocchi_external_project_owner" and the orignal project_id
  of the resource is the user project.

Closes-bug: #1703824
Change-Id: I0c86736a902a21520da18550aea0a7d1549bb24e
(cherry picked from commit b0bdd432)

aodh only supports sql in ocata

Change-Id: I66d8da9d099c9e5ba17aa29bc02c3043cdd2f5b5
(cherry picked from commit 132de83e)

test_alarms_sends_notification will hang forever if it fails.
we don't really need to test that its notification is received by
other, just that it sends a notification. drop the test so it
verifies only that.

also, uncap pbr to resolve requirements conflict

Change-Id: I99f9996e5a3dd1e652d4142c7b596ae87da5e698
(cherry picked from commit b231f83f)

DeprecationWarning: Using the 'enforce_type' argument is deprecated in
version '4.0' and will be removed in version '5.0': The argument
enforce_type has changed its default value to True and then will be
removed completely.

This option have never been useful, and now the default is already True.
So we don't need to raise requirement for this.

Change-Id: I042a5d98748e2b2c6ee8307340aa6056bf0a1dfd
(cherry picked from commit d8e33f78)

pike libs don't work with ocata because they require pbr>=2.0.0 and
ocata is the opposite. upper cap the libs that are conflicting.

Change-Id: I8eabc0649114f18f9f93fa342999ebd645107dc6

* Fix markup
* Add more links
* Don't include an unfinished page

Change-Id: I901f611349feecf56eb18dea425ee655549eeb43
(cherry picked from commit 62b81915)

there is no alarm_change table, so this fails during
migration when using mysql/

Change-Id: Ia0c63681fd8b5bc692d0a52ab587a6d3e430a844
(cherry picked from commit 23552b1c)

Change-Id: I45e310f03efc188083d659e3a2733d5c9b97ee97

Just include an example in the doc is enough.

Change-Id: I78522a7b86d26f287444ce0cbcc8584caf290ebf

test.idempotent_id is being kept temporary to migrate
to new lib interface. Now idempotent_id is available as Tempest stable
interface decorators and all plugins tests using the old decorator
should be switched to new interface.

In future, Once all plugins are switched to new decorator Tempest
will remove the test.idempotent_id

Change-Id: I20ef363a008b1c01652015cc2ada69777b8859d9
Related-Bug: 1616913

Change-Id: I4e88a6a6f37630b2d49e10bdd50778de336d7bbf

Without this Newton and Ocata have the same version causing
packaging issues.

Change-Id: I6e3a544afb93f33a138d89b774320f066fa61377
Sem-Ver: feature

Change-Id: I94c5b0f21e28eeaf8d87d33fa59e1e3a26c32a51

Change-Id: I33c8055245de5821fd8a605d4ea6bf388a01637e

This is already in api-paste.

Change-Id: Ib0751afe3c16a9bea81306cc988b2beff8c1060d