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>
The manila service image was recently rebuilt and is
now bigger than 2 Gibibytes so increase it to 3, which
should last us for a while.
Closes-bug: #1870412
Change-Id: Ia03e48a3f0ff352b94a0224f76f278ef45acad93
Add support for querying user messages by specifying a timestamp, which
will be compared to the created_at field, and manila will return all the
messages matching to the time condition.
Partially-Implements: blueprint query-user-message-by-timestamp
Change-Id: I3d94bac4304c236f275abe7ce31432b0e2384247
This fix doesn't fully address the issue given that share backends
are allowed to use a list of capabilities and reporting thin_provisioning as
[False] will still allow the calculation of provisioned_capacity_gb.
Bug #1869712 will be fixed in a follow up patch.
This reverts commit cd9292b931a0f74079512cd43652129a9c595ee8.
Change-Id: I922f161980e8a1ef7cf111b1e30c02991073d6e5
Fix:
W605 invalid escape sequence
This is the final change I plan for hacking, the remaining problems
need further investigation by manila team and decision whether and how
to solve them.
Change-Id: I73d73e044eaaf412bf7ace358a3f07c8d269d6cf
Fix:
E731 do not assign a lambda expression, use a def
I just marked the lambdas with noqa.
Fix also other problems found by hacking in files changed.
Change-Id: I4e47670f5a96e61fba617e4cb9478958f7089711
