Grenade jobs need to test Ussuri-->Victoria (dev)
upgrades in the master branch.
Change-Id: I95d1efb35f1c3c311071448117406bc275281e43
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This job fails because it's expecting network subnet
details to be in a format that was revised in API version
2.51.
This change can be backported to stable/ussuri
and only impacts the CI.
Change-Id: I3731e6acffccd2ecb398f3b5cf81a5f294c51f45
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: Ia63ac711d3a14be266eb338c9a253b06fd26af83
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: I8b6cb47574f5f6ff29ff4ba895cb86e5a0f14c22
Sem-Ver: feature
Use the default value provided by tox:
https://tox.readthedocs.io/en/latest/config.html#conf-install_command
See discussion on the openstack-discuss ML [1]
for the complete context.
To get this fix in, we'll need to raise
a few requirements:
- eventlet because of the ssl issues with python3.6 in
older packages
(https://github.com/eventlet/eventlet/issues/371)
- oslo.messaging to fix the error "ACCESS_REFUSED - Login
was refused using authentication mechanism AMQPLAIN.".
- psycopg2-binary since 2.6.2 is blacklisted
- oslo.service was bumped to 2.1.0, to pick up its support
for eventlet>=0.22
- oslo.utils was bumped to match the lower constraint from
oslo.service at 2.1.0
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014237.html
Change-Id: I6344f44fb955d631a4f0a13fa53ecc19826c7ea6
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
The NetApp driver is now fixed to not trigger vserver peer accept when
handling with share replica operations on 'driver_handle_share_servers'
mode enabled.
Closes-Bug: #1873963
Change-Id: I9df8b48bf2c127f266c1b950bafc710bc28f7632
This patch fixes the error raised by NetApp driver when the user try
to shrink a share to a size smaller than the current used space. Now
the driver raises "shrinking_possible_data_loss" instead of
"shrinking_error".
Change-Id: I01a549a0e299ae0d0d9b603a9d0797f16f4b68b3
Closes-Bug: #1858328
When project quota set unlimited(-1), and user in the
project is limited to a value.Then project quota must
smaller than project usage when checking quotas, which
means the value 'overs' is not None.
In this case, even though the user not over the quota,
but they can not create share
Closes-bug: #1872872
Change-Id: Id9e2bcb5d30d2b81b0723dd296b537ac7d4519f2
These documents borrow from the cinder, nova and
ironic guides put together painstakingly by
numerous developers.
Change-Id: Ida3480fd1b9cab8eeb9ad002cce7200d89e01cb6
Story: #2007236
Task: #38535
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
when running tox py36/37/38 test, it failed with error
MismatchError, reference in cinder [1].
[1] https://review.opendev.org/#/c/720008/
Closes-bug: #1872919
Change-Id: Ib76c8df7a435ba72cd0cffd7081d455fff02be0f
This is to fix the following assert statements:
* asser_called_once_with, which should be assert_called_once_with
* asser_called_once, which should be assert_called_once
Change-Id: I0025b06d6b10249b118a46e67d8ca6ba56d4befd
It fixes the export locations returned by `create_share` and
`create_share_from_snapshot`. The export locations should be a list of
dict like: `[{'path': <original_location>}]`.
Change-Id: Ic97fa34455054aeda10608486edf120a9dc3d9f3
Closes-bug: #1871999
The NetApp cDOT driver is now fixed to ignore vserver peering
when creating and promoting shares replicas within the same
vserver.
Closes-Bug: #1872243
Change-Id: I0b82c15aec7862ee3630330805ac3ac177aae127
Fixed an issue in the contributor reference. The share replicas
documentation has two references to the same driver interface and
it caused a problem while generating docs, since none of them was
tagged with ``:noindex:``.
Change-Id: I9db0f2c07a8178895490fbcab9bfd9dcd2ccf823
Closes-Bug: #1872479
The job manila-tempest-minimal-dsvm-lvm is functionally
identical to manila-tempest-minimal-dsvm-lvm-ipv6-only.
Semantically, the only difference being that the service
host, and in turn the endpoint base for manila, and the
communication address for rabbitmq, mysql and other infra
services.
manila-tempest-minimal-dsvm-lvm-ipv6-only
has MANILA_SERVICE_HOST set to an IPv6 address,
for example:
MANILA_SERVICE_HOST='[::1]'
MANILA_ENDPOINT_BASE='http://[::1]:8786'
manila-tempest-minimal-dsvm-lvm has MANILA_SERVICE_HOST
set to an IPv4 address, for example:
MANILA_SERVICE_HOST='23.253.236.222'
MANILA_ENDPOINT_BASE='http://23.253.236.222:8786'
So lets drop the job enforcing IPv4 service host since
we have coverage for that scenario in other jobs that
we're running, including the voting
manila-tempest-minimal-dsvm-dummy job.
I'd like to backport this change to stable/train
during which this job was duplicated to cover the scenario
of doing "ipv6-only" service host testing [1]
[1] https://review.opendev.org/#/c/682716/
Change-Id: I51dc25889c1d1fb361f0be6f8c0aa47ca64c9aaa
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch improves the operation of creating share from snapshot
to accept new destinations that can be different pools or
back ends.
Change-Id: Id3b3d5860d6325f368cbebfe7f97c98d64554d72
This patch improves the operation of create share from snapshot
to support different backends/hosts for the zfsonlinux driver
Partially-implements: bp create-share-from-snapshot-in-another-pool-or-backend
Depends-On: Iab13a0961eb4a387a502246e5d4b79bc9046e04b
Change-Id: I124803734c81d3630c5147f5f3bb75724489c929
This patch updates the share groups APIs to be no longer considered
as experimental. It is done by removing the experimental flag from
the share groups, share group snapshots, share group extra specs
and share group types requests.
DocImpact
Partially-Implements: bp graduate-share-groups-feature
Change-Id: I080683541d527657f01008d43529fc53c19a09cd
This patch enables the creation of a share from snapshot
specifying another pool or backend. In the scheduler, a
new filter and weigher were implemented in order to consider
this operation if the backend supports it. Also, a new
field called 'progress' was added in the share and share
instance. The 'progress' field indicates the status
of the operation create share from snapshot (in percentage).
Finally, a new periodic task was added in order to constantly
check the share status.
Partially-implements: bp create-share-from-snapshot-in-another-pool-or-backend
DOCImpact
Change-Id: Iab13a0961eb4a387a502246e5d4b79bc9046e04b
Co-authored-by: carloss <ces.eduardo98@gmail.com>
Co-authored-by: dviroel <viroel@gmail.com>
1. Try parse share_backend_id from export path in case
it is managed share.
2. Try to take snapshot id from 'provider_location' in case
this is managed snapshot
3. Try to get share server name from property 'identifier'
first in case this is managed share server
4. Add property 'provider_location' when creating snapshot
Implements: blueprint emc-unity-manage-unmange
Change-Id: I676475d0500ecce31a1a863926accec8585ac83a
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
On those backends, there is no need to calculate provisioned_capacity_gb
as it is not used during the scheduling. This calculation was not
scaling properly on big environments as it implies many database
queries.
Closes-Bug: #1869712
Change-Id: Icb8947991723a2a1cc334a72276a35cf50fc1b7d
Currently we're in a foobar situation with two database
models ShareTypeProjects and ShareGroupTypeProjects
where we keep stuff around even when the concerned
ShareType or ShareGroupType objects are deleted.
So, delete type access rules when types are being deleted.
Change-Id: Id135a96f2d1b7306156bab0ddedcb1b838a74f0a
Closes-Bug: #1870751
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch adds new quotas for share replicas and replica sizes.
This quotas can be related to either tenants and users or tenants
and share types. Now, when creating a share replica, manila will
check if there are resources available for that specific request.
Partially-Implements: bp limit-share-replicas-per-share
Change-Id: I8ba7bc6f167c28d6c169b2187d0e1bda7cad3f69
Share types can be associated with share group
types. This relationship needs to be dropped in
case share types are to be deleted, or we'll be
leaving behind dead references in the database.
Share groups cannot exist without share group
types, and hence we don't need to check on existing
groups when deleting share types; checking for
existing group types will suffice.
Change-Id: Id86a93f1923a493cefe73e2d90d5094005b42ae4
Closes-Bug: #1699836
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
