manila-ui 7.0.0.0rc1 release candidate

meta:version: 7.0.0.0rc1
meta:diff-start: -
meta:series: yoga
meta:release-type: release candidate
meta:pypi: no
meta:first: no
meta:release:Author: Elod Illes <elod.illes@est.tech>
meta:release:Commit: Elod Illes <elod.illes@est.tech>
meta:release:Change-Id: I0e5b16e4f64d6051b6a88b19fa45987d195994bf
meta:release:Code-Review+1: Goutham Pacha Ravi <gouthampravi@gmail.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

We need a newer version of the SDK to enable
features supported by newer API versions. While
this commit doesn't enable new features, future
commits will; so bumping up the required SDK
version is a necessary predecessor. Using 2.7.0
gives us access to API versions upto 2.63.
Version 2.7.0 was released in June 2021. [1][2]

Horizon 18.3.1 is off of the stable/ussuri release
of horizon, shipped in Apr 2020 [3]

[1] https://lists.openstack.org/pipermail/release-announce/2021-June/011255.html
[2] https://docs.openstack.org/releasenotes/python-manilaclient/xena.html#relnotes-2-7-0-stable-xena
[3] https://review.opendev.org/c/openstack/releases/+/721047


Change-Id: I100a1ec20a0c59c0a7023136e0eab7a0b63b6709
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Add dpkg platform for the packages and their
respective package name for rpm too. There are some 
packages not available in rpm so I added just those that have it.
 
Related-Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2054776
Change-Id: Ib57e0dc00c9f47d589d8723d7feac01f27b0f3a0

Yoga testing runtime[1] has been updated to add py39
testing as voting. Unit tests update are handled by the
job template change in openstack-zuul-job

- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286

this commit updates the classifier in setup.cfg file.

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

Change-Id: I9c7aa6b17073677d15c2b0c6e1e59e73b918fc0f

manila-ui 6.0.0.0rc1 release candidate

meta:version: 6.0.0.0rc1
meta:diff-start: -
meta:series: xena
meta:release-type: release candidate
meta:pypi: no
meta:first: no
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: Ia7872673bb8af26065cfcf23ca87976fbe01c8a7
meta:release:Code-Review+1: Goutham Pacha Ravi <gouthampravi@gmail.com>
meta:release:Code-Review+1: Carlos Eduardo <ces.eduardo98@gmail.com>
meta:release:Code-Review+2: Hervé Beraud <herveberaud.pro@gmail.com>
meta:release:Workflow+1: Hervé Beraud <herveberaud.pro@gmail.com>

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.

See also the PTI in governance [1].

[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Id8fb7b598001507e618638ed4d05b6d20301e4b5

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

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

Sem-Ver: feature
Change-Id: Ia2143e6caced94e49c3aa28106cbc0a38401b048

Follow up to change #783041. Fixes bug of missing "share_id"
argument in redirection url in Exception case.

Change-Id: Iaadf24c839296e44c51dd1da2399bb63f757829a

Partial-Bug: #1823078
Change-Id: I3f2b4e6ebf715615b0f65cc26451f9ba406ba236

Added 'is_default' field to share types and share group
types list. 'is_default' field will show Yes if the share type
or share group type is default.

Partial-Bug: #1823078

Change-Id: I923cb2ae90612fb8d5d3af467654a71b83266ffc

Added access metadata for share access and also introduced the GET /share-access-rules API.
The prior API to retrieve access rules will not work with API version >=2.45

Closes-Bug: #1920687
Change-Id: Iec3a3fad5e2bdf854f04ae974248d899f90bd894

This patch-set modifies how we manage user input when creating a share
from snapshot. Since we use the same form for the basic create share workflow
and for the create share from snapshot workflow, we need to add a check
to distinguish both cases: when creating a share from snapshot, the
parent share availability zone is picked by default. Otherwise, if it's a
regular share create, the user can pick up the availability zone they need.

Closes-Bug: #1915706

Change-Id: I8d93c2214cb187a763df861555ddd7b444c9ca89

The patch bumps min version of tox to 3.18.0 in order to
replace tox's whitelist_externals by allowlist_externals option:
https://github.com/tox-dev/tox/blob/master/docs/changelog.rst#v3180-2020-07-23

Change-Id: I686257fe9ffaefde4d2cdca8ff60a83b908f3b6b

A recent change [1] introduced an encoding for
problematic field names. On the share group
creation form, an encoding was missed causing
a silent failure where the share type/s chosen
were ignored in the API request.

[1] 37e5b2f0


Change-Id: I0983359acc489513a5a0940ac379e0a078870548
Partial-Bug: #1931641
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

This failure has been determined to be unrelated to
changes that are currently in-flight. While we
investigate a fix, we can set this job to non-voting
to merge unrelated fixes/improvements in parallel.

Change-Id: I6f4ce5434a6504ca037c867ce7b9b1ea8e852be4
Partial-Bug: #1933137
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

In the share creation form dialog, share network
selection is optionally provided based on whether
the share type chosen supports the DHSS extra-spec.
This selection breaks often when dealing with share
types that have a name matching the format: ".*-\d+.*".
For example: test-700. The root cause of this seems to
be in javascript code for "switchable" fields [1] that
doesn't get triggered as expected.

A similar issue manifests in the share Network Creation
form where we setup switched fields with the Neutron
network IDs (dashed format UUIDs) and in the Share
Group Creation form where we setup switched fields
with the Share Group Type IDs (dashed format UUIDs).

So, we could encode the "-" in these field names to
workaround this issue.

Closes-Bug: #1931641
[1] https://opendev.org/openstack/horizon/src/commit/647c2b7530f81c4a534ef1d403aa3d90ae608442/horizon/static/horizon/js/horizon.forms.js#L491-L613



Change-Id: Id924fc55debdc38ae2131bf8cef396f28caa3e77
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>

Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I430301474e2294eb6f2d71fc521c73d23c6f8a55

    /usr/lib/python3/dist-packages/openstack_dashboard/local/enabled.
  * Add Breaks: python3-django-horizon (<< 3:19.2.0-2~).

This is essentially dead code elimination
from manila-ui at this point since manila
and python-manilaclient dropped support
in the Ocata release.

Change-Id: I92e87282020047c7fad055cae92f2382c4193597
Partially-implements: bp remove-nova-net-plugin
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>