Policies are generated using oslopolicy-sample-generator
according to Horizon 'Policy file maintenance' guide [1].

[1]
https://docs.openstack.org/horizon/latest/contributor/topics/policy.html#policy-file-maintenance

Change-Id: If31c072ab14e1746969b7f94e6837722cefa28ea
Closes-Bug: #1821289
(cherry picked from commit 36170ed3)

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I2b94433c476cdc008240ba05a1fd4218df29129a

Using a scsi decorated image with:
hw_disk_bus='scsi'
hw_scsi_model='virtio-scsi'

This solve the case where an instance is
launched with 'image' selected as boot
source with a new volume. This will result
in /dev/vda instead of /dev/sda as it
should.

Not specifying device name in
setFinalSpecBootImageToVolume() leaves the
decision to nova to determine it.

Example:
-------
VM boot volume without scsi meta data decoration:
Attached To
0a0cd660-7ce3-4033-9983-2e1099edc5f0 on /dev/vda

VM boot volume with scsi meta data decoration:
Attached To
91f50dbc-8bdf-4293-84ea-fc5df27b5ee4 on /dev/sda
--------

Note: This commit doesn't address cases for
where instances are launched using existing
volume and snapshot, this will involve more
work to migrate the code from BDMv1 to BDMv2.

Closes-Bug #1560965

Change-Id: I9d114c2c2e6736a8f1a8092afa568f930b656f09
(cherry picked from commit 4788c4d2)

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: Icd341ba451e20e8ff5e5caf5a1141d520660dd55

When instance is created from cinder volume, it's image is not displayed
Nowdays using cinder as instance source becomes more widespread,
so there is sense in displaying instance image,
when instance is created from cinder volumes.
We're trying to get volume_image_metadata from the first volume of
the instance, when instance doesn't have image attribute itself.
First volume is suggested based on its device name (eg. '/dev/vda').

This info is displayed only in instances list, not in detail overview.

Change-Id: I00aa9ef07d1680bb2390a30271bb39cd7bea6329
(cherry picked from commit 3c82a38f)

Also fixes the success message of "Clone Group" form.

Change-Id: I7ace2529b9fdfcbbd348f9b49f5d9e54497e9def
Closes-Bug: #1821288
(cherry picked from commit 2d6dfd59)

Previously d3 version of the network topology view handles ports with
device_owner 'compute:nova' and 'compute:None' specially. This leads
to the situtaion that neutron ports with non-default AZ are not shown
properly. There is no reason to handle neutron ports with the default
AZ differently. What we would like to do is just to classify neutron
ports attached to nova servers.

This commit changes the logic to check device_owner of ports have
a prefix 'compute:'. Note that we also need to check if device_owner
is a string before checking the prefix.

Change-Id: I472bae9af3d14d8a31efcae8a7610b84c4f09c3d
Closes-Bug: #1820260
(cherry picked from commit ffbe0e2f)

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

Change-Id: Id6ff32b4edaeb716eb7e18bb6787c7215e11c70a

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I3a14d02e7986349a6508c6b93d01ed6f8f803db7

This patch fixes the issue.

Change-Id: I57172c01f894a3227f39433c343229ba57f44148
Closes-Bug: #1820938

This patch fixes the issue.

Change-Id: I39d0f33030bca62a15c93837b4761c36d4cd372c
Closes-Bug: #1820935

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I1db2fb98c0bc2ac74fe51be104930084d5fd7f70

This patch add a validation message when a user try to 'Create'
a extra spec with an existing key name under Volume Type panel.

Change-Id: I6a1eac269e616ba0861a41eda5eac1b1a4cdd1d0
Closes-Bug: #1818826

Proposed patch correctly passes CSRF token to Angular application with
CSRF_COOKIE_HTTPONLY config option turned on. Also, minor release note
warning fixed

Change-Id: Iec90643078dcf3ed4ad786ecc21bfb067a242c6d
Closes-bug: #1819423

This patch add "Group" column in Volume table and
"Group Snapshot" column in Volume snapshot table under
admin panel.

Change-Id: Ifa18c70be7d73b302e75ab451b1cd572d970b5c6

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: Ibe73987851336f8d8f3d5b4e9de9e99270109638

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I57b1dc503a3060378c8fd0e8611e34f98443e9c3

Monty recently setup a project-template for nodejs4 jobs[1], but
some projects (Octavia for one) want to be bionic/nodejs10 (LTS)
ready.
This patch sets up a template for bionic nodepool instances using
nodejs 10 (LTS).

[1] https://review.openstack.org/#/c/643198

Change-Id: Ibc2c4b5b5207e66700b5c4e04aca3c6a00d392be

It is possible to make Horizon reach the "Pure project admin doesn't
have a domain token" state in domain_lookup by having different policy
files in Keystone and in Horizon, at which point it results in an
unhelpful AttributeError later on, because domain_lookup returns None.

I'm proposing to make it return an empty dict instead, this way Horizon
doesn't crash, but we still get the warning in the logs.

Change-Id: I7a42e8defb2fb348cac8225fb1dcbf5e86c9e65c