Currently, manila doesn't support user controlled way to encrypt the
shares. This spec intends to make this possible.
Implement: blueprint share-encryption
Change-Id: I0245e89e4dedcdb6afd1cbfb992ff3b80f7d06e2
During delete, free the used share/share-snapshot quotas immediately
and process deferred share/share-snapshot deletion in share manager.
This will reduce the waiting time of new share/share-snapshot creation
blocked on quota limit.
Partially-Implements: blueprint deferred-deletion
Change-Id: Ia7591f036f975a0610a45c5ebbc54696d8244fd0
Design of better visibility and manipulation protections
to access rules of a share.
APIImpact
Partially-Implements: bp protect-access-rules
Change-Id: Ib184995f6fce2a9aaa60f8251513d58c5b663112
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
A proposal to introduce "resource locks" that
can be placed by project users against project
resources and specific resource actions that
they intend to prevent. In the 2023.2 Bobcat
cycle, the share deletion resource locks will
be implemented.
Partially-Implements: bp allow-locking-shares-against-deletion
APIImpact
Change-Id: Icdc909c43459730c8e35a677779d842e36dc7b1b
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Adds the spec-lite for the integration between NetApp ActiveIQ
software with Manila Scheduler weigher phase.
It also adds the bobcat release directory specs.
Change-Id: I7ecbad25660f10170172fc2a07507000bfafde75
Currently, manila doesn't support backup and restore share features in
manila itself. This spec intends to make this possible.
Implement: blueprint share-backup
Change-Id: I3b345f396e581575a403c728136eb644565c5928
This spec proposes changes to Manila with the purpose of
addressing the need for having share servers with network
allocations on multiple subnets.
The spec is splitted in two phases, targeting to more
than one release:
1. Add ability to define multiple subnets in the same share network AZ
2. Add ability to "update" subnets in a share network AZ
Implements: bp multiple-subnet-share-servers
APIImpact
Change-Id: I080c083c5517c1b51eaf9fd328810df6aa97fe40
Add support share Recycle Bin, the end user can soft delete
share to Recycle Bin, and can restore the share within 7 dyas,
otherwise the share will be deleted automatically.
Partially-Implements: blueprint manila-share-support-recycle-bin
Change-Id: I9359387267aa617f07e977e30da11efaead2b171
Introduce a new lite spec that describes human readable export
location support for Manila.
Partially-Implements: bp human-readable-export-locations
Change-Id: I3668c65dc094075ea326fd0e0aa2bb3ca455f585
Proposal to accommodate metadata and
associated operations on all user facing
share resources (e.g.: snapshots, groups,
share networks, security services, etc.)
APIImpact
Partially-Implements: bp metadata-for-share-resources
Change-Id: I4d276311e3cd42ad9f0fab78a9b2c850c5727bb6
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch adds a new manila specification to allow updates and
association of new security services to in use share networks. This
operation permits provisioned share servers to have their security
service configurations updated, by updating existing or adding new
authentication server types.
Change-Id: I0a4f573ce19f658702e0c5a7d9910b90bf75ae5d
Signed-off-by: Douglas Viroel <viroel@gmail.com>
Add support for limit the size of share through the share type, the
share created by the user shall not be greater than the maximum value
set in the share type and shall not be less than the minimum value set.
Of course, depending on the usage scenario, only a maximum or a minimum
can be set.
Partially-Implements: blueprint share-size-limited-by-share-type
Change-Id: Ie03a4564ddcacd9b084db09b76be55d15080133f
Moves the change from ussuri to unimplemented and updates it with
some information regarding the implementation that is already
available to use for share replicas quota control.
Change-Id: I4abbedc1aac95c283184173033ff359f08316395
This patch adds a specification for migrating share servers
and all its resources to a new destination. This spec proposes
a mechanism similar to the existent share migration.
APIImpact
Partially-Implements: bp share-server-migration
Change-Id: I535efdc6d8f5517163b6c285e7c1503a4313b6ee
Signed-off-by: Douglas Viroel <viroel@gmail.com>
Add a new lite-spec that proposes two new backend capabilities
to Manila. The capabilities ``max_shares_per_share_server`` and
``max_share_server_size`` are being added to help the
administrator to control the size of share servers.
Partially-implements: bp new-share-server-limits
Change-Id: I23053fcc2cdf8fd7e099c8ccab0785d864b3e7dd
Add annotations to test cases about the status of
their implementation. This clarifies what part of
this spec still needs work.
Change-Id: I035c49ce48e53db787d7153f9957ddd134ec924c
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This patch adds a lite specification describing the unlimited share
replicas per share issue and describes the proposed solution.
Change-Id: I8f8819ddb7200ff3104ed01cdaa3fd31b670dad2
This patch update and move the spec Create Share From
Snapshot in Another Pool or Back End to Ussuri.
The spec updates were based on PTG discussions [1].
[1] https://etherpad.openstack.org/p/shanghai-ptg-manila-virtual
Change-Id: Icbdaaf4c4d1063c6251de30a95283d9e08177b9d
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: I357c198990a92e2ac61ece24df129f9878aa7b64
python-openstackclient is the default command line client
for many OpenStack projects. Having support for python-openstackclient
is a community goal for the Train cycle and it's important that we do
this so we are consistent with the rest of the projects in the OpenStack
ecosystem.
Present a convenient mapping between the current python-manilaclient
and the future implementation for the manila support in python-openstackclient
aiming for ease of use.
Change-Id: I051bedac0f0eb6064bb72efc155ecdf0e6814a75
Co-Authored-By: Sofia Enriquez <lsofia.enriquez@gmail.com>
One of the current limitations present in most Manila drivers is the inability
to create new shares from snapshots in pools other than the source share's.
Given that some storage back ends have the ability to fast clone a share from
a snapshot to another pool or back end, having this feature working in Manila
will greatly improve the user experience.
This spec proposes changes to the current design of scheduling new shares
created from snapshots. We will introduce a new scheduler capability and
improve the behavior of an existing API parameter. By allowing the user to
choose the desired availability zone and the admin to optimize its placement,
we can improve our scheduler to be smarter for better load balancing and
space efficiency results, while also preventing erroneous behavior.
One of the result of the improvements proposed is that drivers will be able to
rely on a proper scheduling mechanism that makes sure new shares created from
snapshots can land on compatible destinations.
Partially-implements: bp create-share-from-snapshot-in-another-pool-or-backend
Change-Id: Ibc0bdc56c642c7db973b74f0ae0494406fb371c0
Currently, only the name and description and public access of share-type
is set when the share-type is created, and not allowed to be edited after
the share-type is created. We can only set extra spec for share-type. But
not name or description or public access for share-type.
APIImpact
DOCImpact
Co-Authored-By: Brin Zhang <zhangbailin@inspur.com>
Implements: blueprint update-share-type-name-or-description
Change-Id: I306dc02e4bd3d507dfee18fca77b43dfba6c3ccd
Kiran Pawar