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

When the neutron_lbaas is configurated and enabled,
the created router will be HA router. Every router
instance will has a HA port which to keep them alived.
Those ports, whose device-owner is router_ha_interface,
will shown on page.
But there will throw an NotFound error when deleting them.
IMO, it is enough for user to known them exist. we
don't need to operate them for they only using by router
instance.

Change-Id: I276b5754b936d03b87b1e8ef39097a130e309211

Change-Id: I8c4d0243716bbdbc8d4195d5dfa1b24e54e03978
Closes-Bug: #1822521

In Train, we will use python 3.6 and 3.7 for python3 runtime
in our gate jobs [1]. This commit drops python 3.5 info
and adds python 3.6 and 3.7 info.

[1] https://governance.openstack.org/tc/reference/runtimes/train.html

Change-Id: I8f024505ed9b37c9f2b480f49b5000d75da42cc0

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

Change-Id: I7b3e2b98f5c0f1e4d98fae745b645668d7fe8561

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

Change-Id: I6d396e0ca181f59b5ff13f7512e99077a0bb4a3d

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

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

Change-Id: I94182b7c593fdf387b332c5af513b845be2f2846

These jobs are stable enough so we can make them voting:

* horizon-selenium-headless
* horizon-integration-tests
* horizon-tox-bandit-baseline - this job is now voting and configured
  only for 'check' queue.

Change-Id: Ifca858e4c85748d801c412d7e91dce3362f0204f

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

Change-Id: Ia0fa7e427c8fe7dcab308a5bdb17d07936826645

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

Change-Id: I7ace2529b9fdfcbbd348f9b49f5d9e54497e9def
Closes-Bug: #1821288

Add file to the reno documentation build to show release notes for
stable/stein.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.

Change-Id: Ie89592ab93af0998b5629c1b33567c98e85200e9
Sem-Ver: feature

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

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